-
Notifications
You must be signed in to change notification settings - Fork 78
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 docs on creating new releases #287
base: main
Are you sure you want to change the base?
Conversation
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.
Thanks for adding these details!
Co-authored-by: Sandra McCann <[email protected]>
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.
LGTM!
hm. sounds great. I was actually unsure if more things were needed than only tagging. Nevertheless, fwiw, my current issue about releasing is more about knowing if I have to ping someone to get a new release or if I have enough rights to do it myself. |
hey @apatard I see you're in the community team with maintain access: https://github.com/orgs/ansible-community/teams/molecule maintainer permissions should be good for creating tags and publishing releases: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#permissions-for-each-role |
@oraNod that's great. I'll try to find some time tomorrow to do a release (and at least merge this PR) |
2. Create a new tag and push it to the repo. | ||
|
||
```bash | ||
git tag <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.
What about signed tags ?
Update the README to explain the release process.