3 ms·
This is slightly wrong. build/ will ignore the build directory at every level. /build will ignore the build directory at the top level. I also have no idea wha
by JoelEinbinder 3y ago
This is slightly wrong. build/ will ignore the build directory at every level. /build will ignore the build directory at the top level.
I also have no idea what it’s trying to communicate with its /*/temp/ examples
- donmcronald 3y ago> This is slightly wrong. I wonder how it does if you tell it it’s wrong. I’ve tried a few times and it seems to get confused pretty easily.
- pwdisswordfishc 3y ago"I apologize for the confusion. [Repeats the same wrong thing]"
- darknavi 3y ago> This is slightly wrong. A perfect representation of my git usage then!
- arp242 3y agoI once had a project with a "bin-name" in the gitignore, to exclude the "/bin-name" that "go build" will produce. Then I added a "dir/bin-name/file.go" which of course got excluded. The CI/CD builds failed, but it worked locally, and great confusion ensued. Since then, I've always added that leading "/" and generally try to be as specific as possible in gitignore files. This is a great example where many people providing different answers and comments based on their different knowledge and experience provide value, opposed to just ChatGPT telling you stuff. Simply "correct" is nice, but "correct, complete, and with experience and context" is better.