Skip to content

Commit 0bce20e

Browse files
committed
chore(): updating contribution guidline
1 parent b1502ce commit 0bce20e

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

CONTRIBUTING.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,9 @@ And so on. The commits are then compiled into the changelog along with each rele
2626
For any contributors with release rights:
2727

2828
1. update package.json with new version bump. Refer to [semver](http://semver.org/) for versioning guidelines
29-
2. run `npm publish` to publish new version (the command wil create new build files)
29+
2. run `npm prepublish` to prepare the new version (the command will create new build files)
3030
3. commit package.json and build files
3131
4. tag commit with newest version
32+
5. push changes to Github
33+
5. run `npm publish` to publish the new version to npmjs.com
3234
5. use Github UI to create a new release

package-lock.json

+2-2
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)