Monitor Repository Activity – Track pushes to ensure compliance and adjust limits if needed. #205114
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
Set a Maximum Update Limit – Restrict the number of branches and tags that can be updated in a single push (for example, a maximum of 5 updates).
Use Pre-Receive Hooks – Configure server-side hooks to reject pushes that exceed the allowed number of branch or tag updates.
Enforce via CI/CD Policies – Integrate checks within your CI/CD pipeline to enforce this limit before accepting the push.
Provide Contributor Guidelines – Inform developers of the push limit and encourage smaller, more frequent updates.
Monitor Repository Activity – Track pushes to ensure compliance and adjust limits if needed.
All reactions