Usually, you can. But occasionally you get mildly defective tools that require some directory to exist, even though it's empty. It's easier to add a gitkeep than fix them.
replyThis used to happen a lot. But I don't think that many modern builders require existing directory these days.
replyYour point is valid though. It would be much preferable to include build/ in your root .gitignore so that the directory is never tracked.
Because you might not have a build script?
replyThen how is anything ending up in the build directory?
replyThen why do you need a build directory?
replyqemu: mkdir build; cd build; ../configure, some projects are like that
replyWhy can’t the configure script do this?
replyYou can. But this makes intent clear. If you clone a git repo and see build/ with only a gitkeep, you are safe to bet your life savings on that being the compiled assets dir.
replyThere may be other directories. I think it's useful to be able to see the entire directory structure of a repo when you check it out, and not just after running some scripts.
reply