You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically, tag with the current value of __version__. Fail if that tag already exists.
Possibly we should be creating annotated tags (see below):
git tag -a -m "" $version
Push the tag to origin. To do this for a commit which is already pushed, we might need::
git push --follow-tags
--tags pushes all tags on every branch, which is probably not desired. e.g. some will be private development status, some might be on distant or unreachable branches, etc.
--follow-tags was designed to fix this, it only sends tags on ancestors of the current commit, and also only sends annotated tags.
The text was updated successfully, but these errors were encountered:
tartley
added
the
process
Changes in our development process, CI, package building, releases, etc
label
Oct 15, 2020
tartley
changed the title
'make release' should tag & push
'make release' should tag the commit
Oct 15, 2020
As is described in README-hacking
Specifically, tag with the current value of
__version__
. Fail if that tag already exists.Possibly we should be creating annotated tags (see below):
Push the tag to origin. To do this for a commit which is already pushed, we might need::
--tags
pushes all tags on every branch, which is probably not desired. e.g. some will be private development status, some might be on distant or unreachable branches, etc.--follow-tags
was designed to fix this, it only sends tags on ancestors of the current commit, and also only sends annotated tags.The text was updated successfully, but these errors were encountered: