Xavier Morel 327500bc83 [FIX] runbot_merge: don't notify on closing unknown PRs ... If an untracked PR is closed, especially on an inactive or untracked branch, the closer (or author) almost certainly don't care to receive 3 different notifications on the subject. The fix requires a schema change in order to track that we're fetching the PR due to a `closed` event, as in other cases we may still want to notify the user that we received the request (and it just happened to resolve to a closed PR). Fixes #857		2024-03-12 12:17:30 +01:00
..
crons	[FIX] runbot_merge: maintenance gc command	2024-02-26 09:58:22 +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	[FIX] runbot_merge: don't notify on closing unknown PRs	2024-03-12 12:17:30 +01: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