jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-30 12:02:01 -05:00
Code Issues Projects Releases Wiki Activity

Update about-rulesets.md (#44730)

Browse Source 
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
This commit is contained in:
Patrick Knight
2023-10-20 03:07:29 -05:00
committed by GitHub
parent b464e551e5
commit cc42a50160
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md
View File

@@ -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.