It is to help with bisect operations when things start failing ... helps us it revert and build faster. also with cherry picking features / fixes to previous versions . And keeping the git history clean with no unnecessary “merge commits”.
Regards Naba On Fri, Dec 13, 2019 at 2:25 PM Kirk Lund <kl...@apache.org> wrote: > -1 I really like to sometimes have more than 1 commit in a PR and keep them > separate when they merge to develop > > On Tue, Oct 22, 2019 at 5:12 PM Nabarun Nag <n...@pivotal.io> wrote: > > > Hi Geode Committers, > > > > A kind request for using squash commit instead of using merge. > > This will really help us in our bisect operations when a > > regression/flakiness in the product is introduced. We can automate and go > > through fewer commits faster, avoiding commits like "spotless fix" and > > "re-trigger precheck-in" or other minor commits in the merged branch. > > > > Also, please use the commit format : (helps us to know who worked on it, > > what is the history) > > > > > > > > * GEODE-xxxx: <brief intro > > > * explanation line 1 * explanation line 2* > > > > This is not a rule or anything, but a request to help out your fellow > > committers in quickly detecting a problem. > > > > For inspiration, we can look into Apache Kafka / Spark where they have a > > complete linear graph for their main branch HEAD [see attachment] > > > > Regards > > Naba. > > > > > > >
