Run checks on generated release metadata pull requests#33
Merged
Conversation
KyranTanDev
pushed a commit
to KyranTanDev/ClickLight
that referenced
this pull request
May 29, 2026
…-release-metadata-checks Run checks on generated release metadata pull requests
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
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.
Summary
actions: writepermission required to start those checks.Why
Release metadata pull requests are created with
GITHUB_TOKEN, so GitHub intentionally does not triggerpull_requestworkflows for them. OnceAudit GitHub Actionsbecame a required status check, generated release metadata PRs stayed blocked with no check run attached.This keeps the required check in place while making future generated release PRs validate automatically.
Validation
zizmor .