-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add release automation and documentation #77
Add release automation and documentation #77
Conversation
page](https://github.com/jupyterhub/repo2docker-action/releases) where | ||
you create a new GitHub release. Enter a _tag name_ and _release name_ of | ||
"vX.Y.Z". Doing so will automatically update the "vX" branch allowing users to | ||
reference this action with `jupyterhub/repo2docker-action@vX`. |
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.
Make a note that you have to change the docs and examples to point to the new version?
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.
Done in 90f2162!
@yuvipanda go for merge on this? |
I'll go for a self-merge on this. This is the pattern we have adopted in the other github actions we maintain in the jupyterhub org. |
This PR aligns this repository that contains a GitHub action definition with some practices for the other repositories in the jupyterhub org that also defines GitHub actions.
With this in place and a new release made, we can also update the readme to suggest referencing
@v1
or similar rather than@master
.