Restrict review dismissals with protected branches
There’s a new way to reinforce your team’s code reviews. Now you can specify who in your organization can dismiss reviews on a protected branch. In the last year, we’ve…
There’s a new way to reinforce your team’s code reviews. Now you can specify who in your organization can dismiss reviews on a protected branch.
In the last year, we’ve been updating pull requests with features that help teams give feedback and make sure only the highest quality code makes it into their projects. You can leave, manage, request, and dismiss reviews, as well as protect branches and limit merging rights. With restricted review dismissals, you can also ensure important feedback gets addressed.
Completely remove the ability to dismiss reviews on a protected branch or restrict that ability to a subset of users or teams specified in your branch protection settings for any organization repository.
Written by
Related posts
Developer policy update: Transparency, state policy, and what’s ahead
Explore GitHub’s latest transparency data and learn more about policy updates affecting developers and open source.
Developers want more efficient software. Here’s what over 1,000 GitHub users told us they need.
New research from GitHub and Yale Program on Climate Change Communication finds strong demand for tools, measurement, and practical guidance that can help developers reduce wasted compute.
GitHub availability report: August 2026
In August, we experienced five incidents that resulted in degraded performance across GitHub services.