Followup for the naive update-refs bot
Followup things to implement and figure out after !1795 (merged) and !1796 (merged) and !1825
The current behavior is that if the bot finds an MR from its account already open, it will abort and not update it or open a new merge request.
For example:
If there's an MR already opened that has failed, but nobody has commented or pushed to it other than the bot, it would be reasonable to git reset and force push. The problem would be how do we determine if we should open a new mr, force push to existing one or do nothing which needs some extra thought.
Edited by Jordan Petridis