Restrict Docker builds to tagged releases only #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Docker builds were triggering on every push and pull request, consuming unnecessary CI resources. Changed workflow to run only on version tags.
Changes
push.branches: ["main"]trigger from docker.yml workflowpull_requesttrigger from docker.yml workflowpush.tags: ["v*"]andworkflow_dispatchtriggersDocker images now build exclusively on release tags (e.g.,
v0.1.1) or manual dispatch, not on every commit or PR.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Note
CI workflow scope change for Docker builds
.github/workflows/docker.ymltriggers topush.tags: ["v*"]andworkflow_dispatchpushon branches (e.g.,main) andpull_requesttriggers, preventing image builds for regular commits/PRsWritten by Cursor Bugbot for commit 9b632d0. This will update automatically on new commits. Configure here.