Allow merge groups to trigger the self-zizmor workflow #80
Conversation
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
|
TruffleHog Scan Results No secrets detected in this PR. |
isaiah-grafana
approved these changes
Oct 7, 2025
floriatsui
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Currently merge groups can't trigger the self-zizmor workflow and remain stuck, this allows the trigger to the workflow to allow these types of commits to succeed CI and get properly merged to the default branch.
I added the
typesfilter although that filter is ignored to make it explicit, currentlypathsare used as filter for other triggers and is also ignored by the ruleset, we might want to revise our triggers and make it explicit that the workflow only supports these triggers: https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#supported-event-triggers