Skip to content

Latest commit

 

History

History
22 lines (13 loc) · 869 Bytes

MAINTAINING.md

File metadata and controls

22 lines (13 loc) · 869 Bytes
Raw

Maintaining

This guide is intended for maintainers (anybody with commit access).

Code of Conduct

Please make sure you're familiar with and follow the CODE_OF_CONDUCT.md.

Reviewing Pull Requests

  1. Ensure all checklist items are completed.
  2. Ensure any architectual decisions are captured in /docs/adr.

Approving Pull Requests

  1. Use "Squash and Merge". This keeps a clean history in master, with a full history available in Pull Requests.
  2. Ensure the merge message conforms to Conventional Commits spec.
  3. Breaking changes? Ensure the commit message contains the text BREAKING CHANGE:.

Releasing

Releasing is handled automatically when merging to master, powered by CircleCI and semantic-release.