xmo-odoo d042bc541f Better reporting of staging state ... * [ADD] runbot_merge: more informative states to stagings on error Currently, when a staging fails for other reasons than a CI failure: * the staging having been cancelled is known implicitly, because the staging will be deactivated but will never get a status beyond pending (because it's not found when looking for it since it's not `active`) * the fast-forward having failed is completely silent (logging aside), it looks for all the world like the staging succeeded Timeout fails the PR already, but split-on-timeout was not so fix that one bit. * [FIX] odoo/odoo#cb2862ad2a60ff4ce66c14e7af2548fdf6fc5961 Closes #41		2018-10-01 10:21:32 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	Better reporting of staging state	2018-10-01 10:21:32 +02:00
res_partner.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00