From 379ffa5d822cfbb995a87390b184c1a0d00881a4 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Tue, 5 Apr 2016 00:31:06 -0700 Subject: CONTRIBUTING.md: Add instructions on shipping a new release [ci skip] --- CONTRIBUTING.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'CONTRIBUTING.md') diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b6ac8cb..0f5ecc0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -20,5 +20,14 @@ Assuming that you don't see any red, you're ready to go. Just be sure to run `gr 5. Update the documentation to reflect any changes. 6. Push to your fork and submit a pull request. -### Licensing +## Licensing By contributing your code, you agree to license your contribution under [the MIT License](https://github.com/twbs/grunt-bootlint/blob/master/LICENSE-MIT). + +## Shipping a release +1. Update the `version` field in `package.json` +2. Add an entry in the "Release History" section of `README.md`. +3. Tag a new [Release](https://github.com/twbs/grunt-bootlint/releases) in GitHub and write a summary of the changes in the Release's description. +4. `git checkout master` and `git pull` +5. `git status` to ensure you have no uncommitted local changes or extraneous untracked files. +6. `npm publish` +7. Done. Congratulations! -- cgit v1.2.3