#Tortoisehg global .hgignore how to#
#Tortoisehg global .hgignore code#
#Tortoisehg global .hgignore windows#

>Keeping untracked files lying around not gitignored is a recipe for one day committing one by mistake, or conversely, that some of them are source files you've forgot to commit. Or it is a file that stores your notes or experiments that don't necessarily belong in a branch, do not want to include in your next commit, but you also don't want to be invisible to '.gitignore' aware tools - and increasingly many modern tools are (vscode, ripgrep, emacs's projectile to name a few). > If it's untracked either it needs to be ignored or it's a new source file to add to the index. Why do you not want to see any untracked files? What harm does it cause? What is the problem that you are trying to solve? I don't want to see any untracked temporary files. It doesn't even matter if many users who work on the codebase day to day actually use emacs or a highly customized IntelliJ setup or whatever - the vscode settings specifically enable the driveby coder to get a working environment fast, and that helps enable the power users to not be bothered by feature requests that could be pull requests.

#Tortoisehg global .hgignore code#

With the right set of extension recommendations and default code settings, a VS code user can automatically be prompted to get the right test executors, linters, prettifiers, and so on so that they get instant feedback on their changes. Npm ci | dotnet restore | terraform init | go get | If I want to encourage small, one-off contributions, I want to support a user workflow that's as close as possible to: vscode/extensions.json file just specifies extension 'recommendations', and I find, really accelerates developers becoming productive in a project. I've rarely been in an environment where that is the case for everyone.Ī.

#Tortoisehg global .hgignore how to#

Having maven and editorconfig instruct IntelliJ on how to make a workspace consistent results in less config file churn and avoids people accidentally checking in the compiler settings on their computer, database configurations (with passwords), run configurations (with passwords) and similar.Ĭhecking in IDE files can be done, just that the developers all need to be diligent in checking what they check in. I am a strong proponent now of not checking in files that are IDE specific unless the developers are all completely aware of what files do what and the associated churn that a file may have through normal use. Not a problem for the dev who checked it in, but a problem for everyone else. When someone checked them in again and you hadn't updated this particular plugin, the newer file format caused it to crash.

Each time you went to switch to a different branch, you got the workspace configuration of the last person to commit that file.Īnother spot of problems was the plugin specific files (that inevitably also got checked in).

#Tortoisehg global .hgignore windows#

This resulted in them checking in the file that had windows and cursor positions checked in too.

idea directory and all the files for a project.