Skip to content

Clarify navigation for push policy settings#44560

Open
rollyjoel wants to merge 2 commits into
github:mainfrom
rollyjoel:patch-1
Open

Clarify navigation for push policy settings#44560
rollyjoel wants to merge 2 commits into
github:mainfrom
rollyjoel:patch-1

Conversation

@rollyjoel
Copy link
Copy Markdown

Updated navigation instructions for push policy settings.

Why:

current docs wrong, had to find this post to even find the setting.

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

Updated navigation instructions for push policy settings.
Copilot AI review requested due to automatic review settings June 2, 2026 13:42
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates documentation to clarify the location of the "Pushes" setting within the repository settings UI.

Changes:

  • Adds "General ->" prefix to the "Pushes" section reference to clarify navigation path

{% 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**.
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 2, 2026

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-push-policy-for-your-repository.md fpt
ghec
ghes@ 3.21 3.20 3.19 3.18 3.17 3.16
fpt
ghec
ghes@ 3.21 3.20 3.19 3.18 3.17 3.16

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jun 2, 2026
Clarified instructions for limiting branch and tag updates in a push.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants