You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
085f717529
I found myself wondering whether a PR I scheduled for automerge was actually merged. It was, but I didn't receive a mail notification for it - that makes sense considering I am the doer and usually don't want to receive such notifications. But ideally I want to receive a notification when a PR was merged because I scheduled it for automerge. This PR implements exactly that. The implementation works, but I wonder if there's a way to avoid passing the "This PR was automerged" state down so much. I tried solving this via the database (checking if there's an automerge scheduled for this PR when sending the notification) but that did not work reliably, probably because sending the notification happens async and the entry might have already been deleted. My implementation might be the most straightforward but maybe not the most elegant. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> |
2 years ago | |
|---|---|---|
| .. | ||
| check.go | 2 years ago | |
| check_test.go | 2 years ago | |
| commit_status.go | 2 years ago | |
| edits.go | 2 years ago | |
| lfs.go | 2 years ago | |
| main_test.go | 2 years ago | |
| merge.go | 2 years ago | |
| patch.go | 2 years ago | |
| patch_unmerged.go | 2 years ago | |
| pull.go | 2 years ago | |
| pull_test.go | 2 years ago | |
| review.go | 2 years ago | |
| temp_repo.go | 2 years ago | |
| update.go | 2 years ago | |