Github Foundations · Free Practice Question Medium
Question 15
You are reviewing proposed changes in a pull request in the GitHub UI. What options are available to you in order to evaluate the pull request and make a decision to approve it or not? (select five)
-
A
review the commits included in the pull request using the Commits tab
-
B
validate that the proposed changes fix the related issue linked to the pull request in the Security tab
-
C
compare the differences between the files in the base and compare branches in the Files Changed tab
-
D
provide inline comments on the changes proposed in the pull request in the Files Changed tab
-
E
ensure the pull request has passed the required checks in the Checks tab
-
F
view discussions related to the pull request in the Conversation tab
Reveal correct answers
Correct answers: A, C, D, E, F
Explanation
You can review changes in a pull request one file at a time. While reviewing the files in a pull request, you can leave individual comments on specific changes. After you finish reviewing each file, you can mark the file as viewed. This collapses the file, helping you identify the files you still need to review. A progress bar in the pull request header shows the number of files you've viewed. After reviewing as many files as you want, you can approve the pull request or request additional changes by submitting your review with a summary comment.
********************
WRONG ANSWER:
GitHub pull request doesn't have a Security tab, nor does GitHub validate that the proposed changes will properly address the issue linked to the PR.
A. Reviewing the commits included in the pull request using the Commits tab allows you to see the history of changes made to the code, providing insight into the development process and the rationale behind the proposed changes.
B. Validating that the proposed changes fix the related issue linked to the pull request in the Security tab is not a valid option in the GitHub UI for evaluating and making decisions on pull requests. This tab is typically used for security-related features and may not be relevant for code review.
C. Comparing the differences between the files in the base and compare branches in the Files Changed tab allows you to see the exact modifications made in the code, helping you assess the impact of the changes and ensure they align with the project requirements.
D. Providing inline comments on the changes proposed in the pull request in the Files Changed tab allows you to give specific feedback, suggestions, or corrections directly on the code, facilitating communication and collaboration with the author of the pull request.
E. Ensuring the pull request has passed the required checks in the Checks tab is crucial for verifying that the proposed changes meet the project's quality standards, such as passing automated tests, code reviews, and other validation processes.
F. Viewing discussions related to the pull request in the Conversation tab enables you to see any comments, questions, or feedback from team members or collaborators, helping you understand the context and potential issues with the changes.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
