Xavier Morel 6565a0f9a1 [FIX] runbot_merge: don't batch patch-X PRs across repos ... Normally, two PRs from the same owner with the same branch name (source) are batched together, and that's represented by batching them by label e.g. two PRs labelled `odoo-dev:12.0-snailmail-address-format-anp` means they probably should be merged together somehow. *However* this is an issue when editing via the web interface: if the editor doesn't have write access to the repository, github automatically createa a branch called `patch-<n>` under their ownership, where `<n>` is a sequence (of sorts?) *within the user's fork*. This means it's possible (and indeed easy) to create <foo>:patch-1 on different (non-forks) but related repositories without them actually being co-dependent, at which point they get blocked on one another, which can lead to them being blocked (period) due to runbot not currently handling co-dependencies between PRs.		2018-10-23 17:39:31 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[FIX] runbot_merge: don't batch patch-X PRs across repos	2018-10-23 17:39:31 +02:00
res_partner.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00