GH-900 · Question #58
You have forked a public GitHub repository, made changes in a new branch, and now want the original repository maintainers to review and possibly merge your updates. Which GitHub feature should you…
The correct answer is C. Open a Pull Request to submit your changes for review and potential mergingright. A pull request (PR) is the standard way to propose changes in GitHub, allowing repository maintainers to review your modifications, discuss them, and merge them into the main codebase if approved. It provides a structured approach to collaboration, ensuring transparency and…
Question
You have forked a public GitHub repository, made changes in a new branch, and now want the original repository maintainers to review and possibly merge your updates. Which GitHub feature should you use to formally propose your changes for review and integration into the main codebase?
Options
- ACreate an Issue and describe the changes you've made
- BOpen a Discussion to announce your code update
- COpen a Pull Request to submit your changes for review and potential mergingright
- DTag the repository owner in a comment within your forked repository
How the community answered
(58 responses)- A2% (1)
- B3% (2)
- C90% (52)
- D5% (3)
Explanation
A pull request (PR) is the standard way to propose changes in GitHub, allowing repository maintainers to review your modifications, discuss them, and merge them into the main codebase if approved. It provides a structured approach to collaboration, ensuring transparency and review before integration Option C is CORRECT because a Pull Request (PR) is used to propose code changes, request reviews, and suggest merging those changes into the target branch of the original repository. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to- your-work-with-pull-requests/about-pull-requests
Topics
Community Discussion
No community discussion yet for this question.