-
Notifications
You must be signed in to change notification settings - Fork 120
Maintaining Clutch
Derek edited this page Jul 30, 2020
·
1 revision
Thank you for helping maintain Clutch! Let's strive for the best experience for both contributor and maintainer.
This guidance was heavily leveraged from envoyproxy/envoy.
- We are a small team at the moment and try to turn around reviews within one to three business days.
- See CODEOWNERS for the current list of maintainers.
- If there is a question on who should review a PR please discuss in Slack.
- Anyone is welcome to review any PR that they want, whether they are a maintainer or not.
- Please make sure that the PR title, commit message, and description are updated if the PR changes significantly during review.
- Please clean up the title and body before merging. By default, GitHub fills the squash merge title with the original title, and the commit body with every individual commit from the PR. The maintainer doing the merge should make sure the title follows the guidelines below and should overwrite the body with the original commit message from the PR (if applicable).
- As guidance, for commit messages we generally follow the format
<area>: <general description of change>
. For example,docs: add maintaining section
.
- As guidance, for commit messages we generally follow the format