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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -318,15 +318,18 @@ For links to `/discord/`, a redirect is configured in _netlify.toml_ to redirect
318
318
319
319
## Pull Requests
320
320
321
-
To best help facilitate contributions to the project, we have Conventional Commits configured for the project to walk you through preparing commits in the format of `<type>(<scope>):<summaryofchange>`, e.g. _bug(cli): fixed bug with the thing_. This workflow will also run your files through Prettier.
321
+
To best help facilitate contributions to the project, we have Conventional Commits configured for the project to walk you through preparing commits in the format of `<type>: #<issue><summary-of-change>`, e.g. _bug: #123 fixed bug with the thing_.
322
322
323
-
After staging the files you ready to commitwith git add, you can initiate the commit "wizard" by running:
323
+
Make sure you have run `npm run lint`, `npm run format` and `npm run test`to prepare your commit. Then, after staging your files with `git add`, you can initiate the commit "wizard" by running:
324
324
325
325
```sh
326
326
$ npm run commit
327
327
```
328
328
329
-
The PR title should match the conventional commits format as well. If you make the PR after one commit, GitHub will automatically use the first commit as the.
0 commit comments