Branch Naming

General branch naming convention for Sentry repositories.

Use the format <type>/<short-description>:

  • type: one of feat, fix, ref, perf, docs, test, ci, build, chore, style, meta, license
  • short-description: what the change is about, in kebab-case

For example: feat/add-resolve-action or fix/empty-reference-handling.

Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").