Xavier Morel 0206d5f977 [FIX] runbot_merge: followup detached PRs when disabling branches ... Although the handling of forward ports on disabled branch was improved in 94fe0329b4 in order to avoid losing or needing to manually port such, because it goes through `_schedule_fw_followup` some of the tests *that* performs were missed, most notably that it only ports batches when no PRs are detached. This is an issue if we need to force the port because of a branch being deactivated: the forward-port could have stopped there due to a conflict, in which case it's always going to be detached. Thus the `force_fw` flag should also override the parenting state check. Also while at it make `force_fw` a regular flag, I don't understand why I made it into a context value in the first place, it's only passed from one location and that's directy calling the one function which uses it... Fixes #897		2024-06-28 16:06:20 +02:00
..
changelog	[ADD] *: changelog entries I forgot	2023-08-14 09:28:19 +02:00
data	[FIX] forwardport: count next to users should be the fwport	2024-06-28 08:18:34 +02:00
migrations	[CHG] *: rewrite commands set, rework status management	2024-05-23 07:58:46 +02:00
models	[FIX] runbot_merge: followup detached PRs when disabling branches	2024-06-28 16:06:20 +02:00
tests	[FIX] runbot_merge: followup detached PRs when disabling branches	2024-06-28 16:06:20 +02:00
__init__.py	[ADD] mergebot, forwardbot: changelog	2021-10-20 15:16:48 +02:00
__manifest__.py	[CHG] *: rewrite commands set, rework status management	2024-05-23 07:58:46 +02:00
controllers.py	[FIX] forwardport: count next to users should be the fwport	2024-06-28 08:18:34 +02:00