From 4a55603d10ef268b133b5d386a896a83e454e452 Mon Sep 17 00:00:00 2001 From: Will Norris Date: Wed, 26 Jun 2013 18:48:02 -0700 Subject: [PATCH] remove note about squashing commits Squashing is a little advanced, and easy to screw up with github pull reqeusts. If needed, I generally squash them myself anyway. --- CONTRIBUTING.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1072a1b..ec7786b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -52,12 +52,6 @@ again. This provides consistency throughout the project, and ensures that commit messages are able to be formatted properly by various git tools. - 1. If you made lots of small commits in the process of developing your patch, - it's often helpful to [squash them into a single commit][squash]. For - larger patches, multiple commits may actually be clearer. Just use your - best judgement, but be aware that the reviewer may ask you to squash them, - or just squash them herself before pushing your patch. - 1. Finally, push the commits to your fork and submit a [pull request][]. [forking]: https://help.github.com/articles/fork-a-repo