README.md in tree_branch-1.0.0 vs README.md in tree_branch-1.1.0
- old
+ new
@@ -1,8 +1,8 @@
# TreeBranch
-[](https://travis-ci.org/bluemarblepayroll/tree_branch)
+[](https://badge.fury.io/rb/tree_branch) [](https://travis-ci.org/bluemarblepayroll/tree_branch) [](https://codeclimate.com/github/bluemarblepayroll/tree_branch/maintainability) [](https://codeclimate.com/github/bluemarblepayroll/tree_branch/test_coverage) [](https://opensource.org/licenses/MIT)
This library allows you to traverse an entire tree structure, compare all nodes, and choose a tree structure to return. The basic input is defined as:
1. Initial Tree structure root node (required)
2. Comparison classes or functions (optional)
@@ -415,15 +415,15 @@
Note: ensure you have proper authorization before trying to publish new versions.
After code changes have successfully gone through the Pull Request review process then the following steps should be followed for publishing new versions:
1. Merge Pull Request into master
-2. Update [lib/tree_branch/version.rb](https://github.com/bluemarblepayroll/tree_branch/blob/master/lib/tree_branch/version.rb) [version number](https://semver.org/)
-3. Bundle
-4. Update CHANGELOG.md
-5. Commit & Push master to remote and ensure CI builds master successfully
+2. Update ```lib/tree_branch/version.rb``` using [semantic versioning](https://semver.org/)
+3. Install dependencies: ```bundle```
+4. Update ```CHANGELOG.md``` with release notes
+5. Commit & push master to remote and ensure CI builds master successfully
6. Build the project locally: `gem build tree_branch`
-7. Publish package to NPM: `gem push tree_branch-X.gem` where X is the version to push
+7. Publish package to RubyGems: `gem push tree_branch-X.gem` where X is the version to push
8. Tag master with new version: `git tag <version>`
9. Push tags remotely: `git push origin --tags`
## License