Menu
So what should not be put in the version control and why? Build artifacts. This should be clear — build artifacts just do not belong to the version control. Having them there would mean that every time source code changes, all related build artifacts would also be updated.
Source control (or version control) is the practice of tracking and managing changes to code. Source control management (SCM) systems provide a running history of code development and help to resolve conflicts when merging contributions from multiple sources.
Some benefits of source control are: It allows multiple developers to work on the same codebase. Developers can commit and merge code without conflicts. Developers can edit shared code without unknowingly overwriting each other's work.
Anything that is generated. Binary, bytecode, code/documents generated from XML.
From my commenters, exclude:
But include:
FWIW, at my work for a very large project, we have the following under ClearCase:
We do not have built modules for our software. A complete binary is distributed every couple weeks with the latest updates.
OS specific files, generated by their file browsers such as
Thumbs.db and .DS_Store
Some other Visual Studio typical files/folders are
*.cachefile
*.backup
_UpgradeReport_Files
My tortoise global ignore pattern for example looks like this
bin obj *.suo *.user *.cachefile *.backup _UpgradeReport_Files
files that get built should not be checked in
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