What happens when you link an issue to a pull request?
Answer : E
Linking an issue to a pull request connects planned or reported work with the code change intended to resolve it. In GitHub workflows, this relationship helps maintainers track which pull request addresses a specific issue. When a pull request is linked in a way that closes the issue, such as through supported closing keywords or the development relationship, GitHub can automatically close the issue after the pull request is merged. This improves traceability and reduces manual cleanup after work is completed. Linking does not approve the pull request, because approval depends on review permissions and branch protection settings. It also does not lock the issue or automatically add the pull request to a project board. The main benefit is connecting work items to code changes.
Which of the following outcomes can be achieved with a branch protection rule?
Answer : B
Which of the following is the first step in the GitHub flow?
Answer : D
GitHub flow is a lightweight workflow used to safely introduce changes into a repository. The first step is to create a branch for your changes. A branch gives you an isolated workspace where you can develop a feature, fix a bug, or test an idea without directly affecting the main branch. After creating the branch, you make commits and push those changes. Then you open a pull request so others can review and discuss the work. Once the pull request is approved, it can be merged into the main branch. Deleting the branch happens only after the work has been merged and the branch is no longer needed. Therefore, branch creation comes first.
How is github.dev different than Codespaces?
Answer : D
For which of the following does GitHub provide hosted runners?
Answer : B
Which of the following statements is true regarding the mergeability of draft pull requests?
Answer : C
Which three files can a user automatically add while creating a new repository?
Answer : C