runbot/forwardport/tests
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
..
conftest.py [IMP] *: store filestore & forwardport checkouts in temp dirs 2022-08-05 15:35:51 +02:00
test_batches.py [REF] forwardport: update re_matches to not use a regex 2024-06-04 14:18:04 +02:00
test_conflicts.py [FIX] forwardport: don't break forward porting on huge conflicts 2024-06-25 15:54:23 +02:00
test_limit.py [IMP] *: convert fw=no to a genuine forward-porting policy 2024-06-28 16:06:20 +02:00
test_overrides.py [CHG] *: move forward-porting over to batches 2024-05-24 09:08:56 +02:00
test_simple.py [IMP] forwardport: don't ping *every* forwardport 2024-06-10 18:47:49 +02:00
test_updates.py [FIX] *: re-enable notification on status failure 2024-06-21 10:27:01 +02:00
test_weird.py [FIX] runbot_merge: followup detached PRs when disabling branches 2024-06-28 16:06:20 +02:00