From cc42a501609f90f37451d30f0bc0f72d2b200969 Mon Sep 17 00:00:00 2001 From: Patrick Knight Date: Fri, 20 Oct 2023 03:07:29 -0500 Subject: [PATCH] Update about-rulesets.md (#44730) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../managing-rulesets/about-rulesets.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md index 0653ef955d79..6e0f88fe62e3 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md @@ -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.