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
It would be helpful for seeing the state of the code at specific versions if each of them were tagged here in the repo instead of just released on NPM.
To tag older versions with the proper timestamp you can use a script like the following on Windows:
tag-release.ps1:
param([string]$version="")
$message=(git log -1--pretty=%B | head -1)
$env:GIT_COMMITTER_DATE=(git show --format=%aD | head -1)
git tag -a "$version"-m "$message"
This is a slightly modified version of this answer which has a version for *NIX shells.
The text was updated successfully, but these errors were encountered:
It would be helpful for seeing the state of the code at specific versions if each of them were tagged here in the repo instead of just released on NPM.
To tag older versions with the proper timestamp you can use a script like the following on Windows:
tag-release.ps1:
This is a slightly modified version of this answer which has a version for *NIX shells.
The text was updated successfully, but these errors were encountered: