Merge branch 'main' into fix/#14959
This commit is contained in:
Ethan Palm
@@ -38,10 +38,20 @@ People with write permissions to a repository can enable auto-merge for a pull r
|
||||
|
||||
1. Click **Enable auto-merge**.
|
||||
|
||||
{% ifversion fpt %}
|
||||
1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** The email dropdown menu is not available if you have email privacy enabled or if you only have one verified and visible email associated with your {% data variables.product.company_short %} account.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% ifversion ghes > 3.0 or ghae or ghec %}
|
||||
1. If you chose the merge or squash and merge methods, type a commit message and description.
|
||||
|
||||
{% endif %}
|
||||
1. Click **Confirm auto-merge**.
|
||||
|
||||
|
||||
## Disabling auto-merge
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ topics:
|
||||
---
|
||||
## About reverting a pull request
|
||||
|
||||
Reverting a pull request on {% data variables.product.product_name %} creates a new pull request that contains one revert of the merge commit from the original merged pull request.
|
||||
Reverting a pull request on {% data variables.product.product_name %} creates a new pull request that contains one revert of the merge commit from the original merged pull request. To revert pull requests, you must have [write permissions](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) in the repository.
|
||||
|
||||
## Reverting a pull request
|
||||
|
||||
@@ -33,6 +33,6 @@ For more information about using Git to manually revert individual commits, see
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
2. In the "Pull Requests" list, click the pull request you'd like to revert.
|
||||
3. Near the bottom of the pull request, click **Revert**.
|
||||
3. Near the bottom of the pull request, click **Revert**. If the **Revert** option isn't displayed, you'll need to ask the repository administrator for write permissions.
|
||||
|
||||
4. Merge the resulting pull request. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)."
|
||||
|
||||
@@ -15,6 +15,7 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
---
|
||||
|
||||
## About pull requests
|
||||
|
||||
{% note %}
|
||||
@@ -31,7 +32,7 @@ After initializing a pull request, you'll see a review page that shows a high-le
|
||||
|
||||
Once you've created a pull request, you can push commits from your topic branch to add them to your existing pull request. These commits will appear in chronological order within your pull request and the changes will be visible in the "Files changed" tab.
|
||||
|
||||
Other contributors can review your proposed changes, add review comments, contribute to the pull request discussion, and even add commits to the pull request.
|
||||
Other contributors can review your proposed changes, add review comments, contribute to the pull request discussion, and even add commits to the pull request. {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. For more information, see "[Viewing deployment activity for a repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)."
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Requesting a pull request review
|
||||
intro: 'After you create a pull request, you can ask a specific person to review the changes you''ve proposed. If you''re an organization member, you can also request a specific team to review your changes.'
|
||||
product: '{% data reusables.gated-features.multiple-pr-reviewers %}'
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review
|
||||
- /articles/requesting-a-pull-request-review
|
||||
@@ -28,9 +29,9 @@ Owners or collaborators can assign a pull request review to any person that has
|
||||
You can request a review from either a suggested or specific person. Suggested reviewers are based on [git blame data](/articles/tracking-changes-in-a-file/). If you request a review, other people with read access to the repository can still review your pull request. Once someone has reviewed your pull request and you've made the necessary changes, you can re-request review from the same reviewer. If the requested reviewer does not submit a review, and the pull request meets the repository's [mergeability requirements](/articles/defining-the-mergeability-of-pull-requests), you can still merge the pull request.
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
2. In the list of pull requests, click the pull request that you'd like to ask a specific person or a team to review.
|
||||
3. Navigate to **Reviewers** in the right sidebar.
|
||||
4. To request a review from a suggested person under **Reviewers**, next to their username, click **Request**.
|
||||
1. In the list of pull requests, click the pull request that you'd like to ask a specific person or a team to review.
|
||||
2. Navigate to **Reviewers** in the right sidebar.
|
||||
3. To request a review from a suggested person under **Reviewers**, next to their username, click **Request**.
|
||||
|
||||
5. Optionally, to request a review from someone other than a suggested person, click **Reviewers**, then click on a name in the dropdown menu.
|
||||
|
||||
|
||||
@@ -19,6 +19,8 @@ shortTitle: About PR reviews
|
||||
|
||||
After a pull request is opened, anyone with *read* access can review and comment on the changes it proposes. You can also suggest specific changes to lines of code, which the author can apply directly from the pull request. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)."
|
||||
|
||||
{% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %}
|
||||
|
||||
Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." {% ifversion fpt or ghae or ghes or ghec %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %}
|
||||
|
||||
Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)."
|
||||
|
||||
Reference in New Issue
Block a user