runbot/runbot_merge/models
Xavier Morel de32b54090 [FIX] runbot_merge: error in maintenance, and tracking
Before this, we would check if a repository had a name and run
maintenance on it, leading to repeated (but unnoticed until now
because I didn't monitor it) tracebacks as the maintenance cron would
fail to find the local repo then run maintenance on nowhere anyway.

Also augment the repo-finding process to try and get better
information about what it's doing when it fails, rather than failing
completely silently.
2024-02-23 13:58:31 +01:00
..
crons [FIX] runbot_merge: error in maintenance, and tracking 2024-02-23 13:58:31 +01:00
project_freeze [FIX] runbot_merge: rebase logging 2024-01-16 09:53:57 +01:00
staging_cancel [ADD] runbot_merge: stagings canceling wizard 2022-12-08 10:46:22 +01:00
__init__.py [MOV] runbot_merge: all the staging creation code to a separate module 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 [FIX] runbot_merge: bot info fetch 2024-02-12 10:18:59 +01:00
pull_requests.py [ADD] runbot_merge: delete scratch branches when a branch is disabled 2023-08-31 09:07:01 +02:00
res_partner.py [ADD] runbot_merge: remote user provisioning 2022-06-07 13:48:17 +02:00
stagings_create.py [FIX] runbot_merge: rebase logging 2024-01-16 09:53:57 +01:00