Remove Quay binary push workflow

[Joeavaikath]

Summary

• Remove the quay_binaries_push.yml GitHub Actions workflow that built multi-arch images and pushed them to quay.io/konveyor/oadp-cli-binaries
• This CI functionality is moving to operator-ci

Test plan

• Verify no other workflows depend on quay_binaries_push.yml
• Confirm operator-ci handles the multi-arch binary build and push

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Removed the automated workflow that built, archived, and published multi‑architecture (amd64/arm64) container images and pushed multi‑arch manifests to the container registry.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 70759849-27c6-4ec7-8de6-413436cda07d

📥 Commits

Reviewing files that changed from the base of the PR and between 2bc88a5 and 84b730d.

📒 Files selected for processing (1)

• .github/workflows/quay_binaries_push.yml

💤 Files with no reviewable changes (1)

• .github/workflows/quay_binaries_push.yml

---

📝 Walkthrough

Walkthrough

Deleted a GitHub Actions workflow that built and pushed multi-architecture container images to Quay.io; the removed workflow previously ran on push and pull_request for oadp-* branches and produced amd64 and arm64 artifacts and manifests.

Changes

Cohort / File(s)	Summary
GitHub Actions workflow (removed) .github/workflows/quay_binaries_push.yml	Removed workflow that built amd64 and arm64 images via Buildah, uploaded OCI archives as artifacts, and on push authenticated to quay.io to load, tag, and push multi-arch manifests with branch-based naming logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• Review quay_binaries_push workflow for oadp-1.6 branch support #153: Discusses reviewing/modifying the same Quay push workflow triggers and branch/tag behavior.

Possibly related PRs

• Trigger Quay push on oadp-* branch pushes instead of tag pushes #155: Alters triggers and manifest/tag conditions of the same workflow file that is deleted here.

Suggested reviewers

• kaovilai
• sseago

Poem

🐇🛠️ I hopped through lines of YAML bright,
Pushed binaries in day and night,
Now I tidy up the trail,
Fewer steps — a lighter tale,
Hooray for clean and quiet flight.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes key information about why changes were made and a test plan, but does not fully align with the template structure which requires 'Why the changes were made' and 'How to test the changes made' sections with specific formatting.	Restructure the description to match the template format: use 'Why the changes were made' heading with linked context, and 'How to test the changes made' heading with detailed verification steps.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main change: removing the Quay binary push workflow. It is concise, specific, and directly related to the primary purpose of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[Joeavaikath]

/hold until
openshift/release#77174
goes in

[mpryc]

/lgtm

[Joeavaikath]

/cherry-pick oadp-1.6

[openshift-cherrypick-robot]

@Joeavaikath: once the present PR merges, I will cherry-pick it on top of oadp-1.6 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick oadp-1.6

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Joeavaikath, kaovilai, mpryc

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Joeavaikath,kaovilai,mpryc]

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

[openshift-cherrypick-robot]

@Joeavaikath: #173 failed to apply on top of branch "oadp-1.6":

Applying: Remove Quay binary push workflow
Using index info to reconstruct a base tree...
M	.github/workflows/quay_binaries_push.yml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/quay_binaries_push.yml deleted in Remove Quay binary push workflow and modified in HEAD. Version HEAD of .github/workflows/quay_binaries_push.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Remove Quay binary push workflow

Details

In response to this:

/cherry-pick oadp-1.6

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.

[Joeavaikath]

/cherry-pick oadp-1.6

[openshift-cherrypick-robot]

@Joeavaikath: new pull request created: #177

Details

In response to this:

/cherry-pick oadp-1.6

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.