-
Notifications
You must be signed in to change notification settings - Fork 2
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
Rename for npm publish #40
Comments
Does this order of operations look wrong to anyone? |
Seems fine to me! |
One nice thing is that GitHub redirects old repo names to their new ones, so the last step is likely not a requirement (though would be a best practice for anything we're still actively working on). |
I'm going through and cleaning up old issues — any objections to me finishing this task off? |
@spaceninja I don't know why I didn't see this question till now. It's probably too little too late, but no, no objections at all. |
Eek! I missed this as well, @spaceninja! 😬 I agree with @tylersticka! 🙂 |
name: @cloudfour/hbs-helpers
.npm version
to create new version and tagnpm publish
repository: cloudfour/hbs-helpers
.cloudfour/core-hbs-helpers.git#
endpoints on older projects./CC @tylersticka @mrgerardorodriguez
The text was updated successfully, but these errors were encountered: