snabbdom/CONTRIBUTING.md

# Contributing

## Making a release

You will need a personal GitHub API token (this is used to create the release on GitHub). You can obtain one [here](https://github.com/settings/tokens/new?scopes=repo&description=release-it) (it only needs "repo" access, not "admin" or other scopes).

Make sure the token is available with an environment variable. It's best to put this in `~/.profile`:

```sh
export GITHUB_TOKEN="<token from step 1>"
```

If you saved the token to `~/.profile` you will not have to repeat this in the future.

Then simply run `npm run release`. This will automatically determine the new version number based on the commit messages, create the commit, tag, github release and publish to npm.
ux(docs): provide a release changelog Also set up a documented release process. Fixes #670. 5 years ago			`# Contributing`

			`## Making a release`

chore(tools): replace standard-version with release-it release-it automates all the steps defined in CONTRIBUTING.md. In addition to that it can also create GitHub releases with the relevant part of the CHANGELOG 4 years ago			`You will need a personal GitHub API token (this is used to create the release on GitHub). You can obtain one [here](https://github.com/settings/tokens/new?scopes=repo&description=release-it) (it only needs "repo" access, not "admin" or other scopes).`
ux(docs): provide a release changelog Also set up a documented release process. Fixes #670. 5 years ago
chore(tools): replace standard-version with release-it release-it automates all the steps defined in CONTRIBUTING.md. In addition to that it can also create GitHub releases with the relevant part of the CHANGELOG 4 years ago			Make sure the token is available with an environment variable. It's best to put this in `~/.profile`:
ux(docs): provide a release changelog Also set up a documented release process. Fixes #670. 5 years ago
chore(tools): replace standard-version with release-it release-it automates all the steps defined in CONTRIBUTING.md. In addition to that it can also create GitHub releases with the relevant part of the CHANGELOG 4 years ago			```sh
			`export GITHUB_TOKEN="<token from step 1>"`
			```
ux(docs): provide a release changelog Also set up a documented release process. Fixes #670. 5 years ago
chore(tools): replace standard-version with release-it release-it automates all the steps defined in CONTRIBUTING.md. In addition to that it can also create GitHub releases with the relevant part of the CHANGELOG 4 years ago			If you saved the token to `~/.profile` you will not have to repeat this in the future.
ux(docs): provide a release changelog Also set up a documented release process. Fixes #670. 5 years ago
chore(tools): replace standard-version with release-it release-it automates all the steps defined in CONTRIBUTING.md. In addition to that it can also create GitHub releases with the relevant part of the CHANGELOG 4 years ago			Then simply run `npm run release`. This will automatically determine the new version number based on the commit messages, create the commit, tag, github release and publish to npm.