ci: only build Docker images on merge to main/next-release #110

cal · 2026-03-20T17:43:49Z

cal commented

2026-03-20 17:43:49 +00:00

Summary

Removes the pull_request trigger from the Docker build workflow. Previously, every push to a PR branch triggered a full Docker build+push, wasting CI resources on feature/bugfix branches.

Now the workflow only runs on pushes (merges) to main and next-release.

Changes

Removed pull_request: branches: [main] trigger from .gitea/workflows/docker-build.yml
Updated header comments to reflect the new behavior

Testing

No tests needed — CI workflow config change only.

🤖 Generated with Claude Code

## Summary Removes the `pull_request` trigger from the Docker build workflow. Previously, every push to a PR branch triggered a full Docker build+push, wasting CI resources on feature/bugfix branches. Now the workflow only runs on pushes (merges) to `main` and `next-release`. ## Changes - Removed `pull_request: branches: [main]` trigger from `.gitea/workflows/docker-build.yml` - Updated header comments to reflect the new behavior ## Testing No tests needed — CI workflow config change only. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

cal added 1 commit 2026-03-20 17:43:50 +00:00

ci: remove pull_request trigger from Docker build workflow ce2c47ca0c

The PR trigger caused Docker builds on every push to PR branches,
wasting CI resources. Only build on merge to main/next-release.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

cal merged commit 4775c175c5 into next-release

2026-03-20 17:44:12 +00:00

cal deleted branch ci/remove-pr-trigger

2026-03-20 17:44:13 +00:00

cal referenced this issue from a commit

2026-03-20 17:44:14 +00:00

Merge pull request 'ci: only build Docker images on merge to main/next-release' (#110) from ci/remove-pr-trigger into next-release

cal referenced this pull request

2026-03-20 17:54:05 +00:00

Merge next-release into main #111

Sign in to join this conversation.

No reviewers