Xavier Morel 318803d7bb [IMP] runbot_merge: tag PRs with a pseudo-branch on merge to master ... If a PR got merged to master (or whatever the current development branch is), there's no easy way to know what maintenance branch it ended up landing in, except by asking git which branches contain the commit (which can be rather slow). Add a special case on merge which labels the PR with a pseudo-branch patterned after the second-to-last branch of the project: * if the branch ends with a number, increment the number by one e.g. 2.0 -> 2.1, 5 -> 5.1 * otherwise, just prefix with `post-` e.g. "maint" -> "post-maint" (that one doesn't sound very helpful, but I guess it's nice for the weirdoes who call their branches "natty narwhal" and shit) Fixes #450		2021-03-02 14:28:32 +01:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[IMP] runbot_merge: tag PRs with a pseudo-branch on merge to master	2021-03-02 14:28:32 +01:00
res_partner.py	[IMP] runbot_merge: overridable CI	2020-11-20 07:41:54 +01:00