Why fire-pr?

We spent more time reading code than writing code. Therefore it is important to have some kind of code review process so only the good code gets into the code base.

With this goal in mind, it is also important to have a nice experience when reviewing the code. This tool exists to make this easier. We can also save a lot of time designing the Pull Request.

Basically, it is an interface generating the markdown for the Pull Request description. It includes different Pull Request topics, to make it as easy as possible to review a code change.

This is done by preparing the reviewer with general information about the code change. An example can be found below which shows the interface of the extension and the output inside the description container of the Pull Request.

This is true. But since no interface for this existed yet, we decided to create it. We live the standard that there should be a tool for every use case and that engineers should interfacivize everything possible, to guarantee good developer experience.

This tool is opinionated in order to set a standard. Developers should not waste time on how they create Pull Requests. Rather they should just use the tool and make the best out of it. The project is open to discussion and maybe even configuration in the future.

This opinionated mindset also helps to create some kind of consistency between Pull Requests. This leads to new engineers understanding the reason behind a Pull Request a lot faster. They can grab testing instructions and test the code for it or see if the tests which are included in the Pull Request are fully testing the requirements. This consistency also gives developers also a feeling of security since they are used on how to deal with Pull Requests now.

Other tools like prettier are also opinionated and have enjoyed great success. To see why they are successful check out their site which explains why you should use it.