Story (Required)

As a developer,
I want to be able to trigger or cancel a PipelineRun by commenting on a GitHub commit that is associated with a Git tag,
So that I can manage release-specific pipelines in a streamlined and version-controlled way.

Background (Required)

To improve our GitOps-based CI/CD workflow, we are adding support for triggering and canceling PipelineRuns via GitHub comments on commits associated with Git tags. This allows developers to initiate pipelines tied to specific release versions (e.g., v1.0.0) directly from GitHub, without needing to push new commits or open PRs.

Out of scope

Any changes in PR GitOps comments or pushed commits GitOps comments.

Approach (Required)

• To trigger a PipelineRun:
  /test xyz-pipeline-run tag:v1.0.0

• To cancel a PipelineRun:
  /cancel xyz-pipeline-run tag:v1.0.0

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

• Comments on tagged commits are monitored for /test and /cancel commands.

• The system identifies the specified pipeline and tag, and performs the corresponding action (trigger or cancel).

• Invalid or malformed commands are handled gracefully with informative error messages.

• Only valid tags and pipeline names should be accepted.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met