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

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more