runbot/runbot_merge/models
Xavier Morel 9de18de454 [CHG] *: move repo cache from forwardbot to mergebot
If the stagings are going to be created locally (via a git working
copy rather than the github API), the mergebot part needs to have
access to the cache, so move the cache over. Also move the maintenance
cron.

In an extermely minor way, this prefigures the (hopeful) eventual
merging of the ~~planes~~ modules.
2023-08-25 15:04:48 +02:00
..
crons [CHG] *: move repo cache from forwardbot to mergebot 2023-08-25 15:04:48 +02:00
project_freeze [FIX] runbot_merge: concurrency error in freeze wizard (hopefully) 2023-06-21 14:26:19 +02:00
staging_cancel [ADD] runbot_merge: stagings canceling wizard 2022-12-08 10:46:22 +01:00
__init__.py [CHG] *: move repo cache from forwardbot to mergebot 2023-08-25 15:04:48 +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: sentry instrumentation 2023-06-21 14:26:19 +02:00
pull_requests.py [IMP] runbot_merge: split staging heads out to join tables 2023-08-10 14:04:59 +02:00
res_partner.py [ADD] runbot_merge: remote user provisioning 2022-06-07 13:48:17 +02:00