Free GH-900 practice test: 30 questions with answers

git commit records the staged changes as a new snapshot in the local repository history. Cloning copies a remote repository, fetching downloads remote updates without merging, and init creates a new repository.

A new branch gives an independent line of development that can be merged later after review. Deleting main, merging into a tag and uploading release assets do not isolate feature work.

git clone creates a local copy of a remote repository, including its history. Push sends local commits to a remote, merge combines branches, and revert creates a commit that undoes earlier changes.

When the same lines change differently on two branches, Git reports a merge conflict that needs a person to choose the result. A fork is a separate copy of a repository, tags name commits, and protected branch rules restrict changes.

A fork gives the contributor their own copy with write access, and a pull request proposes merging those changes into the upstream project. Admin rights are not needed, direct edits are blocked without write access, and emailed patches bypass the review workflow.

The README is displayed on the repository's home page and typically introduces the project. The other files configure tooling, ignore patterns or ownership and are not the main introduction.

Branch protection rules can require a number of approving reviews and passing status checks before merge, which enforces the policy. A README, a label or a wiki page is informational and does not block merging.

Review comments attach to specific lines in the diff and form threads that the author can answer. Issues without code links, release notes and general discussions are not tied to the changed lines.

Issues track work items with assignees, and a pull request can reference or close an issue. Gists store snippets, packages host artifacts, and Sponsors manages donations, so none of them tracks bug work.

Keywords such as Closes followed by the issue number link the pull request to the issue and close it on merge. Informal mentions or ignoring the issue do not close it automatically.

CODEOWNERS maps paths to owners, and those owners are requested for review when matching files change. Dependabot configuration, README and licence files do not assign reviewers.

Projects offer boards and tables that track issues and pull requests by status and custom fields. Gists, packages and a wiki index do not provide that workflow view.

A committed secret must be treated as compromised, so revoking and rotating it comes first, and history cleanup is secondary. Assuming privacy, deleting only the last commit and posting the token all leave the secret exposed.

Dependabot alerts flag known vulnerable dependencies and security updates propose fixes as pull requests. Disabling the dependency graph removes visibility, and ignoring alerts or publishing lock files without review increases exposure.

Encrypted secrets are stored in settings and injected into workflows at run time, and their values are masked in logs. Plain text files, YAML comments and issue comments expose the value.

Code scanning produces alerts for potential vulnerabilities, which can be triaged and tracked. Wiki edits, stars and release notes do not report security findings.

Passkeys and security keys are phishing-resistant second factors, which provide the strongest protection. Written passwords, shared accounts and disabled alerts weaken security.

Organization settings can require two-factor authentication for all members, which enforces the policy centrally. Personal profiles, READMEs and wiki requests depend on individual choice.

GitHub Copilot provides AI-assisted code suggestions and chat in supported editors. GitHub Pages hosts websites, Sponsors manages funding, and Gists store snippets.

Workflows are YAML files in .github/workflows and are triggered by events such as pushes and pull requests. They are not limited to manual merges or public repositories, and they are commonly used to run tests.

A workflow triggered by the issues event, with a condition on the label, automates the triage comment. Manual reminders, releases per issue and forks per bug do not automate triage.

A workflow triggered by the release or tag event builds and publishes the image automatically and consistently. Manual uploads, README changes and labels do not publish images.

Reusable workflows and composite actions let several repositories call shared logic, which keeps the steps consistent and easy to update. Manual copies drift, email is not a workflow mechanism, and laptop-only runs do not serve the organization.

The dependabot.yml configuration file defines which package ecosystems, including GitHub Actions, are checked and how often updates are proposed. The other files do not configure Dependabot.

Organizations group repositories and manage teams and permissions centrally, which suits a company. Individual accounts, shared passwords and gists do not provide centralized team management.

CODE_OF_CONDUCT.md sets behaviour expectations and CONTRIBUTING.md explains how to contribute and report issues. A licence, an ignore file and a tag do not provide that guidance.

Locking a conversation limits who can comment, which contains spam while keeping the record. Deleting the repository or the README and turning off organization notifications do not address the spam in that thread.

Repository roles such as maintain give the team operational rights on specific repositories without organization-wide authority. Owner status, shared passwords and billing access exceed the requirement.

GitHub Sponsors lets maintainers receive funding from the community. Issue templates, pull request labels and the Actions cache do not provide funding.

Setup instructions in the README and structured issue templates reduce guesswork and help contributors report useful information. Missing instructions, closing all issues and an unnamed default branch make contributions harder.