diff options
| author | kolaente <k@knt.li> | 2022-11-03 16:49:00 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-03 23:49:00 +0800 |
| commit | 085f717529008c31b147f76ea7eeaf06ca8801bd (patch) | |
| tree | 673e6904f488d1c2cd0def082d4ff979c72a3de2 /modules/convert/convert.go | |
| parent | f17edfaf5a31ea3f4e9152424b75c2c4986acbe3 (diff) | |
| download | gitea-085f717529008c31b147f76ea7eeaf06ca8801bd.tar.gz gitea-085f717529008c31b147f76ea7eeaf06ca8801bd.zip | |
feat: notify doers of a merge when automerging (#21553)
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>
Diffstat (limited to 'modules/convert/convert.go')
0 files changed, 0 insertions, 0 deletions