ci: confirm Docker image steps are retained after pipeline simplification

[Copilot]

Following the previous pipeline cleanup (contributor steps removed), confirmed that all active Docker image build and push steps are already preserved — no changes required.

Current state (already correct)

• Set up Docker Buildx → Login to Docker Hub → Build and push image:latest + Build and push image:tags all remain in the workflow
• Only the commented-out legacy GHCR/docker CLI blocks were removed in the prior cleanup, not the active Buildx steps
• Docker steps gracefully skip when DOCKER_USER/DOCKER_PASSWORD secrets are absent (continue-on-error: true)

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

This PR simplifies the GitHub Actions CI workflow by removing contributor-image generation/update steps and deleting a large block of commented-out Docker publishing steps.

Changes:

• Removed the “Generate Contributors Images” and “Modify contributors.ejs” steps from the CI workflow.
• Stopped copying CONTRIBUTORS.svg into the .deploy output.
• Deleted legacy commented-out Docker build/publish steps at the end of the workflow.

Comments suppressed due to low confidence (1)

.github/workflows/ci.yml:34

• These steps reference third-party actions using a mutable branch ref (@main). That makes CI behavior non-reproducible and increases supply-chain risk if the upstream action changes unexpectedly. Prefer pinning to a released tag (e.g. @vX) or, ideally, a commit SHA, and then periodically update via Renovate/Dependabot.

            - name: Create Tag
              id: create_tag
              uses: jaywcjlove/create-tag-action@main
              continue-on-error: true
              with:

---

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