This document provides an introduction to version control and Git. It discusses the basics of version control systems including backups, history tracking, experimentation, and collaboration. It then covers getting started with Git, including basic commands like init, add, commit, push, and pull. More advanced Git topics are also introduced like logging, tagging, branching, merging, rebasing, and resolving conflicts. The document concludes with an overview of Git-related files and productivity tools that integrate with Git.

1. Introduction to
Version Control

2. Agenda
◎ Overview of Version Control
◎ Getting started with Git
◎ Basic Git daily commands
◎ Advanced Git commands
◎ Git-related files
◎ Resolve conflicts
◎ Version Control and DevOps
◎ Productivity tools
2

3. 1.
Overview of Version
Control
3

4. Version Control System
◎ A software that records changes made to a set of files
over time, allowing specific history to be recalled and
restored as necessary.
4

5. 5
VCS example

6. 6
VCS example

7. 7
VCS example

8. 1. 1
Use cases
8

9. Backups
◎ Accidentally delete the file without backups.
9

10. Backups
◎ Accidentally delete the file without backups.
◎ Version Control makes backups, we can recover.
10

11. Backups (alternatives)
◎ Manually backup files with timestamp
◎ Online file hosting websites
11

12. Backups (alternatives)
12

13. History and Changes
◎ No clues what / why changes has been made.
13

14. History and Changes
◎ No clues what / why changes has been made.
◎ Version Control keeps a history line-by-line with a
description.
14

15. History and Changes
15

16. Experiment
◎ In case of running some experiment, you need to
create a new project since it will affect the existing
main project.
16

17. Experiment
◎ In case of running some experiment, you need to
create a new project since it will affect the existing
main project.
◎ Version Control allows us to create experiment
sections.
17

18. Collaboration
◎ Unable to collaborate since the file belongs to one
person at a time.
18

19. Collaboration
◎ Unable to collaborate since the file belongs to one
person at a time.
◎ Version Controls allows us to work at the same file, at
the same time.
19

20. Version Control offers ...
◎ Backups
◎ History records
◎ Changes
◎ Experiment
◎ Collaboration
20

21. 1. 2
Types of Version
Control System
21

22. Centralized vs Distributed
22

23. Centralized VCS Distributed VCS
Speed Slow Fast
Offline mode
No Yes
23
Centralized vs Distributed

24. 2.
Getting started with
Git
24

25. Git gives you ...
◎ Distributed version control system
◎ Speed
◎ Free and Open-source
◎ Staging area
25

26. How Git works
26

27. Online shopping analogy
27
Add stuffs to cart Order
confirmation

28. Git hosting providers
◎ GitHub
◎ GitLab
◎ Bitbucket
◎ Azure DevOps
28

29. 3.
Basic Git daily
commands
29

30. Initializing
git init
30
Create an empty Git repository.

31. Initializing
git init
31

32. Staging
git add <file>
32
Indicate which files and their states are to be included in
the next commit.

33. Staging
git add <file>
33

34. Status
git status
34
See the status of the repository.

35. Committing
git commit -m “<commit-message>”
35
Place copies (snapshots) of working directory back into the
repository as a new version.

36. Committing
git commit -m “<commit-message>”
36

37. Syncing
git remote [add | set-url] <remote> <url>
37
Sync the local repository to the remote repository.

38. Syncing
git remote [add | set-url] <remote> <url>
38

39. Pushing
git push -u <remote> <branch>
39
Push changes up to a branch of a remote repository.

40. Pushing
git push -u <remote> <branch>
40

41. Pulling
git pull <remote> <branch>
41
Pull changes from (a branch of) a remote repository.

42. Pulling
git pull <remote> <branch>
42

43. Cloning
git clone <remote-url>
43
Get your own local copy of an existing repository.

44. 44

45. 4.
Advanced Git
commands
45

46. 4. 1
View history
46

47. Logging
git log <object>
47
Review the history of committed snapshots.

48. Difference
git diff <path> <path>
48
Explore differences between the workspace, the staging
area, and commits.

49. Difference
git diff <path> <path>
49

50. Tagging
git tag <tag-name>
50
Another way to track the history of a repository via certain
milestone commits.

51. 4. 2
Recovery
51

52. Checkout
git checkout “<commit>”
52
Explore the state associated with a specific commit.

53. Checkout
git checkout “<commit>”
53

54. Reset
git reset [--soft | --hard] <commit>
54
Return to a previous state, effectively erasing subsequent
commits.

55. Reset
git reset [--soft | --hard] <commit>
55

56. Revert
git revert <commit>
56
Generate a new commit that reverses the changes
introduced by a commit.

57. 4. 3
Branching
57

58. Branching
◎ Isolating environment from main development line
without impact.
◎ For example, developing new features without
affecting production-quality code.
◎ Encouraging experiment purposes.
58

59. Branching example
59

60. Branching
git branch <branch-name>
60
Take edits in the project in a new direction to allow for
modifications that will not affect the main branch.

61. Merging
git merge <branch-name>
61
Incorporate changes in a branch into another branch
(typically master).

62. Merging
62

63. Rebasing
git rebase <branch-name>
63
Apply all changes of a branch on top of another branch by
creating a new commit.

64. Rebasing
64

65. Merging vs Rebasing
Safety vs
Traceability
65

66. Stashing
git stash [pop | apply | list | clear]
66
Record the current state of the working directory and the
index, but want to go back to a clean working directory.

67. 5.
Git-related files
67

68. .gitignore
68
Ignore files that we don't want to get staged and
committed.

69. .gitconfig
69
Git configuration file contains a number of variables that
affect the Git commands' behavior.

70. 6.
Resolving conflicts
70

71. 7.
Git and DevOps
71

73. 73

74. 8.
Productivity tools
74

75. Text editors / IDE
75

76. Git Kraken
76

77. gitignore.io
77

78. Thanks!
Contact us:
Raksit Mantanacharu
raksit.mantanacharu1@exxonmobil.com
78