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

What's the use case for committing both the freshly created file and it's exclusion in .gitignore?

From
BKBartosz Konikiewicz <izdwuut@gmail.com>
Date
Aug 9, 2018, 11:04 UTC
Message-ID
<CAAdU=LuNn7qdXf81C3-3=0uh7NOSihm3U3dfDcXPiKxfaZMaFQ@mail.gmail.com>
Hi there!

I hope that the subject of my message (i.e. the question) is exhaustive enough, so I'll just stick to reproducing my issue.

Steps to reproduce:
1. Create a new file.
2. Stage the file.
3. Add the file to .gitignore.
4. Stage the .gitignore.
5. Commit changes.

I imagined that the file would now be removed from the stage (because it's ignored now and not yet committed) but it isn't. Where this behavior would be desirable? I know that a 'git add' command can be invoked with an '-f' flag, which would yield the same result, but I can't come up with an explanation where can it be applied.

Next: Jeff King
Message 1 of 5 in “What's the use case for committing both the freshly created file and it's exclusion in .gitignore?”
  1. Bartosz KonikiewiczAug 9, 2018
  2. Jeff KingAug 9, 2018
  3. Jonathan NiederAug 10, 2018
  4. Bartosz KonikiewiczAug 10, 2018
  5. brian m. carlsonAug 10, 2018

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.