Clarify navigation for push policy settings#44560
Conversation
Updated navigation instructions for push policy settings.
There was a problem hiding this comment.
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**. |
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 linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Clarified instructions for limiting branch and tag updates in a push.
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: