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
+25-15Lines changed: 25 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ The core team works directly on GitHub and all work is public.
10
10
11
11
### Development workflow
12
12
13
-
> **Working on your first pull request?** You can learn how from this *free* series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
13
+
> **Working on your first pull request?** You can learn how from this _free_ series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
14
14
15
15
1. Fork the repo and create your branch from `master` (a guide on [how to fork a repository](https://help.github.com/articles/fork-a-repo/)).
16
16
2. Run `yarn` to setup the developement environment.
@@ -20,32 +20,42 @@ The core team works directly on GitHub and all work is public.
20
20
21
21
We prefix our commit messages with one of the following to signify the kind of change:
22
22
23
-
*`fix`: bug fixes, e.g. fix incorrect error message.
24
-
*`feat`: new features, e.g. add useful API.
25
-
*`refactor`: code/structure refactor, e.g. new folder structure.
26
-
*`docs`: changes into documentation, e.g. add usage example for `getByText`.
27
-
*`test`: adding or updating tests, eg unit, snapshot testing.
28
-
*`chore`: tooling changes, e.g. change circle ci config.
29
-
*`BREAKING`: for changes that break existing usage, e.g. change API.
23
+
-`fix`: bug fixes, e.g. fix incorrect error message.
24
+
-`feat`: new features, e.g. add useful API.
25
+
-`refactor`: code/structure refactor, e.g. new folder structure.
26
+
-`docs`: changes into documentation, e.g. add usage example for `getByText`.
27
+
-`test`: adding or updating tests, eg unit, snapshot testing.
28
+
-`chore`: tooling changes, e.g. change circle ci config.
29
+
-`BREAKING`: for changes that break existing usage, e.g. change API.
30
30
31
31
Our pre-commit hooks verify that your commit message matches this format when committing.
32
32
33
33
### Linting and tests
34
34
35
35
We use `flow` for type checking, `eslint` with `prettier` for linting and formatting the code, and `jest` for testing. Our pre-commit hooks verify that the linter and tests pass when commiting. You can also run the following commands manually:
36
36
37
-
*`yarn flow`: run flow on all files.
38
-
*`yarn lint`: run eslint and prettier.
39
-
*`yarn test`: run tests.
37
+
-`yarn flow`: run flow on all files.
38
+
-`yarn lint`: run eslint and prettier.
39
+
-`yarn test`: run tests.
40
40
41
41
### Sending a pull request
42
42
43
43
When you're sending a pull request:
44
44
45
-
* Prefer small pull requests focused on one change.
46
-
* Verify that `flow`, `eslint` and tests are passing.
47
-
* Preview the documentation to make sure it looks good.
48
-
* Follow the pull request template when opening a pull request.
45
+
- Prefer small pull requests focused on one change.
46
+
- Verify that `flow`, `eslint` and tests are passing.
47
+
- Preview the documentation to make sure it looks good.
48
+
- Follow the pull request template when opening a pull request.
49
+
50
+
### Publishing a release
51
+
52
+
We use [release-it](https://github.com/webpro/release-it) to automate our release. If you have publish access to the NPM package, run the following from the master branch to publish a new release:
53
+
54
+
```sh
55
+
yarn release
56
+
```
57
+
58
+
NOTE: You must have a `GITHUB_TOKEN` environment variable available. You can create a GitHub access token with the "repo" access [here](https://github.com/settings/tokens).
0 commit comments