Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-5992

DOC: Add support for on-comment events for pull requests

XMLWordPrintable

    • 3
    • Documentation (Ref Guide, User Guide, etc.), User Experience
    • Hide
      We now support the on-comment annotation to match a PipelineRuns on
      pull requests.

      This is only supported on pull_requests and on GitHub, Gitea and GitLab
      providers.

      Show
      We now support the on-comment annotation to match a PipelineRuns on pull requests. This is only supported on pull_requests and on GitHub, Gitea and GitLab providers.
    • ---
    • ---

      Story (Required)

      As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>

      Add an annotation on PipelineRun to trigger on-comments events

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

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

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      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

              Unassigned Unassigned
              mramendi Mikhail Ramendik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: