Red Hat Konflux purge oadp-must-gather-oadp-dev

[red-hat-konflux]

Pipelines as Code configuration removal

[coderabbitai]

Walkthrough

Two Tekton PipelineRun manifest files are deleted: oadp-must-gather-oadp-dev-pull-request.yaml and oadp-must-gather-oadp-dev-push.yaml. These configurations defined multi-task container image build and validation pipelines for OADP must-gather, including dependency prefetching, multi-platform builds, security scanning, and artifact publication workflows.

Changes

Cohort / File(s)	Summary
Tekton Pipeline Configurations Removed .tekton/oadp-must-gather-oadp-dev-pull-request.yaml, .tekton/oadp-must-gather-oadp-dev-push.yaml	Complete removal of two PipelineRun manifests (~1,331 lines total). Both files defined comprehensive multi-task build pipelines with parameters, task orchestration, security checks, and artifact handling logic.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch konflux-purge-oadp-must-gather-oadp-dev

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign sseago for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.