How to improve your PR life cycle

So, what can we do here?

Four improvements come to mind:

1. Adding a precise context to every PR is crucial.
2. Adding separate field called e.g. Estimated Time to Review sounds like a good idea.
3. Assigning the right person to PR.
4. In case you use ChatOps, you can create a separate channel where your git tool sends notifications about PRs waiting for you.

One more thing about “Estimated Time to Review” – this one really works, especially when people are distracted by meetings, why? Let’s imagine you have an additional 25mins, because your last meeting has ended a bit earlier than intended. You are checking PRs list to review something, you notice that you can easily see time (estimated) needed for each review, and yes! Someone said that this PR needs just 15mins, okay, I am jumping into it to help.

As you can see without “Estimated Time to Review” you wouldn’t be able to do that as usually people assume more time for PRs.

Happy reviewing,

Łukasz.