Repository navigation
fix(ci): skip the decision record branch rule on the release PR - #369
Merged
Merged
Conversation
Contributor
🛡️ Security Hardening Pipeline ResultsBranch: Workflow Run: 618 Scan Status
Summaries Collected: 4 Scanner Results🔬 CodeQL SAST (Javascript)Status: Completed Findings Summary
No security findings detected for Javascript. Artifacts: CodeQL Reports (Javascript) 🔗 Dependency ReviewStatus: ✅ No issues found No vulnerable or license-violating dependencies detected in this PR. 🔑 Gitleaks (Secrets)No 🔑 Gitleaks (Secrets) findings summary was produced. 📦 OSV (Dependencies)No 📦 OSV (Dependencies) findings summary was produced. Generated by Argus Generated by Argus |
The beta -> main release PR adds every record that landed on beta, and its head branch has no issue number, so the check always failed it. Each of those records already passed the rule on its own PR. Fork branches named beta still get the rule. Closes #368
eFAILution
force-pushed
the
fix/368-release-pr-decision-check
branch
from
October 23, 2026 13:32
2335f06 to
615e1d2
Compare
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.
Closes #368
The release PR (#357) adds every record that landed on
beta, and its head isbeta, so the branch rule always failed it. Each record already passed the rule on its own PR. Now the check skips the branch rule only for a same-repobeta->mainPR, and still validates the stores. A fork branch namedbetastill gets the rule.npm run decisions:checkpassesactionlintis clean