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
This should do the trick with the missing tag, using the 1.0 commit e8cc698.
# set the HEAD to the old commit that we want to tag
git checkout e8cc69868af427f5fd03c8ad125b493cbf2e8292
# temporarily set the date to the date of the HEAD commit, and add the tag
GIT_COMMITTER_DATE="$(git show --format=%aD | head -1)" \
git tag -a v1.0.0 -m"First Stable Release"
# push to GitHub
git push origin v1.0.0
# set HEAD back to whatever you want it to be
git checkout master
Then someone with release rights could either use the GH CLI or click on the tag to convert it to a release, possibly adding some highlights about the release or leave it as "First Stable Release" and ideally adding one artifact: the vscode-org-mode.org-mode-1.0.0.vsix.
This would also allow people to easily get the vsix from here if they need to install it manually.
... and of course a tagged version 1.1.0 would be marvelous, too.
The text was updated successfully, but these errors were encountered:
This should do the trick with the missing tag, using the 1.0 commit e8cc698.
Then someone with release rights could either use the GH CLI or click on the tag to convert it to a release, possibly adding some highlights about the release or leave it as "First Stable Release" and ideally adding one artifact: the vscode-org-mode.org-mode-1.0.0.vsix.
This would also allow people to easily get the vsix from here if they need to install it manually.
... and of course a tagged version 1.1.0 would be marvelous, too.
The text was updated successfully, but these errors were encountered: