git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: basics - auto staging?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 30, 2025, 16:44 UTC
Message-ID
<xmqqbjsd38h7.fsf@gitster.g>
In-Reply-To
<10c9da5c-234c-4a40-bbff-91ba820dd970@wszib.edu.pl>
Marcin Mikłas <m.miklas@wszib.edu.pl> writes:
Show 8 quoted lines
> when I execute
> git commit file.txt
> (by listing file as argumentbut without the -a switch) for a file
> file.txt that I have made changes without staged them in the index,
> the changes are still commited.
> Is there a way to make this work like command
> git commit
> without committing the changes that are not staged in the index?
I do not think there is.

The "git commit --only [<pathspec>...]" mode (which is the default) was introduced as a variant whose blast radius is much smaller than the "git commit --include [<pathspec>...]" mode (which was the only mode before "--only" was introduced), but what you seem to be after is a mode that is even finer-grained one.

I do not offhand see a reason why such a mode should not exist. It would be called the "git commit --cached [<pathspec>...]" mode (that would be listed next to the existing "--only" and "--include" modes in the documentation), by taking inspiration from the name of another command "git diff --cached [<pathspec>...]" (i.e., use only the contents already added to the index), if we were to add one.

Previous: Marcin Mikłas
Message 2 of 2 in “basics - auto staging?”
  1. Marcin MikłasApr 30, 2025
  2. Junio C HamanoApr 30, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.