Instruction file imported from isaacismaelx14/minerelay (
.github/instructions/commit.instructions.md). Copyright stays with the author.
Commit Message Instructions
These instructions are mandatory for AI-generated commits in this repository.
Required Title Format
Use exactly:
type(scope): short summary
Optional breaking format:
type(scope)!: short summary
Rules:
typemust be lowercasescopeis mandatory- summary should be concise, imperative, and without trailing period
Allowed Types
Only these are allowed:
featfixperfrefactordocsstylechorebuildcitest
Allowed Scopes
Only these are allowed:
apiadminlauncherplatformdesktopsharedcoreuirelease
Do not use any other scope.
Breaking Changes
When introducing breaking behavior:
- Use
!in title - Include body line:
BREAKING CHANGE: <what changed and migration guidance>
Multi-change Commit Bodies
When needed, body bullet lines must also be conventional:
* feat(api): ...* fix(shared): ...
Examples
Valid:
ci(platform): update semantic release workflow inputsfeat(api): expose package version at root endpointfix(launcher): show app version in compact headerchore(release): @minerelay/api/v0.1.0-beta.32
Invalid:
feat: add release flow(missing scope)feat(unknown): add release flow(scope not allowed)Update workflow(not conventional)
Enforcement
Husky commit-msg validates these rules from release.config.json.
If commit is rejected, rewrite it to match this file.