> the file is created inside the project, and Claude Code only adds it to your global git ignore, not the repo's .gitignore. So a fresh clone or a second machine commits it like any other file

A fresh clone wouldn’t have the file. This claim doesn't make any sense.

The only way I can see this getting committed is if someone edited their global .gitignore or, more likely, did a whole directory transfer to do a different machine to work on.

▲

shmulc a day ago | parent [-]

Fair, “fresh clone” was wrong. It happens on a new machine or container without the global ignore, in a copied project folder, or once the file has been committed, since ignore rules don’t apply to tracked files.

▲

CrimsonRain 20 hours ago | parent | next [-]

Why are you copying instead of git clone?

▲

hathawsh 20 hours ago | parent [-]

The new wave of git users (coming from AI) don't know what git is.

	▲	yubblegum 17 hours ago \| parent [-]
		I wonder how many of this type are 'senior/principle software engineers' employed by our AI vendor overlords. This situation is the inevitable result of vocal VCs (ahem) poo pooing "age" and "experience" and promoting youth as a 'requirement' starting in the '00s, coupled with these same VCs now attempting to hijack an entire industry to run on their obviously immature and buggy and frankly possibly dangerous products. The silver lining in all this is all of us very experienced "ancient" software practitioners will likely be in demand again. In a sane world, of course.

▲

rendaw a day ago | parent | prev [-]

In that case what relevance does the gitignore file have at all?