Repository navigation
ci: run the release workflow conformance check as an informative check - #284
Merged
Merged
Conversation
Calls the shared conformance workflow on pull requests and the merge queue. It reads workflow files only and is not a required check; a ruleset may require it later, at which point this trigger file is removed.
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
shan8851
approved these changes
Nov 16, 2026
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.
Problem
The shared release workflow conformance check exists in
0xPolygon/pipelines, and before any ruleset makes itrequired it needs a trial on real pull requests in this repository to show it gives no false failures.
Solution
Adds
.github/workflows/release-conformance-trigger.yml, which calls the shared conformance workflow on pullrequests and the merge queue. It reads workflow files only, needs only
contents: read, and is not arequired check. When a ruleset later requires the check for this repository, this trigger file is removed in
the same change, so the check never runs twice.
Verification
pnpm install --frozen-lockfile,pnpm run lintandchangeset statuspass (no package changes, so nochangeset).