Skip to main content

GitHub–Disable required reviews for pull requests

I’m working on a (small) open source application where I’m currently the only contributor. I setup the project so that the main branch is protected by a branch protection rule.

By using branch protection rules, you can enforce certain workflows or requirements before someone can push changes to a branch, including merging a pull request into the branch. You can view the active branch protection rules by going to Settings –> Branches (available in the Code and automation section):

In my case I had setup a rule that required a pull request before merging son that I could track and iterate on changes in separate branches.  To see the specific branch rule, click on Edit next to the branch:

I liked the pull request model for this application but as a default GitHub also configured that an approval was required by at least one reviewer.

This is great if you are working with multiple contributors on a project but as I was working mostly alone on it, requiring such a review no longer made sense.

The good news is that you can easily disable it by unchecking the Require approvals checkbox:

This allows you to still use pull requests but removes the approval step as a requirement before being able to merge.

Remark: Notice that I’m still using the status checks to do some automated validation.

More information

Require pull requests without requiring reviews - GitHub Changelog

About protected branches - GitHub Docs

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.