2026-10-11 03:40 UTC
Had a quick playaround with it:
Yes, that does prevent gitignore files from being committed.
It does not prevent locally-created gitignore files from being applied.
But I’d say the latter is overall a good thing, as some build tools will do a echo “*” > build/.gitignore to have their build-folder add itself to the ignore-list.
Replies (3)
-
@NotSteve_@lemmy.ca 2026-10-11 03:57
What’s the benefit of scripting the wildcard gitignore over just adding build/ to the root gitignore? I guess being build directory name agnostic?
-
@otter@lemmy.ca 2026-10-11 04:36
Does it prevent the initial .gitignore from being commited too? For example, what if a file name had sensitive information. It’s bad practice, but someone might want to ignore the file while also hiding the ignore rule itself. /test/fake-person-first-last.json /test/real-person-first-last.json Someone might want to selectively omit the second file while keeping the first, but not show what they are hiding.
-
@deadbeef79000@lemmy.nz 2026-10-11 04:48
Ooh, uncomittable files are still honoured. That’s mildly interesting, I can see it being both useful and maddening.