README.md in hashematics-1.0.0 vs README.md in hashematics-1.1.0

- old
+ new

@@ -381,16 +381,18 @@ ### Handling Blanks Records with blank ID's are ignored by default. This is due to the flat nature of the incoming data. Take the following example: -ID # | First Name | Last Name | Costume ID # | Costume Name | Costume Color ----- | ---------- | --------- | ------------ | ------------ | ------------- -1 | Bruce | Banner | 3 | Basic Hulk | Green -2 | Tony | Stark | | | - | | | 4 | Undercover | Purple +ID # | First Name | Last Name | Costume ID # | Costume Name | Costume Color +------ | ---------- | --------- | ------------ | ------------ | ------------- +1 | Bruce | Banner | 3 | Basic Hulk | Green +2 | Tony | Stark | *null* | *null* | *null* +*null* | *null* | *null* | 4 | Undercover | Purple +*Note: null is shown for blank values so the markdown renders properly.* + This is interpreted as: * Bruce Banner is an avenger and has 2 costumes * Tony Stark is an avenger but has no costumes * An undercover purple costume exists, but belongs to no avenger @@ -648,13 +650,10 @@ 1. Merge Pull Request into master 2. Update ```lib/hashematics/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 hashematics` -7. Publish package to RubyGems: `gem push hashematics-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` +6. Run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## License This project is MIT Licensed.