<type>(DMC-<number>): <subject>
<body>
Resolves: DMC-<number>
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Code formatting, semicolons, etc.
- refactor: Code refactoring without functionality changes
- test: Adding or updating tests
- chore: Maintenance, build tasks, dependency updates
- ci: CI/CD pipeline changes
- MANDATORY: Every commit MUST include ticket number in format
DMC-<number> - Subject line: Include ticket number after type:
fix(DMC-46): Fix API parameter mismatches - Footer: Include
Resolves: DMC-<number>line at the end
feat(DMC-46): Add human-readable display names to job configurations
- Added displayName and description fields to expert.json
- Added displayName and description fields to testcases-generator.json
- Updated parameter descriptions for better UX
- Fixed nested array structures in examples
Resolves: DMC-46
fix(DMC-46): Fix JSON deserialization errors in job configurations
- Removed nested arrays from examples fields
- Changed defaultValue from [] to null for array types
- Fixed confluencePages parameter type configuration
Resolves: DMC-46
docs(DMC-46): Add commit message rules with mandatory ticket references
- Created COMMIT_MESSAGE_RULES.md with format specifications
- Added examples for different commit types
- Enforced ticket number requirements
Resolves: DMC-46
β Add new feature (missing ticket number)
β fix: bug (missing ticket number)
β feat: new API endpoint (missing ticket number)
Add this to your .gitconfig to enforce format:
[commit]
template = .gitmessage
Create .gitmessage file:
# feat|fix|docs|style|refactor|test|chore|ci(DMC-XXX): Brief description
# Detailed explanation of changes
# - What was changed
# - Why it was changed
# - How it affects the system
Resolves: DMC-XXX