Xavier Morel c93ce7c2c2 [FIX] runbot_merge: blocked flag false positive ... The "blocked" computation would not take branch targets in account, so PRs with the same label targeting *different branches* (possible if somewhat rare due to our naming conventions) could block one another, despite really being unrelated. Also fix up some messages: * if a PR is blocked due to having no merge method, it should say that, not "has no merge" (no merge what?) * format un-managed branches as `$repo:$branch` in logging messages, `$repo#$thing` is for issues / PRs and `$branch` alone can be very unhelpful Closes #407		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: blocked flag false positive	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