We could enforce this if we all agree. Il giorno gio 12 feb 2026 alle ore 09:33 Pasquale Congiusti < [email protected]> ha scritto:
> I think it makes sense. If there are several commits that benefit the > history to be separated, then they should be provided with separated PRs. A > PR is the unit of the change, so, all commits belonging to that unit should > be squashed. If the commits belongs to different means, then they should > belong to separate PRs. > > Pasquale. > > On Thu, Feb 12, 2026 at 9:17 AM Claus Ibsen <[email protected]> wrote: > > > On Thu, Feb 12, 2026 at 9:07 AM Aurelien Pupier via dev < > > [email protected]> wrote: > > > > > Hello, > > > > > > When the list of commits has been curated for a coherent history > already, > > > it can also be interesting to use the Rebase and merge. > > > > > > > No we dont want 15 commits for a single thing. It also makes git bisect > > much harder. > > And any kind of git diff and whatnot. > > > > We should make the github force squash only. > > > > > > > > > ________________________________ > > > From: Claus Ibsen <[email protected]> > > > Sent: Wednesday, February 11, 2026 8:41 PM > > > To: dev <[email protected]> > > > Subject: [EXTERNAL] Merging PRs using squash and merge > > > > > > Hi > > > > > > When merging PRs from github, then remember to "squash and merge" so > its > > > only 1 commit. > > > > > > > > > -- > > > Claus Ibsen > > > > > > Unless otherwise stated above: > > > > > > Compagnie IBM France > > > Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex > > > RCS Nanterre 552 118 465 > > > Forme Sociale : S.A.S. > > > Capital Social : 664 614 175,50 € > > > SIRET : 552 118 465 03644 - Code NAF 6203Z > > > > > > > > > -- > > Claus Ibsen > > >
