-
Notifications
You must be signed in to change notification settings - Fork 336
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
Document how to tag releases #1272
Labels
good first issue
Good for newcomers
Comments
ansible-documentation-bot
bot
added
the
needs_triage
Needs a first human triage before being processed.
label
Apr 16, 2024
samccann
removed
the
needs_triage
Needs a first human triage before being processed.
label
Apr 23, 2024
I'd like to give this a go. Could you please assign it to me? |
With the PR approved, should this be closed? |
Thanks again for the docs contribution @x1101 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Purpose is to add instructions to the README on how to create tags that correspond to the release candidates and releases available in
ansible/ansible
.Python script to create tags:
hacking/tagger/tag.py
. Basic usage is available with./tag.py --help
You need a directory with this repository (
ansible/ansible-documentation
) checked out and a directory with theansible/ansible
directory checked out.You can then run
./tag.py tag
if the upstream is configured as theorigin
remote or pass the remote flag with something like./tag.py --remote upstream tag
.The text was updated successfully, but these errors were encountered: