Files
puaros/.gitmessage
imfozilbek 7f6180df37 docs: add monorepo versioning strategy and release pipeline
- add Path Reference section with explicit paths
- add Monorepo Versioning Strategy with prefixed tags
- add 6-phase Release Pipeline documentation
- update Git Commit Format for monorepo (package scope)
- update .gitmessage with package scopes
- fix tsconfig.json references (remove non-existent, add ipuaro)
- fix guardian tsconfig formatting (4-space indent)
2025-11-29 22:41:03 +05:00

46 lines
1.4 KiB
Plaintext

# <type>(<package>): <subject>
#
# <body>
#
# <footer>
# Format:
# - Package changes: <type>(<package>): <subject>
# Examples: feat(guardian): add detector
# fix(ipuaro): resolve memory leak
# - Root changes: <type>: <subject>
# Examples: chore: update eslint config
# docs: update root README
# Type should be one of the following:
# * feat: A new feature
# * fix: A bug fix
# * docs: Documentation only changes
# * style: Changes that do not affect the meaning of the code (formatting, etc)
# * refactor: A code change that neither fixes a bug nor adds a feature
# * perf: A code change that improves performance
# * test: Adding missing tests or correcting existing tests
# * build: Changes that affect the build system or dependencies
# * ci: Changes to CI configuration files and scripts
# * chore: Other changes that don't modify src or test files
# * revert: Reverts a previous commit
# Package scopes:
# * guardian - @puaros/guardian package
# * ipuaro - @puaros/ipuaro package
# * (none) - root-level changes
#
# Subject line rules:
# - Use imperative mood ("add feature" not "added feature")
# - Don't capitalize first letter
# - No period at the end
# - Limit to 50 characters
#
# Body (optional):
# - Explain what and why (not how)
# - Wrap at 72 characters
# - Separate from subject with blank line
#
# Footer (optional):
# - Reference issues: "Fixes #123" or "Closes #123"
# - Breaking changes: "BREAKING CHANGE: description"