-
Notifications
You must be signed in to change notification settings - Fork 7
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
Request of merging my branch #11
Comments
Open up a pull request, and we'll have a look! |
I've merged this into a 2.x branch, since I can't merge it into master. I can't re-tag 2.0.0 because the commit SHA1 is lost and the old maintainer already published 2.0.0 to NPM. What would you like to do now? |
Thank you!! Would you tell me 2.0.0 made by old maintainer? |
I don't have the old 2.0.0 commit SHA1 in Git. And npm already has a specific SHA1 attached to its published 2.0.0 version. I can't recreate 2.0.0 without access to the old Git repo that the previous maintainer deleted. I can create a 2.0.1 version off the code you gave. Would you like me to do that? |
You don't have to. |
Oh! Sorry!! Would you create a 2.0.1 version? |
Hi John,
Could you please merge my branch to your master branch?
https://github.com/lvs-shinjisueyoshi/grunt-kss/tree/v2.0.0
This is grunt-kss version 2.0.0, it's great isn't it?
Hope you like it.
Cheers,
Shinji
The text was updated successfully, but these errors were encountered: