runbot/runbot_merge/models
Xavier Morel f97502e503 [IMP] runbot_merge: make skipchecks impact PR state
It's a bit weird and inconsistent to have a PR being staged while
unreviewed or unapproved or w/e. If we compute the state based on
skipchecks then everything is consistent.

Also remove the implicit override of all statuses when explicitly
marking the pr as `ready`, it risks creating difficult to understand
states, and it's unnecessary since `skipchecks` gets set.

Also as with setting skipchecks, sets the current user as reviewer on
all PRs of the batch without a reviewer.
2024-05-24 09:08:56 +02:00
..
crons [FIX] runbot_merge: maintenance gc command 2024-02-26 09:58:22 +01:00
project_freeze [CHG] runbot_merge: move staging readiness to batch 2024-05-23 07:58:58 +02:00
staging_cancel [ADD] runbot_merge: stagings canceling wizard 2022-12-08 10:46:22 +01:00
__init__.py [CHG] *: persistent batches 2024-05-23 07:58:58 +02:00
batch.py [IMP] runbot_merge: make skipchecks impact PR state 2024-05-24 09:08:56 +02:00
commands.py [FIX] runbot_merge: handling of staging cancellation 2024-05-23 07:58:58 +02:00
ir_actions.py [IMP] runbot_merge: add json & requests to server actions context 2023-02-20 10:13:05 +01:00
project.py [ADD] runbot_merge: support staging ready PRs over splits 2024-05-23 07:58:58 +02:00
pull_requests.py [IMP] runbot_merge: make skipchecks impact PR state 2024-05-24 09:08:56 +02:00
res_partner.py [ADD] runbot_merge: ad-hoc ACL tracking to res.partner 2024-05-16 09:32:03 +02:00
stagings_create.py [IMP] runbot_merge: fix dual merge of split prioritised PRs 2024-05-23 07:58:58 +02:00
utils.py [CHG] runbot_merge: move priority field from PR to batch 2024-05-23 07:58:58 +02:00