Story (Required)

Description:
In Pipelines as Code (PAC) controller logs, messages like the following are currently logged at the “error” level:

{
    "level": "error",
    "ts": "2025-09-19T20:48:18.538Z",
    "logger": "pipelinesascode",
    "caller": "adapter/sinker.go:32",
    "msg": "failed to parse event: commit 57f16c1647ea40b9c82a492c67e2cd8cd03c8fae is part of pull request #6, skipping push event",
    ...
}

This is not an actual error but an intentional skip to prevent duplicate PipelineRuns when a commit is part of an open pull request. Logging it as “error” can confuse users and support teams, leading to unnecessary investigations.

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