If you ever tried to get developers to fill out a pull request description template, or at least write something in the description, you’d want this.
Creating a PR description template as you know is the easy part.
Sometimes people are just too busy to bother filling it out. Or they forget.
Because there isn’t an easy way for you to enforce the template, you probably end up having to remind them in person or during code reviews.
Datree’s new pull request description policy solves this problem. You can:
As always, Datree will tell you why your PR failed the check:
Want to start using this rule? Go to Docs for step-by-step instruction.
Developers spend a lot of time working with git and GitHub, so investing in improving your GitHub practices makes a lot of sense. Implementing best practices in this guide could help the team improve developer productivity and reduce security risks.
Best practices for writing git commit messages - cheatsheet included. Read how to optimize git commit messages to improve your development productivity.