-
Notifications
You must be signed in to change notification settings - Fork 13
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
All git tags missing #49
Comments
I'm sure there;'s tons of ways to automate npm publishing, if needed I can port my own version to this repo, which is just plain GitHub Actions (no extra plugin): |
For small projects like this I don't bother with all of that extra work, I have too many small repos to make it worth my time. |
Extra work of what? publishing npm release manually seems extra work to me. The repo I linked, after initial setup making a release is pushing a git tag. |
And I do like transparency, like what did you do for 1.4.1 release, why it has changes missing? See: |
Finished this comment: With this PR (read the body of it how to finish the setup): |
It's a cool idea but this is just one repo of many, it'd be an edge case where it's the only one which deploys this way |
Loosely created tags from commit messages. not all tags were created as there aren't even commits for some releases (delivering spyware probably :D)
I believe you can grab the tags like this and then push to your remote:
|
Seems this repo lacks all git tags for npm releases!
The text was updated successfully, but these errors were encountered: