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
- As a convenience, a tool called `semantic-git-commit-cli` is installed in node_modules so you can commit using
35
-
`npx sgc` instead of `git commit`. This tool will ask a series of questions and generate a properly-formatted
36
-
commit message for you. You can still run `git commit` and format the message properly yourself if you prefer.
33
+
[conventional commit format](https://www.conventionalcommits.org/en/v1.0.0/). Our CI will check this and fail any PRs that are formatted incorrectly.
34
+
- This repo is [commitizen friendly](https://github.com/commitizen/cz-cli), so you can use the `cz` cli to help create your commits.
37
35
- Lint and test before submitting the pull request by running `$ npm test`
38
36
- Write a convincing description of why we should land your pull request. Answer _why_ it's needed and provide use-cases.
39
37
- Make the pull request from a [topic branch](https://github.com/dchelimsky/rspec/wiki/Topic-Branches) (not master)
40
-
- You might be asked to do changes to your pull request. There's never a need to open another pull request –[just update the existing one.](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
38
+
- You might be asked to do changes to your pull request. There's never a need to open another pull request –[just update the existing one.](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
41
39
42
40
## [Finding contributions to work on](labels/help%20wanted)
0 commit comments