git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matej Dujava <mdujava@kocurkovo.cz>
To: The Super Techie <thesupertechie1@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Add a git squash function?
Date: Sun, 16 Aug 2026 23:52:00 +0200	[thread overview]
Message-ID: <aoIxALomheh-3N44@kocurkovo.cz> (raw)
In-Reply-To: <bc49c03e-5a90-480e-8bfa-ad8fb8e42db2@gmail.com>

On Sun, Aug 16, 2026 at 11:49:50AM -0700, The Super Techie wrote:
>Hi,

Hi,

>
>I am a developer who often squashes their commits using Git. 
>Currently, the simplest way to squash is to run the following two 
>commands:
>
>git reset --soft HEAD~3
>
>git commit
>
>Where 3 is the number of commits that a user would like to squash. 
>However, what if there was a command like as follows:
>
>Which did the same thing? This would save quite a bit of time for 
>developers. Since some projects require the DCO, an -s flag could be 
>added which would add a sign-off to the squashed commit as well.

when later commits are adressing feedback you can do fixup! or squash!
commits and then cleanup before merge: `git rebase --autosquash HEAD~3`

>
>Has this been suggested before?

Looks like there is a v13 [0] patchset discussing similar worflow, which
started as [1].

>
>git squash 3

suggested command was `git history squash HEAD~3` but this will keep
message of the fist commit


[0] https://lore.kernel.org/git/pull.2337.v13.git.git.1786088371.gitgitgadget@gmail.com/
[1] https://lore.kernel.org/git/pull.2337.git.git.1781465141.gitgitgadget@gmail.com/

Thanks,
Matej

  reply	other threads:[~2026-08-16 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 18:49 Add a git squash function? The Super Techie
2026-08-16 21:52 ` Matej Dujava [this message]
2026-08-16 23:38   ` Bradley Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aoIxALomheh-3N44@kocurkovo.cz \
    --to=mdujava@kocurkovo.cz \
    --cc=git@vger.kernel.org \
    --cc=thesupertechie1@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).