Skip to content

Conversation

christophfroehlich
Copy link
Contributor

Can be activated by

  • workflow dispatch manual action
  • adding labels: check-prerelease or check-prerelease-downstream. Once one of the label is added, it will be triggered by subsequent updates of the PR.

If not activated, github lists them as "skipped". Nothing I can do against it afaik.

@christophfroehlich christophfroehlich added backport-humble Triggers PR backport to ROS 2 humble. backport-jazzy Triggers PR backport to ROS 2 jazzy. labels Sep 2, 2025
saikishor
saikishor previously approved these changes Sep 2, 2025
@christophfroehlich christophfroehlich added the check-prerelease Runs the pre-release workflow without downstream dependencies label Sep 2, 2025
@christophfroehlich christophfroehlich merged commit 92c2582 into master Sep 3, 2025
7 checks passed
@christophfroehlich christophfroehlich deleted the add/prerelease branch September 3, 2025 12:47
mergify bot pushed a commit that referenced this pull request Sep 3, 2025
(cherry picked from commit 92c2582)
mergify bot pushed a commit that referenced this pull request Sep 3, 2025
(cherry picked from commit 92c2582)
christophfroehlich added a commit that referenced this pull request Sep 3, 2025
christophfroehlich added a commit that referenced this pull request Sep 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-humble Triggers PR backport to ROS 2 humble. backport-jazzy Triggers PR backport to ROS 2 jazzy. check-prerelease Runs the pre-release workflow without downstream dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants