Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-7834

Add Support for pull_request_number variable on push events

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • After this update, `pull_request_number` dynamic variable can be referenced in push event PipelineRuns which are occurred on pull request merge and the variable will be holding value of pull request number.
    • Enhancement
    • Done
    • Pipelines Sprint Crookshank 30, Pipelines Sprint Crookshank 31

      Story (Required)

      When a pull request is merged, push event occurs and I want `pull_request_number` dynamic variable should be holding the pull request number value which caused the push event.

       

      https://github.com/openshift-pipelines/pipelines-as-code/issues/1353

      Out of scope

      any changes in pull request event.

      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

              rh-ee-zashaikh Zaki Shaikh
              rh-ee-zashaikh Zaki Shaikh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: