Hi Christoph, The method you described looks great. Squashing with rebase interactive works fine, with choosing what commits to keep and what commits to squash into the kept ones. This can be done by merger or author.
Merging a pull request with squashing in github will set the author's commit to the person who merge it. The same things happens with *git merge --squash <branch>* If you agree, what would be the best way to propagate this information so that everyone use this method, when squashing is needed? Regards, Alex On Sun, Sep 22, 2019 at 3:03 PM Christoph M. Becker <cmbecke...@gmx.de> wrote: > On 20.09.2019 at 12:59, Alexandru Pătrănescu wrote: > > > Can you let us know what you used as it's doing the job well :) > > CLI git merge or another UI; which one? > > I'm usually using TortoiseGit, but basically I'm doing > > git rebase -i HEAD~<number of commits to squash> > > > I'm also curious what will happen if there would be two authors on the > same > > branch/pull request. > > Is it interactive or pre-configured to use author of the first commit, > last > > commit, most of the commits? > > In this case I likely would not squash commits of different authors. An > alternative would be to append the following to the commit message: > > Co-authored-by: name <n...@example.com> > > -- > Christoph M. Becker >
