-
Notifications
You must be signed in to change notification settings - Fork 14
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
rewrite history #5
Comments
Is this really necessary? This seems quite difficult since the files have been moved around several times. The stuff I'd want to keep:
|
yes, i'll try to make up something in my fork and see |
here's something i quickly throw together: https://github.com/glensc/jsmin-php/tree/rebase and finally as you wanted it: |
so if you still think it's good idea, you should probably fetch the wanted master branch, git reset hard and push -f to github to ovewrite your master with the new one. (can give exact commands if needed). and after that the pull requests should work fine. |
Your filtering looks good. Still not convinced it's a good idea. This is being used on Packagist; how will it affect those users? |
really up to you. but packagist problem is what? if tag by same version is recreated, it should no problem for clients to understand git forced push. close if you reject the idea. otherwise i will have to work more on this, as somewhy last commit removed all files. huh |
hi @mrclay,
i was wondering, if you be interesting doing git filter branch to trim history to include only files that are jsmin-php related.
it would be probably very good idea to do that before you merge any of the PRs here.
The text was updated successfully, but these errors were encountered: