Skip to content

workflow: allow gholms to trigger backport comment commands - #4206

Merged
aignas merged 1 commit into
bazel-contrib:mainfrom
rickeylev:allow_comment_user_list
Oct 1, 2026
Merged

aignas merged 1 commit into
bazel-contrib:mainfrom
rickeylev:allow_comment_user_list

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

gholms contributes fixes that need backporting to release branches,
but lacks repository collaborator permissions to run slash commands.

Add gholms to the backport user allowlist so they can trigger
/backport commands on pull requests and release tracking issues.

`gholms` contributes fixes that need backporting to release branches,
but lacks repository collaborator permissions to run slash commands.

Add `gholms` to the backport user allowlist so they can trigger
`/backport` commands on pull requests and release tracking issues.
@rickeylev
rickeylev requested a review from aignas as a code owner October 1, 2026 07:29
@aignas
aignas added this pull request to the merge queue Oct 1, 2026
Merged via the queue into bazel-contrib:main with commit fc7dc41 Oct 1, 2026
5 checks passed
@rickeylev

Copy link
Copy Markdown
Collaborator Author

fyi @gholms you can now comment /backport on PRs and release issues to schedule them for backporting. More docs at https://github.com/bazel-contrib/rules_python/blob/main/RELEASING.md#method-a-comment-on-the-pr

@rickeylev
rickeylev deleted the allow_comment_user_list branch October 1, 2026 16:45
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