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

consider adopting a ‘squash only’ merge policy #48

Closed
wbolster opened this issue Mar 8, 2019 · 2 comments
Closed

consider adopting a ‘squash only’ merge policy #48

wbolster opened this issue Mar 8, 2019 · 2 comments

Comments

@wbolster
Copy link
Contributor

wbolster commented Mar 8, 2019

you may want to consider a ‘squash only’ setting for this project (repo setting in github). history like this:

image

is a pain to look at, and not useful at all for debugging (e.g. git bisect). all that noise in small commits after a review + the merges make the main changes invisible.

@wbolster
Copy link
Contributor Author

wbolster commented Mar 8, 2019

(feel free to ignore/close)

@wbolster wbolster changed the title consider adoping a ‘squash only’ merge policy consider adopting a ‘squash only’ merge policy Mar 8, 2019
@tomchristie
Copy link
Member

Will switch the default to “squash and merge” yup.

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

No branches or pull requests

2 participants