Git and releases

BranchesCopy Anchor Link

Commit and push to develop. Never commit to main; it only moves through the develop to main pull request.

Commit messagesCopy Anchor Link

Commits follow Conventional Commits and commitlint checks them. The header is at most 72 characters and body lines are at most 100. Mark breaking changes with ! and a BREAKING CHANGE: footer.

Hooks stay onCopy Anchor Link

Lefthook runs format and lint before a commit and the affected typecheck and test gate before a push. Do not pass --no-verify. When a hook fails, fix the cause and commit again.

ChangesetsCopy Anchor Link

Every user-visible change adds a changeset with pnpm changeset. The apps share one version through a fixed group, so pick any app and describe the change for users. Releases do not use release-please.

Uncommitted work belongs to the userCopy Anchor Link

Do not run git checkout, git restore, git reset or git stash on files you did not change in this task. The one routine exception is restoring the .po catalogs described in Translations.