fix: open BCR pull requests for review#85
Merged
Merged
Conversation
longlho
enabled auto-merge (squash)
July 16, 2026 15:45
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
1 participant
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.
What
Pass
draft: falseto the reusable BCR publish workflow so generated registry PRs open ready for review.Why
publish-to-bcr@v1.4.2defaultsdrafttotrue. The v0.9.0 release inherited that default and created bazelbuild/bazel-central-registry#9716 as a draft.The BCR publisher uses the
formatjsprojectbot account, so there is no need for the human-author draft/auto-approval workaround described by the upstream workflow.Validation
.github/workflows/publish.yamlwith Ruby YAMLgit diff --checkDRAFT: truebefore this override