Reusable workflows

[karofox]

No description provided.

[Copilot]

Pull request overview

This PR refactors the existing Docker build workflow into a reusable GitHub Actions workflow, and adds a caller workflow that invokes it for multiple ROS distro/tag combinations.

Changes:

• Added a new caller workflow that runs builds for humble and jazzy, plus a separate latest tag build.
• Converted the existing Docker workflow into a reusable workflow_call template with inputs for image name, Dockerfile path, and base tag.
• Updated tagging logic to use template inputs rather than a hardcoded image name and distro matrix.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/docker.yaml	New caller workflow that invokes the reusable template for multiple distros/tags.
.github/workflows/docker-template.yaml	Reusable workflow template parameterized via workflow_call inputs and used by the caller workflow.

Comments suppressed due to low confidence (2)

.github/workflows/docker-template.yaml:58

• github.event_name will be workflow_call inside a reusable workflow, so this condition will never be true and SUFFIX will always be empty. If you need PR-specific tags, compute/pass a suffix from the caller workflow (as an input), or detect PRs via ref patterns (e.g., refs/pull/).
  .github/workflows/docker-template.yaml:73
• This if guard will prevent the manifest job from ever running in this reusable workflow because github.event_name is workflow_call (even when the caller was triggered by push). If the manifest should only run for push builds, gate it in the caller job (using if: on the job that calls this workflow) or pass an explicit boolean input like publish_manifest and use that here.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.