Use Release Please compatible Conventional Commits for all commit messages that may end up in release notes.
Use:
<type>(<scope>): <subject>
Scope is optional:
<type>: <subject>
Use these types:
featfixdepschore
Use ! for breaking changes when needed:
feat(pdc)!: require reviewed route before web clearance issue
Use chore when a commit should not show up as a user-facing release-note change.
For this repo, do not use other generic types such as docs, refactor, test, build, ci, perf, or revert for release-note commit titles.
Use a scope when it adds domain meaning.
Do not use product or package scopes such as:
backendfrontendeuroscope-plugindocs
Prefer feature or domain scopes such as:
cdmpdcecfmpstripclearancesessionwebsocketprivate-message
If a change spans multiple products, still scope by the domain or behavior being changed, not by the product directory.
- Use imperative mood.
- Keep it concise and release-note friendly.
- Start with the change itself, not with filler words.
- Do not end the subject with a period.
feat(cdm): show startup status in strip dialogfix(pdc): prefer SID over stale vectored departure textdeps(front-strip): bump zustand to 6.0.1chore(ecfmp): rename injected test helpersfix(private-message): route sends through controller CIDfeat(ecfmp)!: require explicit restriction acknowledgment