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

Add documentation on how to prepare commits #701

Merged
merged 1 commit into from
Apr 10, 2020

Conversation

gonzaponte
Copy link
Collaborator

This is a first attempt in documenting how to make a good commit, building on what's already described in contributing.rst and making it a bit more specific.

I intend to update this PR with some common practices that don't follow these guidelines to make a clearer picture.

@gonzaponte gonzaponte requested a review from mmkekic March 5, 2020 16:57
doc/commits.rst Outdated
For instance, do not mix cosmetical changes with other, more relevant ones.

- Commit frequently and in an incremental manner.
Do not be afraid of making too many commits, they can be merged afterwards.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Careful, "merge" has a very specific meaning in git, and not the one you are trying to convey here: "squash".

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, you are right. I was actually thinking that maybe it would be more descriptive for people that are not familiar with git, but it cannot be used like this.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand completely where you're coming from. How about: "they can be combined afterwards. (This is known as squashing in git.)"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that's nice.

@gonzaponte gonzaponte changed the title Add documentation of how to prepare commits Add documentation on how to prepare commits Mar 11, 2020
@gonzaponte gonzaponte force-pushed the docs.commit-guide branch 2 times, most recently from c9bcf77 to 1b831b6 Compare April 10, 2020 15:29
Copy link
Collaborator

@mmkekic mmkekic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds a best practice guideline on how and when to commit. Hopefully the developers will follow it, which would not only make the history cleaner but also immensely ease the review process. Thanks for taking time to make this document!

@bpalmeiro bpalmeiro merged commit aa05f82 into next-exp:master Apr 10, 2020
@gonzaponte gonzaponte deleted the docs.commit-guide branch April 10, 2020 18:45
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

Successfully merging this pull request may close these issues.

4 participants