Skip to content

Conversation

@rickeylev
Copy link
Collaborator

By default, the workflow creates draft PRs. The bazel-io bot ignores drafts.
Since we can't mark the PR as non-draft ourselves, we then have to wait for
bcr maintainers to do so.

To fix, create the bcr prs are non-draft. Then we can approve and the bazel-io
bot will approve and merge the PR.

@rickeylev rickeylev requested a review from aignas as a code owner January 10, 2026 22:46
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@rickeylev rickeylev enabled auto-merge January 10, 2026 22:47
@rickeylev rickeylev added this pull request to the merge queue Jan 11, 2026
Merged via the queue into bazel-contrib:main with commit 22f3de0 Jan 11, 2026
4 checks passed
@rickeylev rickeylev deleted the chore.nondraft.bcr.publish branch January 11, 2026 01:08
@rickeylev rickeylev mentioned this pull request Jan 11, 2026
17 tasks
rickeylev added a commit to rickeylev/rules_python that referenced this pull request Jan 11, 2026
…ted PRs (bazel-contrib#3504)

By default, the workflow creates draft PRs. The bazel-io bot ignores
drafts.
Since we can't mark the PR as non-draft ourselves, we then have to wait
for
bcr maintainers to do so.

To fix, create the bcr prs are non-draft. Then we can approve and the
bazel-io
bot will approve and merge the PR.

(cherry picked from commit 22f3de0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants