Menu
I looked this up and almost every answer linked to a gitignore repository or a website. However, upon inspection I've found that it doesn't ignore files that I'm having problems with.
The files in question are:
Which of these files are safe to ignore? Which are not? And for what reasons?
Thanks!
462
Ignored files are usually build artifacts and machine generated files that can be derived from your repository source or should otherwise not be committed. Some common examples are: dependency caches, such as the contents of /node_modules or /packages. compiled code, such as .o , .
Files that don't belong to the project Files like . DS_Store (for Mac OS), Thumds. db (for Windows), . vscode (for code editors) have nothing to do with your project.
Use a global gitignore file A global . gitignore file helps ensure that Git doesn't commits certain file types, such as compiled binaries, in any local repo.
gitignore is a file in your git root directory. Add the name patterns for the files that you want to ignore, and the files will be ignored automatically. It is the directory where you used git init .
This totally depends on what you want to track in source control. I'd say typically files prefixed with a "dot" are safe to ignore/exclude from source control.
Some of your files contain the word "user" which would imply they're user-specific files and shouldn't be committed; otherwise, each user would likely have diff changes for these files each time they worked on the project, which probably isn't what you want. I see one file has "suo" which is a Visual Studio convention for "solution user options", and the same logic applies there too.
I'd assume you want to track PROJECTNAME.rds in source control, and you wouldn't want to track the others.
107
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
