Project

henry

0.0
No commit activity in last 3 years
No release in over 3 years
Continuously deploy your Rubygems via Travis
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.11
~> 0.8
~> 2.0
~> 0.10
~> 10.0
~> 3.0
~> 3.0
~> 1.24

Runtime

~> 1.3
~> 0.13
~> 0.19.1
~> 1.8.2
 Project Readme

Build Status Dependency Status Coverage Status Code Climate Gem Version License Badges

Henry

Henry

(Photo by davidwithacamera)

We all like continuous deployment, but when it comes to publishing Ruby gems, crafting a new version can become a royal pain. Travis's Rubygems integration makes things easier, but you still have to push a new tag and write a changelog, and who has time for that?

Henry makes things really easy, as per Github flow, master is always considered deployable. As soon as the version number is changed and everything is pushed to Travis, once the tests pass (and they will, won't they?), Henry will push a new tag and an automatically generated Changelog (via the magic of github-changelog-generator). Assuming you have Travis set up with Rubygems integration, it will then build the latest tag, and publish it directly to Rubygems. Easy huh?

Usage

In your project directory, first run gem install henry and henry bootstrap and follow the onscreen prompts.

Then push up your changes, and sit back and relax, safe in the knowledge that you'll never forget to push a new gem version again.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/theodi/henry. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

License

The gem is available as open source under the terms of the MIT License.