-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Readme: Version Update Rules #223
Conversation
41b85c6
to
b04ae22
Compare
b04ae22
to
6e5cee4
Compare
6e5cee4
to
5f0fab8
Compare
README.md
Outdated
@@ -33,13 +33,19 @@ npm install | |||
|
|||
npm install | |||
|
|||
3. Tag a new version by running the following command: `npm version [ major | minor | patch ]`. Choose `major`, `minor`, or `patch` depending on the kind of update according to [Semantic Versioning](https://semver.org) rules. | |||
## Tag a Version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please turn this back into an enumerated list item. When you made it into a heading, it interrupted the logical flow of the document.
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Set of rules for Unified Schema Versioning on the Notices producers document:
(a) Includes version type
(b) Announce to team and community
(c) Mission page rule
Resolves ##142