runbot/runbot_merge/models
Xavier Morel 747162d6e1 [CHG] runbot_merge: switch staging from github API to local
It has been a consideration for a while, but the pain of subtly
interacting with git via the ignominous CLI kept it back. Then ~~the
fire nation attacked~~ github got more and more tight-fisted (and in
some ways less reliable) with their API.

Staging pretty much just interacts with the git database, so it's both
a facultative github operator (it can just interact with git directly)
and a big consumer of API requests (because the git database endpoints
are very low level so it takes quite a bit of work to do anything
especially when high-level operations like rebase have to be
replicated by hand).

Nota: it might be a good idea to use pygit2 instead of the CLI, the
library seems to be typed and might allow doing the processing we need
on a bare repository directly. Which we can do via the plumbing
commands anyway, but still.

Fixes #247
2023-08-18 13:51:18 +02:00
..
crons [CHG] *: move repo cache from forwardbot to mergebot 2023-08-16 14:37:28 +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 [MOV] runbot_merge: all the staging creation code to a separate module 2023-08-18 13:07:51 +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 [MOV] runbot_merge: all the staging creation code to a separate module 2023-08-18 13:07:51 +02:00
pull_requests.py [MOV] runbot_merge: all the staging creation code to a separate module 2023-08-18 13:07:51 +02:00
res_partner.py [ADD] runbot_merge: remote user provisioning 2022-06-07 13:48:17 +02:00
stagings_create.py [CHG] runbot_merge: switch staging from github API to local 2023-08-18 13:51:18 +02:00