This has come up several times in our organization. We have some sort of emergency outage, or an organization wide code freeze. (For instance, over the Thanksgiving holiday) We rely on Slack/email to communicate that we're in a code freeze, and that no one should merge code - but we'd really like a programmatic way to enforce this.
So my ideal feature would be a way to specify for a particular protected branch that merging is disabled. It could be very simple: just an option that says "Disable merges" with an optional reason field that would be displayed on all PRs next to the merge button. This would let us communicate "Site is down - do not merge until given the all clear" or "Code is frozen until Monday 11/27", etc.
This would go a huge way toward letting us control our changes better. Getting fancier, you might want to support an "exclude list", so the protection becomes "no one can merge except these users" to allow emergency fixes.
Thoughts? Is this the kind of functionality that others would find useful?
For now, the best way to submit bug reports or feature requests is via our contact page (github.com/contact). GitHub Staff working in the Forum will see and respond to those requests there.
That said, I do want to share that we are working on a new tool and process for submitting these sorts of things for the Community Forum (and for github.com). This is still in the investigative stage, and I don't have a timeline to share, but we are planning on improving this process.
We also recognize the desire for feature requests to be visible to other users, commented on, and even voted on. These are all things that we are taking into consideration when looking at implementing a new process.
Thank you so much for the feedback! I'll be locking this thread from further replies, and I encourage you to send your feature request via the contact form linked above.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!