Skip to content

Commit 8fb1528

Browse files
authored
Merge pull request #13789 from github/repo-sync
repo sync
2 parents 3f3b9b0 + 85f9e42 commit 8fb1528

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests

content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ By default, protected branch rules do not apply to people with admin permissions
153153
You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
154154
{% endif %}
155155

156-
When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings.
156+
When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
157157

158158
You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch.
159159

0 commit comments

Comments
 (0)