torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
3c9127678c0bb7f18dd91f78d202c0ac104a3893
my-pal-mcp-server/.github/pull_request_template.md
PCITI 3c9127678c docs+docker: Complete documentation infrastructure with Docker automation testing (#2) 
* fix: Remove invalid colon in bash else statement

- Fix bash syntax error in auto-version workflow
- Remove Python-style colon from else statement
- Resolves exit code 127 in version bump determination

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* feat: Add Docker build combinations for non-versioning prefixes

- 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>

* docs: Add comprehensive PR prefix and automation documentation

- Update CONTRIBUTING.md with detailed PR prefix system explanation
- Add automation workflow documentation to docs/contributing/workflows.md
- Create new user-friendly contributing guide at docs/user-guides/contributing-guide.md
- Include Mermaid diagrams for workflow visualization
- Document Docker testing combinations and image tagging strategy
- Add best practices and common mistakes to avoid

This provides clear guidance for contributors on using the automated
versioning and Docker build system effectively.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Patryk Ciechanski <patryk.ciechanski@inetum.com>
Co-authored-by: Claude <noreply@anthropic.com>
2025-06-12 09:57:44 +02:00

1.9 KiB
Raw Blame History

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> or BREAKING 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 only
  • chore: <description> - Maintenance tasks
  • test: <description> - Test additions/changes
  • ci: <description> - CI/CD changes
  • style: <description> - Code style changes

Docker Build Options:

  • docker: <description> - Force Docker build without version bump
  • docs+docker: <description> - Documentation + Docker build
  • chore+docker: <description> - Maintenance + Docker build
  • test+docker: <description> - Tests + Docker build
  • ci+docker: <description> - CI changes + Docker build
  • style+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.