3 ms·

I would say that having files in the repo that you have to change but are not allowed to commit is more an issue with the project setup than with jj. The way th

by rob74 2y ago

I would say that having files in the repo that you have to change but are not allowed to commit is more an issue with the project setup than with jj. The way this is usually done (at least where I work) is to have e.g. an `.env.example` file in the repo containing default values which the developer copies to `.env` after cloning the project (usually done by a setup script) - `.env` can then be changed, but is in `.gitignore`, so you don't accidentally commit it.

0cf8612b2e1e 2y ago
There are always edge cases. VSCode still does not let you have a personal configuration file for a project[0] (open since 2016). There are workarounds, but many of them are less good than just manually ignoring the modified file. [0] https://github.com/microsoft/vscode/issues/15909 https://github.com/microsoft/vscode/issues/15909