Skip to content
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

Discuss squashing commits #6

Open
codersquid opened this issue Oct 1, 2014 · 3 comments
Open

Discuss squashing commits #6

codersquid opened this issue Oct 1, 2014 · 3 comments

Comments

@codersquid
Copy link

Should you recommend squashing commits as a practice for submitting code to review/merge?

@bkatiemills
Copy link
Member

To be honest, and maybe I'm a horrible person, I never do this :)

I think it's definitely worth touching on, and fits in the 'crafting a contribution' theme you've been building up. It might be more of a master class point, but will definitely keep it in mind when that content gets developed - thanks as always!

@codersquid
Copy link
Author

Perhaps this issue can be closed, unless you want to have some lessons on the mechanics of squashing commits.

If the point of view is someone crafting a contribution to an existing project, emphasizing that someone should review the contributor guidelines of the project is probably good enough. If the maintainors have a strong preference for squashing commits, they'll mention it.

@bkatiemills
Copy link
Member

But, there's also a big element in these lessons of helping people set those preferences in the first place; when someone comes to the idea of DVCS for the first time, I would be really impressed if the concept of commit squashing just came to them on their own! I'm going to leave this open under the 'Contrib Crafting' tag, so I remember to consider folding it in to lessons about how to define a great contribution when the time comes - need to finish the intro material first though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants