- Add support for prefix+docker combinations (docs+docker:, chore+docker:, etc.) - Enable Docker build for non-versioning changes when requested - Add repository_dispatch trigger for Docker workflow - Update Docker tagging for PR-based builds (pr-X, main-sha) - Update PR template with new prefix options This allows contributors to force Docker builds for documentation, maintenance, and other non-versioning changes when needed. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
1.9 KiB
1.9 KiB
PR Title Format
Please ensure your PR title follows one of these formats:
Version Bumping Prefixes (trigger Docker build + version bump):
feat: <description>- New features (triggers MINOR version bump)fix: <description>- Bug fixes (triggers PATCH version bump)breaking: <description>orBREAKING CHANGE: <description>- Breaking changes (triggers MAJOR version bump)perf: <description>- Performance improvements (triggers PATCH version bump)refactor: <description>- Code refactoring (triggers PATCH version bump)
Non-Version Prefixes (no version bump):
docs: <description>- Documentation onlychore: <description>- Maintenance taskstest: <description>- Test additions/changesci: <description>- CI/CD changesstyle: <description>- Code style changes
Docker Build Options:
docker: <description>- Force Docker build without version bumpdocs+docker: <description>- Documentation + Docker buildchore+docker: <description>- Maintenance + Docker buildtest+docker: <description>- Tests + Docker buildci+docker: <description>- CI changes + Docker buildstyle+docker: <description>- Style changes + Docker build
Description
Please provide a clear and concise description of what this PR does.
Changes Made
- List the specific changes made
- Include any breaking changes
- Note any dependencies added/removed
Testing
- Unit tests pass
- Integration tests pass (if applicable)
- Manual testing completed
- Documentation updated (if needed)
Related Issues
Fixes #(issue number)
Checklist
- PR title follows the format guidelines above
- Code follows the project's style guidelines
- Self-review completed
- Tests added/updated as needed
- Documentation updated as needed
- All tests passing
- Ready for review
Additional Notes
Any additional information that reviewers should know.