Repository navigation
Unlock branch rulesets around docs metadata push in build workflow - #292
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
petesramek
added
bug
github_actions
petesramek
enabled auto-merge (squash)
October 29, 2026 16:28
This branch was successfully deployed
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
The
Push assembly metadata artifactstep inbuild.ymlpushed directly to a branch covered by a ruleset (e.g.develop/**), failing with GH013 (required status checks / deployment). Wrap it with the existingbranch-protection/unlockandlockactions, asrelease.ymldoes. Failing run: 40907507353.Type of change
Checklist
/tests)/benchmarks) — if performance-impactingdotnet formatrun with no issues/samplesupdated — if public API changedbreaking/feat/fix/docs) — for changelog categorization