GH-900

GitHub links a pull request to an issue when its description or commit message uses one of the supported keywords: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved, followed by the issue reference. So fix, resolves and closed all work. Merge, join and connects are not recognized keywords and do not create a link.

Saved replies are reusable comment text, and like other comments on GitHub they are written in GitHub Flavored Markdown. The documentation for creating a saved reply points to the Markdown basic writing and formatting syntax. HTML is not the authoring syntax, YAML is used for configuration files such as workflows and issue forms, and Markup is not a GitHub authoring syntax.

A pull request proposes changes from one branch to another, lets collaborators review them, and is where the changes are merged. Discussions are for conversations, projects are for planning and tracking work, and issues track bugs, tasks and ideas; none of them merges code.

When a repository contains more than one README, GitHub picks the one to display in this order: the .github directory, then the repository's root directory, and finally the docs directory. So a README in .github takes precedence over one in the root. A README in src is not surfaced on the repository's main page at all.

A branch lets you develop features, fix bugs or experiment in isolation, so work on one branch does not affect the default branch or others until it is merged. Branches do not merge automatically, they are lightweight pointers to commits rather than physical copies of the project, and they are not how files and folders are organized.

Git is a distributed version control system, used mainly from the command line, that tracks changes to files. GitHub is a cloud platform that hosts Git repositories and adds collaboration features such as pull requests, issues and Actions. They are not the same tool, option C reverses the roles, and Git is distributed rather than centralized.

Git is distributed: every clone holds the full repository history, so committing, branching, viewing history and diffing all happen locally and work offline. Git has no real-time co-editing, is not a cloud service, and is not tied to web or browser-based development.

GitHub is a hosting and collaboration platform for Git repositories, so it is built on Git. Subversion, Mercurial and Perforce are other version control systems that GitHub does not use as its underlying system.

git checkout -b newBranchName creates the branch and checks it out in a single step (git switch -c does the same in newer Git versions). git branch newBranchName only creates the branch and leaves you on the current one. git checkout newBranchName switches to a branch that already exists, and -n is not a branch-creation option of git checkout.

GitHub Enterprise Server is self-hosted: the organization runs the appliance in its own data center or cloud account and controls the infrastructure, while GitHub Enterprise Cloud is hosted by GitHub. SAML single sign-on and SCIM provisioning are available on both, so they are not a difference. GHES runs as a virtual appliance on supported hypervisors and cloud platforms rather than being installed on Windows or Linux, and administrators can configure rate limits on GHES.

The github.com/codespaces page lists all your active and stopped codespaces, and selecting one reopens it. On a repository page, pressing the comma key opens the Resume codespace page, where Resume this codespace reopens your most recent codespace for that branch. Pressing the period key opens the github.dev web editor, not a codespace, and codespaces are managed with the GitHub CLI (gh codespace), not a git codespace command.

Issues track ideas, feedback, tasks and bugs, and are a place to discuss and share information; they do not push any code. Pull requests propose the changes made on a branch so collaborators can review and discuss them before they are merged. Projects are planning boards that organize issues and pull requests, not something pull requests change.

The Development section in the right sidebar of a pull request (and of an issue) lets you manually link a pull request to an issue. Assignees only sets who is responsible for the work. Mentioning a pull request in an issue comment or description creates a cross-reference, not a linked pull request; automatic linking uses closing keywords in the pull request description.

Alpha (now called private preview) features are offered only to a limited set of users for demonstration and testing, so they are not available to the public. Neither alpha nor beta (public preview) features carry SLAs or technical support obligations; those apply only at general availability. Alpha features may lack documentation, so documentation is not guaranteed.

github.dev opens the repository in a browser-based VS Code editor instantly (press the period key on any repository page), with no installation or configuration, and lets you edit many files, stage them all and commit them together. GitHub Desktop and the git CLI must be installed and the repository cloned first, which is not the quickest path. A codespace can take a few minutes to create because it provisions a virtual machine for building and running code, and GitHub Mobile is not designed for editing files.

GitHub comments, issues, pull request descriptions and wikis are written in GitHub Flavored Markdown, which supports headings, lists, links, code blocks, mentions and more. JSON, JavaScript, XML and CSS can appear inside a fenced code block, but they are not the formatting language of comments.

The issues list offers built-in default filters so you can narrow results without typing search qualifiers: open issues and pull requests, those you created (your issues), those assigned to you, and those where you are @mentioned. There is no default filter for a project, for items assigned to your team, or for items you commented on; those need qualifiers such as project:, team: or commenter:.

Achievements are badges shown on a GitHub profile that recognize particular actions and milestones on GitHub, such as merging pull requests, co-authoring commits or contributing to projects. They are not counts of repositories or stars, which appear elsewhere on the profile, and they are not awarded for completing coding challenges.

Git records history as snapshots in time called commits: each commit captures the state of all tracked files in the project at that moment, like taking a photo. A commit is not just the latest changes or a series of changes, and the commit message is only one part of a commit that describes it.

The mentions: qualifier finds issues that mention a certain user, for example mentions:defunkt. GitHub search has no threads:, mentioned: or @mentioned: qualifier. The related involves: qualifier is broader, matching the author, assignee, mentions or commenter.