From ba2ba64833c9b367ecff106c5e89e4314ff448d9 Mon Sep 17 00:00:00 2001 From: Joel Dodge Date: Tue, 2 Jun 2026 06:40:55 -0700 Subject: [PATCH 1/2] Clarify navigation for push policy settings Updated navigation instructions for push policy settings. --- .../managing-the-push-policy-for-your-repository.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md index cf51b930fba3..fa8bcefbb2e8 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md @@ -26,7 +26,7 @@ The push policy also blocks the Git command: `git push --mirror`. This is a pote {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "Pushes", select **Limit how many branches and tags can be updated in a single push**. +1. Under "General -> Pushes", select **Limit how many branches and tags can be updated in a single push**. 1. After "Up to", type the number of branches and tags you want to limit in a single push. Lower numbers are more restrictive of which pushes are allowed, and higher numbers are less restrictive but have more potential for being destructive. We recommend the default maximum of `5` branch or tag updates allowed in one push. The minimum value is `2`, because Git requires two branch updates to rename a branch in a single push: _delete branch_ and _create branch_. From 6c0c070185022b260b83ec85f8ad8e85c8cb860f Mon Sep 17 00:00:00 2001 From: Joel Dodge Date: Tue, 2 Jun 2026 06:44:55 -0700 Subject: [PATCH 2/2] Update push policy instructions for clarity Clarified instructions for limiting branch and tag updates in a push. --- .../managing-the-push-policy-for-your-repository.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md index fa8bcefbb2e8..e3fb4c904b23 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md @@ -26,7 +26,7 @@ The push policy also blocks the Git command: `git push --mirror`. This is a pote {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "General -> Pushes", select **Limit how many branches and tags can be updated in a single push**. +1. In the "General" settings, under "Pushes", select **Limit how many branches and tags can be updated in a single push**. 1. After "Up to", type the number of branches and tags you want to limit in a single push. Lower numbers are more restrictive of which pushes are allowed, and higher numbers are less restrictive but have more potential for being destructive. We recommend the default maximum of `5` branch or tag updates allowed in one push. The minimum value is `2`, because Git requires two branch updates to rename a branch in a single push: _delete branch_ and _create branch_.