git untracks my files

git untracks my files

[russell thamm]

Under Ubuntu 20.04, when my program modifies one of its log files, git 
marks it as untracked. Other files that my program modifies are 
correctly marked as modified.

This does not happen under Windows 11 and it didn't use to happen under 
Ubuntu.

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

Pulled the project, built and ran my program which modified log files.

What did you expect to happen? (Expected behavior)

I expected the log files to be marked as modified.

What happened instead? (Actual behavior)

The log files were marked as untracked.

What's different between what you expected and what actually happened?

I do not expect git to untrack my files.

Anything else you want to add:

Only happens on Ubuntu 24.04, and not on Windows 11.

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.43.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 
20:41:06 UTC 2024 x86_64
compiler info: gnuc: 13.2
libc info: glibc: 2.39
$SHELL (typically, interactive shell): /bin/bash


[Enabled Hooks]

Re: git untracks my files

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]

On 2024-09-05 at 04:51:56, russell thamm wrote:
> Under Ubuntu 20.04, when my program modifies one of its log files, git marks
> it as untracked. Other files that my program modifies are correctly marked
> as modified.
> 
> This does not happen under Windows 11 and it didn't use to happen under
> Ubuntu.
> 
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
> 
> What did you do before the bug happened? (Steps to reproduce your issue)
> 
> Pulled the project, built and ran my program which modified log files.
> 
> What did you expect to happen? (Expected behavior)
> 
> I expected the log files to be marked as modified.
> 
> What happened instead? (Actual behavior)
> 
> The log files were marked as untracked.
> 
> What's different between what you expected and what actually happened?
> 
> I do not expect git to untrack my files.
> 
> Anything else you want to add:
> 
> Only happens on Ubuntu 24.04, and not on Windows 11.

I'm not sure that there's enough information for us to go on here.  Are
you sure the file name is exactly the same, including in case and, if
relevant, how it uses Unicode composition in the file system?  Note that
Ubuntu, as with most Unix systems, is case sensitive, and Windows is not
by default.

Can you provide us with an example shell script that can reproduce the
problem, or a repository that we can clone and build relatively easily
that demonstrates the problem?  If we had such a reproduction example,
it would be easy for us to see what the difference in behaviour is
across systems and fix it if it's a bug (or explain what's going on if
it's not).

One final note: typically log files don't belong in a repository, since
they're artifacts from building or running the program, which tend to
cause needless diff noise and merge conflicts.  Thus, usually we'd
recommend that this output not even be stored in a repository at all, so
the files should be untracked and ignored.
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]