bors merge failures shouldn't cause a red X

Stream: general

[Scott Morrison]

When a batch of PRs fails in bors, it currently puts a red X against all the PRs, even though it's actually just retrying them in smaller batches.

I find this quite annoying, as it makes it hard to tell which PRs actually need attention!

I opened an issue about this on the bors-ng github repo a while back, but don't appear to have had any traction.

If anyone wants to add their +1 to that issue, please do. :-) (Even more amazing if someone wants to provide a patch. I added a comment on that issue with my best guess of where to start.)

[Adam Topaz]

What language is this?

[Bryan Gin-ge Chen]

Elixir. @Gabriel Ebner has gotten a few PRs merged into bors, I think.

[Gabriel Ebner]

Yes, it's quite approachable. Please give it a try!