-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Create publish-gem.yml #405
Conversation
Welcome! Congrats on your first pull request to the Minimal theme. If you haven't already, please be sure to check out the contributing guidelines. |
Thanks for this. Do you mind providing a bit more information about what problem you're trying to solve? |
Congrats on getting your first pull request to the Minimal theme merged! Without amazing humans like you submitting pull requests, we couldn’t run this project. You rock! 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tsusdere Following up from github/jekyll-commonmark-ghpages#34 (review) …
(the above will probably apply to all the repos, themes, plugins where this was copied over)
## Publishing Gem | ||
In order to publish the Gem bump the version in *this file*, commit, create a tag with the new version number, and finally push the commit and tag to the repo. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"…in this file" — this file is CONTRIBUTING.md — wasn't there supposed to be a link? Probably to the gemspec?
Anyways the workflow isn't tied to tags, but to releases. So the instructions don't seem correct?
Add workflow for auto-publishing gem