Xavier Morel 94cf3e9647 [IMP] *: convert fw=no to a genuine forward-porting policy ... After seeing it be used, I foresee confusion around the current behaviour (where it sets the limit), as one would expect the `fw=` flags to affect one another when it looks like that would make sense e.g. no/default/skipci/skipmerge all specify how to forward port, so `fw=default` not doing anything after you've said `fw=no` (possibly by mistake) would be fucking weird. Also since the author can set limits, allow them to reset the fw policy to default (keep skipci for reviewers), and for @d-fence add a `fw=disabled` alias. Fixes #902		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	[IMP] *: convert fw=no to a genuine forward-porting policy	2024-06-28 16:06:20 +02:00
tests	[IMP] *: convert fw=no to a genuine forward-porting policy	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