Recently, the question arose of replacing the local source code management system with the "keep all versions" file system or tool.
Many answers mostly say that source control systems are not just preserving past versions, even for an individual developer - I think this is correct.
So the question is: what are the reasons for managing source code? And which one is most important?
I'm not interested in source control features, but there are reasons why these features exist.
Here's a starter for ten, but I would like to know if I missed something:
- Saving all versions, especially those that form the shipped product
- Enables commands to edit and prevent (or at least warn) when two collision attempts occur.
- It's easy to see the differences between file versions (covering the two main excuses for the developers: “I didn't change anything” and “my changes shouldn't have done this”)
- Developer Accident Protection (deleting / changing the code inadvertently)
- Protection against hardware problems (bad drives, etc.)
- Allow the development of several different base codes while minimizing duplication of immutable files.
- Keeping a record of who changed something and why
- Enabling experimental changes without breaking the core code base
Why are you using source control?
source
share