I manually "tested" the new --force-tag flag github-tag-version by running it against the production repos.
github-tag-version --org 'lsst' --team 'Data Management' --email 'sqre-admin@lists.lsst.org' --tagger 'sqreadmin' --debug "w.2017.30" "b2974" --force-tag
|
[master] ~/github/afw $ git fetch --all --tags --prune
|
Fetching origin
|
remote: Counting objects: 18, done.
|
remote: Compressing objects: 100% (7/7), done.
|
remote: Total 18 (delta 11), reused 18 (delta 11), pack-reused 0
|
Unpacking objects: 100% (18/18), done.
|
From github.com:lsst/afw
|
* [new branch] tickets/DM-11332 -> origin/tickets/DM-11332
|
t [tag update] w.2017.30 -> w.2017.30
|
[master] ~/github/afw $ git show-ref -d w.2017.30
|
9099d49766d32f85ae1b917c06874bca7e117534 refs/tags/w.2017.30
|
d3ef40641b9102e57e8ba7a88ffac335202b28fd refs/tags/w.2017.30^{}
|
|
I have added the ability to update a pre-existing annotated tag to github3.py. After a bunch of fiddling around trying to unwind the requests mock[ing] wrappers, as an attempt to properly unit test a top level method that results in multiple REST calls (which none of the existing unit tests seems to do), I gave up and opened PRs upstream:
sqre-codekit will need a minor update to use the tag moving feature.