ci: skip multi-arch manifest publish when push is disabled

[fallintoplace]

Summary

• skip the multi-arch manifest job when push_on_build is false

Why

The per-arch image builds already honor push_on_build through the build output settings, but the final manifest job still runs unconditionally.

That leaves us with an inconsistent flow in non-push contexts: the workflow can skip pushing the arch images and then still try to create and push a multi-arch manifest that references images that were never published.

This showed up after the CI workflow split introduced push_on_build into the modular workflows, but the manifest job never started consuming that signal.

Validation

• git diff --check
• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/image-builds.yaml")'

I did not run the workflow end-to-end locally.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[kvalliyurnatt]

@fallintoplace can you please check and make sure you have signed your commit

Commit not signed

[fallintoplace]

@kvalliyurnatt Let me check real quick. Sorry for that.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: QUIET

Plan: Enterprise

Run ID: ec2b4713-5830-40f4-bb2f-899ece7b48ec

📥 Commits

Reviewing files that changed from the base of the PR and between f12acb8 and 0fa5039.

📒 Files selected for processing (1)

• .github/workflows/image-builds.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The image build workflow now runs the multi-architecture manifest build and push job only when push_on_build is set to 'true'.

Merge Risk: ⚪ Minimal · up to 0fa50

The workflow will now skip multi-architecture manifest publishing when image pushes are disabled, avoiding an invalid manifest publication attempt in non-push contexts. No actionable merge-blocking risk remains beyond normal checks and review.

---

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

[kvalliyurnatt]

/ok to test 0fa5039

[tariq1890]

Thank you for you contribution @fallintoplace !