Eliminate duplicate workflow runs on pull requests

[RadCod3]

Problem

Opening a PR triggered workflows multiple times:

• CI workflow ran twice (once on push to feature branch, once on pull_request event)
• Docker publish workflow ran unnecessarily on PRs (already covered by CI's Docker build test)

Solution

• CI workflow: Removed push trigger for feature branches (feat/, fix/, chore/**). Now only runs on PRs to main and pushes to main.
• Docker publish workflow: Removed pull_request trigger. Now only runs on pushes to main and version tags.

[Copilot]

Pull request overview

This PR eliminates duplicate workflow runs when opening pull requests by adjusting GitHub Actions triggers. The CI workflow previously ran twice on feature branch PRs (once on push, once on pull_request), and the Docker publish workflow ran unnecessarily on PRs despite CI already testing Docker builds.

Key Changes:

• CI workflow now only runs on pull requests to main and direct pushes to main (removed feature branch push triggers)
• Docker publish workflow now only runs on pushes to main and version tags (removed pull_request trigger)
• Docker Compose configuration updated to use published image instead of local build

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/ci.yml	Removed push triggers for feature branches (feat/, fix/, chore/**), preventing duplicate runs on PRs
.github/workflows/docker-publish.yml	Removed pull_request trigger, as Docker builds are already tested in CI workflow
docker-compose.yml	Changed from local build to using published ghcr.io image

---

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