docs(meta): add type and scope commit options #28

Open
opened 2025-07-28 09:21:23 +00:00 by chartgerink · 0 comments
Owner

We use Conventional Commits to help standardize our commits and generate release notes. However, we do not yet have documentation on what types and scopes we actually use. This issue tracks the current option list and is open to discussion until the code stabilizes. Please join in on the discussion 😊

Below the evolving draft follows:

Type

  • build
  • chore
  • ci
  • docs
  • feat
  • fix
  • perf
  • refactor
  • revert
  • style
  • test

Scope

  • auth - authentication or authorization
  • legal
  • core
  • db
  • deps - dependencies
  • meta
  • devex - developer experience
  • security - cybersecurity
  • route
  • storage - anything s3 related

Until the type and scope stabilizes, commits are not expected to be 100% consistent (we do our best).

We use `Conventional Commits` to help standardize our commits and generate release notes. However, we do not yet have documentation on what types and scopes we actually use. This issue tracks the current option list and is open to discussion until the code stabilizes. Please join in on the discussion 😊 Below the evolving draft follows: ## Type * build * chore * ci * docs * feat * fix * perf * refactor * revert * style * test ## Scope * auth - authentication or authorization * legal * core * db * deps - dependencies * meta * devex - developer experience * security - cybersecurity * route * storage - anything s3 related --- Until the type and scope stabilizes, commits are not expected to be 100% consistent (we do our best).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: libscie/researchequals-api#28
No description provided.