How are commits related to pull requests?

Commits and pull requests (PRs) are fundamental concepts in Git and GitHub workflows, particularly

in collaborative software development.

Commits:

Commits are individual changes or updates made to the codebase. Each commit is identified by a

unique SHA-1 hash and typically includes a commit message describing the changes.

Commits are made to a specific branch in the repository. The branch could be the main branch, or

more commonly, a feature branch created for specific work or a feature.

Pull Requests (PRs):

A pull request is a mechanism for developers to notify team members that a branch is ready to be

merged into another branch, usually the main branch.

PRs are used to review code, discuss changes, and make improvements before the branch is merged

into the target branch.

Relationship Between Commits and PRs:

Option A is correct because commits are made on a branch, and this branch can have a pull request

associated with it. The pull request tracks the branch’s commits and allows for code review before

merging into the target branch.

Commits can be added to the branch both before and after the pull request is created. Any new

commits pushed to the branch are automatically included in the pull request.

Incorrect Options:

Option B is incorrect because commits can be made both before and after a pull request is created.

Option C is incorrect because it suggests that commits can only be made before a pull request is

created, which is not true.

Option D is incorrect because commits are not made on a pull request; they are made on a branch.

The pull request links a branch to another branch (e.g., feature branch to the main branch).

Reference:

GitHub Documentation: About Pull Requests

GitHub Docs: Understanding the GitHub Flow

Git Documentation: Git Basics - Getting a Git Repository