runbot/forwardport/models
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
..
__init__.py [ADD] runbot_merge: ~~tree~~ freeze wizard 2021-11-17 10:40:12 +01:00
forwardport.py [IMP] forwardport: automatically approve freeze backfills 2024-06-07 15:02:28 +02:00
project_freeze.py [FIX] runbot_merge: sync PR target and message on check 2023-01-25 12:25:45 +01:00
project.py [IMP] *: convert fw=no to a genuine forward-porting policy 2024-06-28 16:06:20 +02:00