Editing Version control (section)

===Benefits===

====Allows for reverting changes====
A core benefit is the ability to keep history and revert changes, allowing the developer to easily undo changes.  This gives the developer more opportunity to experiment, eliminating the fear of breaking existing code.<ref>{{cite web |url=https://www.claytex.com/tech-blog/the-cost-of-not-using-version-control/ |author=Alessandro Picarelli |title=The cost of not using version control |date=2020-11-17 |access-date=2022-11-18 |quote=In terms of man hours it’s going to cost you 6 to 48 times what it would have cost you using version control, and that’s for rewinding a couple of models for a single developer. |archive-date=2022-11-19 |archive-url=https://web.archive.org/web/20221119184145/https://www.claytex.com/tech-blog/the-cost-of-not-using-version-control/ |url-status=live }}</ref>

====Branching simplifies deployment, maintenance and development====
Branching assists with deployment.  Branching and merging, the production, packaging, and labeling of source code [[Patch (computing)|patches]] and the easy application of patches to code bases, simplifies the maintenance and concurrent development of the multiple code bases associated with the various stages of the deployment process; development, testing, staging, production, etc.<ref>{{cite web |url=https://www.seguetech.com/a-review-of-software-version-control-systems-benefits-and-why-it-matters/ |title=A Review of Software Version Control: Systems, Benefits, and Why it Matters |author=Irma Azarian |date=2023-06-14 |access-date=2022-11-18 |quote=Version control systems allow you to compare files, identify differences, and merge the changes if needed prior to committing any code. Versioning is also a great way to keep track of application builds by being able to identify which version is currently in development, QA, and production. |archive-date=2024-09-26 |archive-url=https://web.archive.org/web/20240926165505/https://www.seguetech.com/a-review-of-software-version-control-systems-benefits-and-why-it-matters/ |url-status=live }}</ref>

====Damage mitigation, accountability and process and design improvement====
There can be damage mitigation, accountability, process and design improvement, and other benefits associated with the record keeping provided by version control, the tracking of who did what, when, why, and how.<ref>{{cite web |url=https://reqtest.com/requirements-blog/what-are-benefits-of-version-control/ |author=ReQtest |title=What Are The Benefits Of Version Control? |date=2020-10-26 |access-date=2022-11-21 |quote=The history of the document provides invaluable information about the author and the date of editing. It also gives on the purpose of the changes made. It will have an impact on the developer that works on the latest version as it will help to solve problems experienced in earlier versions. The ability to identify the author of the document enables the current team to link the documents to specific contributors. This, in turn, enables the current team to uncover patterns that can help with fixing bugs. This will help to improve the overall functionality of the software. |archive-date=2022-11-22 |archive-url=https://web.archive.org/web/20221122023907/https://reqtest.com/requirements-blog/what-are-benefits-of-version-control/ |url-status=live }}</ref>

When bugs arise, knowing what was done when helps with damage mitigation and recovery by assisting in the identification of what problems exist, how long they have existed, and determining problem scope and solutions.<ref>{{cite web |url=https://www.spiceworks.com/tech/devops/articles/what-is-version-control/ |author=Chiradeep BasuMallick |title=What Is Version Control? Meaning, Tools, and Advantages |date=2022-10-06 |access-date=2022-11-18 |quote=Software teams can understand the evolution of a solution by examining prior versions through code reviews. |archive-date=2022-11-19 |archive-url=https://web.archive.org/web/20221119184200/https://www.spiceworks.com/tech/devops/articles/what-is-version-control/ |url-status=live }}</ref> Previous versions can be installed and tested to verify conclusions reached by examination of code and commit messages.<ref>{{cite web |url=https://www.spiceworks.com/tech/devops/articles/what-is-version-control/ |author=Chiradeep BasuMallick |title=What Is Version Control? Meaning, Tools, and Advantages |date=2022-10-06 |access-date=2022-11-18 |quote=If an error is made, developers can go back in time and review prior iterations of the code to remedy the mistake while minimizing disturbance for all team members. |archive-date=2022-11-19 |archive-url=https://web.archive.org/web/20221119184200/https://www.spiceworks.com/tech/devops/articles/what-is-version-control/ |url-status=live }}</ref>

====Simplifies debugging====
Version control can greatly simplify debugging.  The application of a test case to multiple versions can quickly identify the change which introduced a bug.<ref>{{cite web |url=https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Debugging |first1=Scott |last1=Chacon |first2=Ben |last2=Straub |publisher=Apress |edition=Version 2.1.395-2-g27002dd |title=Pro Git |date=2022-10-03 |access-date=2022-11-18 |quote=The git bisect tool is an incredibly helpful debugging tool used to find which specific commit was the first one to introduce a bug or problem by doing an automatic binary search. |archive-date=2024-09-26 |archive-url=https://web.archive.org/web/20240926165502/https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Debugging |url-status=live }}</ref>  The developer need not be familiar with the entire code base and can focus instead on the code that introduced the problem.

====Improves collaboration and communication====
Version control enhances collaboration in multiple ways. Since version control can identify conflicting changes, i.e. incompatible changes made to the same lines of code, there is less need for coordination among developers.<ref>{{cite web |url=https://www.seguetech.com/a-review-of-software-version-control-systems-benefits-and-why-it-matters/ |title=A Review of Software Version Control: Systems, Benefits, and Why it Matters |author=Irma Azarian |date=2023-06-14 |access-date=2022-11-18 |quote=Versioning is a priceless process, especially when you have multiple developers working on a single application, because it allows them to easily share files. Without version control, developers will eventually step on each other’s toes and overwrite code changes that someone else may have completed without even realizing it. Using these systems allows you to check files out for modifications, then, during check-in, if the files have been changed by another user, you will be alerted and allowed to merge them. |archive-date=2024-09-26 |archive-url=https://web.archive.org/web/20240926165505/https://www.seguetech.com/a-review-of-software-version-control-systems-benefits-and-why-it-matters/ |url-status=live }}</ref> 

The packaging of commits, branches, and all the associated commit messages and version labels, improves communication between developers, both in the moment and over time.<ref>{{cite web |url=https://dev.to/jessekphillips/git-is-a-communication-tool--2j9k |author=Jesse Phillips |title=Git is a Communication tool |date=2019-01-21 |orig-date=2018-12-12 |access-date=2022-11-18 |quote=There are continued discussions on using rebase, merge, and/or squash. I want to bring focus to the point of all these choices, communicating. |archive-date=2022-11-19 |archive-url=https://web.archive.org/web/20221119184143/https://dev.to/jessekphillips/git-is-a-communication-tool--2j9k |url-status=live }}</ref>  Better communication, whether instant or deferred, can improve the code review process, the testing process, and other critical aspects of the software development process.