(2024-2025) CHI Grad Fellowship - Version Control

1. UNDERSTANDING VERSION CONTROL
2. Version control is a system that records changes to a fi le or set of fi les over time so that you can recall speci fi c versions later. VERSION/SOURCE CONTROL
3. WHY?
4. DISTRIBUTED VERSION CONTROL ➋ ➋ CENTRALIZED VERSION CONTROL LOCAL VERSION CONTROL ➊
14. (SOME IMPORTANT GITHUB TERMS)
15. The project. Collection of fi les that comprise the project. Resides in a central (and accessible) location (the repository) A REPOSITORY
16. duplication of an object under revision control (such as a source code fi le, or a document) so that modi fi cations can happen in parallel along both branches. In GitHub main branch is always now called main A BRANCH
17. when developers take a copy of source code from one software package and start independent development on it, creating a distinct piece of software. FORKING
18. Copying all of the fi les from a repository to your local machine (for editing, etc) CLONING
19. submitting the latest changes of the source code to the repository, and making these changes part of the repository (any branch) COMMITTING
20. A request by the person who forked the repository to roll any changes they made back into the main (original) repository. PULL REQUEST
21. WEB VS DESKTOP
22. THE DESKTOP ALWAYS USE
23. 3RD PARTY CLIENTS
24. CODING COLLABORATIVELY
25. COLLABORATIVE WORKFLOW
26. DO WORK LOCALLY USING GITHUB DESKTOP w ➋ CLONE REPOSITORY CREATE A REPOSITORY ➊ ADD COLLABORATORS x COLLABORATORS CLONE REPOSITORY y COLLABORATORS WORK LOCALLY USING GITHUB DESKTOP z
27. FETCH ORIGIN WHEN YOU START WORKING w ➋ COMMIT WHEN YOU STOP WORKING WRITE A GOOD COMMIT MESSAGE ➊ WORK LOCALLY x ALWAYS NEVER EDIT ON THE WEB IN COLLABORATIVE PROJECT y
28. GITHUB AS PM TOOL
29. GITHUB AS WEB HOST
30. THE END