feat: add action to notify MM about GH failures - #132
Open
hk21702 wants to merge 1 commit into
Open
Conversation
hk21702
force-pushed
the
mm-notify-on-failure-action
branch
6 times, most recently
from
July 23, 2026 16:44
44697d9 to
6da16bd
Compare
Here, we add an action to notify Mattermost about GH failures. This utilizes the MM REST API and requires a bot token for use. When used as intended, it fetches the corresponding failing run, linking the run, ref, and describing the trigger. It also pings a list of configured users.
hk21702
force-pushed
the
mm-notify-on-failure-action
branch
from
July 23, 2026 16:50
6da16bd to
909c5d6
Compare
Member
Author
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
1 participant
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.
Here, we add an action to notify Mattermost about GH failures. When used as intended, it fetches the corresponding run, linking the run, ref, and describing the trigger. It also pings a list of configured users.
This is pretty similar to what we already use elsewhere. But, instead of a webhook, this utilizes the MM REST API and requires a bot token for use. We also add a few additional features, such as using the repository org/owner icon as the author icon by default.
In terms of safety, as long as the MM token is implemented using a repository secret, it should be that only actors with write permissions can send notifications. That being said, caution should still be taken when using this action in public repositories.
Example notification:
