What is typically created in a Git repository to have changes reviewed by peers?

In a Git repository, a pull request serves as a mechanism for requesting the merging of changes from one branch into another, typically from a feature branch into the main branch. The pull request is not just a formal request; it also provides a platform for code review, discussion, and collaboration among team members. When a developer finishes work on a new feature or bug fix in a separate branch, they create a pull request to notify others that the code is ready for review.

This mechanism allows peers to examine the proposed changes, add comments, suggest improvements, and ensure that the code adheres to the team's quality standards before it gets merged into the main codebase. After review, if there are no significant issues, the changes can be approved and merged.

The other options reflect different aspects of workflow in Git but do not specifically relate to the peer review process. A feature branch refers to a separate branch created to develop a specific feature, a merge request is a term used in some Git platforms similar to pull requests, and a hotfix pertains to a quick fix for a critical bug in the production environment. However, the specific term used widely for requesting review and discussion on changes is the pull request.