Common workflow:
* Developer finishes code on their local machine
* Developer opens PR
* Developer adds reviewers
* CI build fails
* Reviewers open PR and CI build is red. Close tab.
* Developer fights CI over and over until it's green
* Developer needs to ask reviewers (after a delay) to review the PR
It's a bit unproductive (and there's the human aspect to this all).
Would it be possible to restrict adding reviewers until X number of builds have passed?
Hi Giovanni,
Thanks for the suggestion!
I'm not sure we would implement this improvement exactly as suggested, but we are looking into the broader problem of "how do I signal to reviewers that my code is ready for review?" which this falls into.
For now, I suggest shifting your workflow to the branch list page -- that way you can see when your branch's builds are green, and then create a PR.
Alastair
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.