Mastering Version Control with Git & GitHub

Version Control and
Workﬂow 16-10-2025

Who am I ?
• Data Scientist
• Research Master's Student, Faculty
of Science of Sfax (FSS)

Plan
Part 1 — Theoretical Foundations
Part 2 — Practical Session

A
1

A
B
Modiﬁcation
2

A
B
Saved
3

A
B
How to keep the 2 versions?
4

Bad solutions
5

Problematic
How to manage ﬁles versions
effectively?
6

Version Control
• System that tracks every change made to your
codebase.
• Allows developers to revert, compare, and
collaborate safely.
7

Why Every Developer Needs
It?
Keeps a complete history of your project
8

Why Every Developer Needs
It?
Allows experimentation without fear of breaking the main code
9

Beneﬁts for Teams and Open
Source
• Teams can work in parallel on different features.
• Merge and review changes without overwriting others.
10

Beneﬁts for Teams and Open
Source
• Enables open-source collaboration
• Supports automation and DevOps pipelines.
11

DevOps
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to
shorten the systems development life cycle and provide continuous delivery with high software
12

Git
• Git = Distributed Version Control System (DVCS)
• Manages snapshots of the project
• Each developer has a full local history
13

Git architecture
• Working Directory:
• Staging Area (Index):
• Local Repository:
• Remote Repository:
Where you make changes
Prepares changes for commit
Stores conﬁrmed commits
Shared version on GitHub
14

Key Concepts• Commit
• Branch
• Merge
15
Concept Description
Repository Project folder tracked by Git
Commit Snapshot of your code at a specific time
Branch Independent line of development
Merge Combine changes between branches
Remote A hosted version of your repo (e.g., GitHub)

Github
• Web-based hosting for Git repositories
that provides version control and
collaboration features.
“Git tracks code. GitHub connects people.”
16

Core Features
• Repositories: Store and version your code
• Forks: Copy someone’s repo to make your own
changes
• Pull Requests (PRs): Propose changes to a
project
17

Objective of the workshop
• Push a ﬁle or a project to a distant repository
• Fork and clone an existing project
18

Steps:
Install Git
https://git-scm.com/downloads
19

Steps:
Create a GitHub account and try to create an
empty project
20

Steps:
• Create a folder named “workshop”
• Under it, create a text ﬁle “test.txt”
21

Steps:
Open cmd/power_shell/git_bash(CLI) under
the folder “workshop”
22

Steps:
Initialize a git repository:
git init
23

Steps:
Providing information about the current state
of your repository:
git status
24

Steps:
Staging your ﬁles to make them ready to
commit:
git add .
25

Steps:
Author authentication:
git conﬁg --global user.email "you@example.com"
git conﬁg --global user.name "Your Name"
26

Steps:
Commit your ﬁles with a comment:
git commit -m "ﬁrst commit"
27

Steps:
Visualize your commits:
• ID of a commit
• A comment
• Author information (email-name...)
• Creation date 28

Steps:
Visualize your commits:
git log
29

Steps:
Create a new branch to work on:
git branch "new_branch_name"
30

Steps:
Reallocate to the new branch:
git checkout "new_branch_name"
31

Steps:
Create a text ﬁle (feature.txt) in your repo and
make some modiﬁcations on it
32

Steps:
We repeat same process:
git add .
git commit -m "add feature"
33

Steps:
Return to the principal branch
git checkout master
34

Steps:
Merge the new branch to the master:
git merge "new_branch-name"
35

Steps:
Remote to the distant repository:
git remote add origin "link"
36

Steps:
Push your ﬁles to the distant repo:
git push -u origin master
37

Fork and clone
Fork repository then clone it using:
git clone "link"
38

Next Step
• Explore more Git-GitHub
• Try other web-based hosting for Git
repositories: GitLab, DagsHub...
39

Thank you for
your attention
Get in touch

Mastering Version Control with Git & GitHub

More Related Content

Similar to Mastering Version Control with Git & GitHub

Recently uploaded

Mastering Version Control with Git & GitHub