Xavier Morel be4c8bd491 [FIX] runbot_merge: forcefully rollback ref after a failed rebase() ... rebase() can fail after merge(), during set_ref(), having already updated the target. Under the pre-rebase model, stage() assumed on a staging failure on a given repo it only had to rollback stagings having succeeded. This assumption fails in a post-rebase model as even a failed staging can have modified the target, leading to the next staging (if multiple batches are ready) containing the failed one. Things can get really strange if the set_ref failure was (as it probably is) some sort of transient failure, as the following staging will likely succeed (under the assumption that most PRs/batches pass staging) as PR1's content gets merged as part of PR2, and PR2 is merged empty of content later on.		2018-10-17 14:18:49 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[FIX] runbot_merge: forcefully rollback ref after a failed rebase()	2018-10-17 14:18:49 +02:00
res_partner.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00