Skip to content

Repo sync #29305

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 20, 2023
Merged

Repo sync #29305

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
767fe68
Merge pull request #44736 from github/repo-sync
docs-bot Oct 20, 2023
b464e55
Merge pull request #44737 from github/repo-sync
docs-bot Oct 20, 2023
cc42a50
Update about-rulesets.md (#44730)
patrick-knight Oct 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...ring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ For each ruleset you create, you specify which branches or tags in your reposito

When you create a ruleset, you can allow certain users to bypass the rules in the ruleset. This can be users with a certain role, such as repository administrator, or it can be specific teams or {% data variables.product.prodname_github_apps %}.

There is a limit of 75 rulesets per repository{% ifversion repo-rules-enterprise %}, and 75 organization-wide rulesets{% endif %}.

## About rulesets, protected branches, and protected tags

Rulesets work alongside any branch protection rules and tag protection rules in a repository. Many of the rules you can define in rulesets are similar to protection rules, and you can start using rulesets without overriding any of your existing protection rules.
Expand Down