Update README with multi-arch build and tagging workflow documentation

[hardikdr]

Summary by CodeRabbit

• Documentation
  • Updated build flow documentation to support multi-arch builds with --config flags
  • Added image tagging workflow examples for build and post-build scenarios
  • Clarified push/pull mechanics for multi-arch images including sub-manifests
  • Enhanced examples for handling architecture-specific builds (amd64, arm64)

[coderabbitai]

Walkthrough

The README documentation has been reworked to explain a multi-arch build workflow, replacing single-arch build instructions with a --config flag approach for architecture-specific configuration. Updated examples show repeated --config blocks for multiple architectures, new image tagging workflows, and modified push semantics using --push-sub-manifests.

Changes

Cohort / File(s)	Summary
Documentation README.md	Updated build flow documentation from single-arch to multi-arch approach using --config flags; added examples for architecture-specific builds (amd64, arm64); revised post-build tagging and push workflows with --push-sub-manifests; reformatted examples and clarified manifest handling semantics.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is missing; only an empty template placeholder exists with no proposed changes or details documented.	Add a detailed description following the template with specific changes made (e.g., multi-arch build flow, tagging workflow, push semantics updates).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately describes the main changes in the pull request, which reworks the README to document multi-arch build workflows and tagging instructions.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch enh/improve-doku

---

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.}