CI - Close some gaps with GitHub discord notifications#5056
Merged
Conversation
bfops
commented
Jun 23, 2026
…into bfops/notify-on-push
bfops
changed the title
jdetter
approved these changes
Jun 23, 2026
jdetter
left a comment
jdetter
left a comment
Contributor
There was a problem hiding this comment.
Seems fine to me, let's try it 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
We currently have discord notifications when PRs merge into master. We have two problems:
This PR fixes those issues by changing the job to run on any push to master rather than when a PR is closed.
API and ABI breaking changes
None. CI only.
Expected complexity level and risk
1
Testing
I don't think we can test this without merging into master.