Story (Required)

Any relevant RN from upstream needs to be added to the release notes section in a consolidated manner and docs team will be referring to this instead of google docs moving forward.

1) Before this update, PipelineRuns status comments posted on every pull request, creating noise. This is now resolved by allowing status comments to be disabled in repository CR settings in the following way:

...
kind: Repository
spec:
  settings:
    github:
      comment_strategy: "disable_all" 
...

2) Before this update, the "PipelineRun starting" comment did not include a console link, making access less convenient. This is now resolved by adding a direct link to the PipelineRun in the comment.

3) Before this update, empty commits in Bitbucket push events were processed by PaC, causing controller crash. This is now resolved by invalidating empty commits in the payload.

4) Before this update, PipelineRuns modified by external controllers (e.g. Kueue) were not correctly annotated when marked as "started." This is now resolved by ensuring proper annotation on status change.

Background (Required)

<Describes the context or background related to this story>

Out of scope

• Drafting the release notes text.

• Review and approval of release notes.

• Publication of the release notes.

Approach (Required)

• Fetch the list of PRs/issues merged upstream for v1.20 from GitHub 

• Identify PRs relevant to OpenShift Pipelines (skip upstream-only changes not consumed downstream, if applicable).

• Organize contributions into categories (features, enhancements, bug fixes).

Dependencies

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

Acceptance Criteria (Mandatory)

RN section is added with a consolidated list of revelant upstream release notes.

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