Story (Required)

From Ortec on upstream:

Currently PipelinRuns targeting the pull_request event are triggered every time a commit occurs on a pull_request. However, we'd like to be able to trigger a PipelineRun only when a PR is opened or closed and no longer on the commits to the pull request.
One way to achieve this behavior is to use GitHub workflows to start the PipelineRun by sending a CURL request (pipelinesascode.com/docs/guide/incoming_webhook). Unfortunately, we can't set the branch name to any name, since the Repository resource doesn't allow wildcards for the incoming target branch name and constantly updating the Repository resource is not favorable.
Would it be possible to either support wildcards for the incoming target branch name in the Repository resource, or to extend the events or cel expressions to include events for opening/closing PRs?
 

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

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