From 46cd4cc931c595da34043772b9046606b90ecc1a Mon Sep 17 00:00:00 2001 From: Patrick Knight Date: Fri, 22 Nov 2024 11:12:35 -0600 Subject: [PATCH] Update troubleshooting-rules.md (#53187) Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com> --- .../managing-rulesets/troubleshooting-rules.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md index f4f6cd092474..4774988fda2f 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md @@ -17,6 +17,8 @@ Depending on which rules are active, you may need to edit your commit history lo If a branch or tag is targeted by rules restricting the metadata of commits, your commits may be rejected if part of the commit's metadata does not match a certain pattern. For example, you might need to add an issue number to the start of your commit message, or change the name of a new branch or tag you're trying to push to the repository. If your commits are rejected, you will see a message telling you the pattern the relevant metadata needs to match. As with signed commits, you may need to perform a rebase to squash the commits or rewrite each commit individually. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#metadata-restrictions)." +When utilizing push rulesets, a maximum of 1000 reference updates are allowed per push. If your push exceeds this limit, it will be rejected. For more information see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#creating-a-push-ruleset)". + {% ifversion repo-rules-required-workflows %} ## Troubleshooting ruleset workflows