You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the conventional commits convention (type(scope): description), we (@lwjohnst86 and I) have talked about the need for some common workspace scopes in our projects. Especially, since we have a strong focus on documentation, the type docs seems too unspecific, when almost an entire repository, like the decisions repo, is documentation.
With the Conventional Commits VS Code extension, it's possible to set workspace scopes in .vscode/settings.json, which could help us use the same scopes across commits/PRs/team members.
The text was updated successfully, but these errors were encountered:
Following the conventional commits convention (
type(scope): description
), we (@lwjohnst86 and I) have talked about the need for some common workspace scopes in our projects. Especially, since we have a strong focus on documentation, the typedocs
seems too unspecific, when almost an entire repository, like thedecisions
repo, is documentation.With the Conventional Commits VS Code extension, it's possible to set workspace scopes in
.vscode/settings.json
, which could help us use the same scopes across commits/PRs/team members.The text was updated successfully, but these errors were encountered: