COMP 206 Lecture Notes - Lecture 14: Version Control, Workflow, Git
Document Summary
A tool to help you code in your own directory (revision control system for example) A tool to help (cid:373)a(cid:374)y de(cid:448)elope(cid:396)s sha(cid:396)e (cid:272)ode that"s i(cid:374) a (cid:272)e(cid:374)t(cid:396)al pla(cid:272)e (cid:894)se(cid:396)(cid:448)e(cid:396)(cid:895) (cid:894)su(cid:271)(cid:448)e(cid:396)sio(cid:374) for example) Modern flexible tools that allows the above workflows and many more (git for example) Main concept: repo full history of project, local files are only one snapshot. The version we see actively in our directory may be the latest. We can also go backwards and work on old files (deleted something by mistake) In advanced use, we can keep two branches alive permanently (work on one branch and then merge into master branch for example) We start to make a change to main. c, run a test and get an error. Then we can go back, or "revert main. c" to get the latest version of the file that works previously. Let"s say we shipped software to a customer. We name the branch "release" to keep track.
