3 ms·
I prefer gitignore since it survives dev container rebuilds. I can set a creation script or volume to restore/persist configs if I must avoid gitignore. Howeve
by 8cvor6j844qw_d6 4mo ago
I prefer gitignore since it survives dev container rebuilds.
I can set a creation script or volume to restore/persist configs if I must avoid gitignore. However, that's an extra script or devcontainer mounts config over a gitignore line.
- mvanbaak 4mo agoIn my opinion (which might not be shared by everyone) this is a you problem. Developers in the team not using decontainers should not have to worry about your environment. ide/local-env stuff should be ignored in the users git setup, everything that the repo creates (build artifacts, environment files etc) should be in the repo.
- arcanemachiner 4mo agoInteresting case. For the global ignore file, couldn't you just bind-mount that into the container?
- paulddraper 4mo ago> However, that's an extra script or devcontainer mounts config over a gitignore line.
- arcanemachiner 4mo agoWell, that's what I get for being an idiot.
- paulddraper 4mo agoThat's an interesting case, where you are crossing operating systems. --- That said, the easier change is still a one/two line bind mount that trying to exhaustively list ignored directories for every IDE or tool under the sun.