Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Version control
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====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.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)