Git vs GitHub: Version Control and Collaboration Explained

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: Git tracks project history

   0:18

   It records changes to files in a version-controlled project.

   On-screen labels: Tracked files; Saved changes; Project history.

2. 2

   Step 2: Git can work on a computer

   0:30

   A local repository can hold code and its history.

   On-screen labels: Local project; Local history; Developer workflow.

3. 3

   Step 3: GitHub hosts repositories

   0:42

   Teams can store and collaborate on Git projects online.

   On-screen labels: Hosted repository; Team access; Shared project.

4. 4

   Step 4: Collaboration adds review tools

   0:54

   Issues and pull requests help discuss work and proposed changes.

   On-screen labels: Issue discussion; Proposed change; Code review.

5. 5

   Step 5: Ownership still needs checking

   1:06

   Know which business or team controls the hosted project.

   On-screen labels: Repository owner; Authorised access; Handover arrangements.

6. 6

   Step 6: Code history has a defined scope

   1:18

   A repository may not include live databases or uploaded customer files.

   On-screen labels: Tracked project files; Separate live data; Complete backup plan.

See it in a diagram

Read the diagram as text

1. Record the change: Save an identifiable commit
2. Review the update: Inspect the proposed differences
3. Deploy and check: Verify the intended environment

Keep the release reference. Connect the live deployment with the reviewed project version.

Live databases and uploaded files may need separate backup and recovery.

Diagram by Jersey Web. Open full size · Source and further detail (opens in a new tab)

Common questions

Go further