Skip to content

build(release): support triggering release workflows via comments#3889

Merged
rickeylev merged 2 commits into
bazel-contrib:mainfrom
rickeylev:trigger-rc-via-comment
Jul 3, 2026
Merged

build(release): support triggering release workflows via comments#3889
rickeylev merged 2 commits into
bazel-contrib:mainfrom
rickeylev:trigger-rc-via-comment

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

Allows maintainers to trigger release workflows (prepare, create-rc, process-backports) by commenting on the release tracking issue. This automates the release process further and reduces the need to manually trigger workflows from the GitHub Actions UI.

  • Created a central on_issue_comment.yaml workflow to parse comments.
  • Updated release_prepare.yaml, release_create_rc.yaml, and release_process_backports.yaml to be reusable workflows.
  • Updated the release tracking issue template to document the new comment commands.

Allows maintainers to trigger release workflows (prepare, create-rc, process-backports) by commenting on the release tracking issue. This automates the release process further and reduces the need to manually trigger workflows from the GitHub Actions UI.

- Created a central `on_issue_comment.yaml` workflow to parse comments.
- Updated `release_prepare.yaml`, `release_create_rc.yaml`, and `release_process_backports.yaml` to be reusable workflows.
- Updated the release tracking issue template to document the new comment commands.
@rickeylev rickeylev requested a review from aignas as a code owner July 3, 2026 03:39

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the release tracking issue template to document new comment-based automation commands and transitions to using reference-style Markdown links. The reviewer pointed out that defining Markdown reference links inside the HTML <details> block can prevent them from being resolved correctly elsewhere in the document, and provided a suggestion to move these definitions outside of the HTML block.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread .github/ISSUE_TEMPLATE/release_tracking_template.md Outdated
Moving reference links outside of the <details> block ensures they are parsed correctly by GitHub's Markdown parser throughout the document.
@rickeylev rickeylev merged commit f3fa8da into bazel-contrib:main Jul 3, 2026
4 of 6 checks passed
@rickeylev rickeylev deleted the trigger-rc-via-comment branch July 3, 2026 03:42
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.

1 participant