Notes on how to release a new gem version #117
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * on the master branch, run: | ||
|
|
||
| ```sh | ||
| $ git commit -m "bump vX.X.X" |
There was a problem hiding this comment.
I like @rsanheim's idea of removing $, so the lines are copy/pastable. Thoughts?
There was a problem hiding this comment.
Can we just automate the whole thing like we do for Octokit?
There was a problem hiding this comment.
@pengwynn love it. Commit incoming.
|
@simeonwillbanks I tried it for a while, but prefer just updating CHANGELOG.md. Since the gem is pushed up, the download doesn't need to live with Releases. |
|
@jch sounds good. |
jch
added a commit
that referenced
this pull request
Feb 21, 2014
Notes on how to release a new gem version
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Opening PR for comments. cc @simeonwillbanks @rsanheim #116 (comment)
I know we could add a gem rake task, but I prefer this route since it's simple enough and doesn't hide any steps.