Story (Required)

As an end user trying to correctly configure my PaC pipelinerun definitions, I want the system to provide me feedback when I erroneously create two pipelinerun definitions with the same name, but different on-cel-expressions. 

PaC will only act on one of the two, and I will be confused why it does not act on the other one unless PaC provides me some indication of my error.

You might consider providing the feedback either via the openshift events api, or via the "checks" api of the SCM provider - the user is most likely to see it there.

Background (Required)

https://redhat-internal.slack.com/archives/C04PZ7H0VA8/p1702924292760709?thread_ts=1702918251.520489&cid=C04PZ7H0VA8

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