Skip to content

chore: vcs message scope rule #299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
me-marcel merged 1 commit into from
Apr 26, 2026
Merged

chore: vcs message scope rule #299

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .agenstra/rules/version-control.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,12 @@ alwaysApply: true
- **Atomic Commits:** One logical change per commit
- **Conventional Commits:** Use format: `type(scope): description`
- Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`
- Scopes:
- Prefer the Nx project `name` from the touched `project.json` when a single project changes
- Domain libraries under `libs/domains/<domain>/...` often use `{domain}-{scope}-{type}-{name}`
- Exact literals and app naming: follow schemas in your workspace Nx plugin (e.g. `tools/<plugin>/`, `tools/code`)
- Typical generated app prefixes (when those generators exist): `backend-*`, `frontend-*`, `mcp-*`, `keycloak-theme-*`
- Multi-project or workspace-wide changes: Nx tags `backend`, `frontend`, `keycloak`, `shared`, or `repo`, `ci`, `deps`, `nx`, `tools`
- **Descriptive Messages:** First line ≤50 chars; body explains why, not what
- **Frequency:** Commit frequently; small, logical units
- **No Merge Commits:** Use rebase or squash to keep history clean
Expand Down
Loading