Xavier Morel 2fafd5419a [FIX] runbot_merge: attempt to stage PRs on disabled branches ... Normally opening a PR against a disabled branch is like opening a PR against a branch which is not configured at all: the PR id ignored entirely. However if the PR already exists then the state of the branch isn't normally checked when interacting with the branch, and it is possible to trigger its staging, at which point the staging itself will crash: on a project the branches are `active_test=False` so they're all visible in the form, but when repos go search()-ing for the branch they won't find it and will blow up. Solution: only try staging on branches which are active. Fixes odoo/runbot#408. Also do the same for checking stagings. And while at it, fix #409 by wrapping each checking or staging into a try/except and a savepoint. This way if a staging blows up it should move on to the next branch instead of getting stuck.		2020-10-02 15:28:36 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[FIX] runbot_merge: attempt to stage PRs on disabled branches	2020-10-02 15:28:36 +02:00
res_partner.py	[ADD] runbot_merge: allow overriding statuses	2020-07-14 13:34:05 +02:00