runbot/runbot_merge/models
Xavier Morel 3191c44459 [ADD] runbot_merge: synthetic batches & stagings to freeze wizard
Merged PRs should have a batch which should have a staging, this makes
the treatment uniform across the board and avoids funky data which is
hard to place or issues when reconstructing history.

Also create synthetic batches & stagings for older freezes (and bumps)
2024-05-29 07:55:07 +02:00
..
crons [FIX] runbot_merge: maintenance gc command 2024-02-26 09:58:22 +01:00
project_freeze [ADD] runbot_merge: synthetic batches & stagings to freeze wizard 2024-05-29 07:55:07 +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] *: don't remove PRs from batches on close 2024-05-29 07:55:07 +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 [CHG] *: move forward-porting over to batches 2024-05-24 09:08:56 +02:00
pull_requests.py [IMP] *: don't remove PRs from batches on close 2024-05-29 07:55:07 +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: preserve batch ordering in stagings 2024-05-29 07:55:07 +02:00
utils.py [CHG] runbot_merge: move priority field from PR to batch 2024-05-23 07:58:58 +02:00