-
Notifications
You must be signed in to change notification settings - Fork 86
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
Squash git history into one 'initial commit' #2
Comments
Do you have any concerns in regard to the commit messages itself? Seeing the history of the project is a good way to learn about the component for future contributors. Just my 2 cents. |
I think the benefit of what @mkalmes mentions outweighs the vanity of having one initial monster commit. |
I'm fine with keeping my 💩 around. |
To late, but I think we should keep it. A project with a (especially not that clean) history before the coming out looks much more friendly. |
I think we should squash the history before releasing the library to the public.
The text was updated successfully, but these errors were encountered: