-
Notifications
You must be signed in to change notification settings - Fork 30
Automate release process #54
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
Conversation
The normal workflow should be: 1) Make your linux_admin code changes. 2) Test and commit these changes. 3) When ready for a new tag... 4) Run rake release 5) This will invoke the update_changelog rake task, it will ask you to: 6) Update LinuxAdmin::VERSION. 7) Verify that the script correctly added the commits since the last tag to the beginning of the CHANGELOG.md. 8) Add the correct version information before these commits. 9) Commit these changes 10) Hit enter and rake release will be run to create the tag, and push the version to rubygems.org.
@jrafanie @Fryguy Building on LJ's #26 ... let me know what you think You can try it yourself by running
Done:
TODO:
|
Not sure if this should be merged here, I think it is a perfect candidate for a git submodule |
Checked commits bdunne@3241888 .. bdunne@e361a91 with rubocop Rakefile
tasks/release.rake
|
Closing as stale, we can re-open if this becomes active again. |
No description provided.