Xavier Morel 87948ef575 [IMP] runbot_merge: inline stage_into, remove working copy ... Turns out we can (most likely) do all the work in the local main repo directly, so there is no need for the separate working copy, or the exist stack, and thus no need for a separate function to be context-managed. Should have yagni'd and waited to setup the working copy stuff... oh well.		2023-08-22 14:23:51 +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	[ADD] runbot_merge: github identity for the mergebot	2023-08-22 08:04:46 +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	[IMP] runbot_merge: inline stage_into, remove working copy	2023-08-22 14:23:51 +02:00