Git introduction

• What is git?
• Why use git?
• Basic concepts
  • How it works
  • Standart workflow
  • Explanation of git commands

What is git

• Git is a version control system used to track changes in code during software development.

• It maintains a history of changes, enabling developers to revert to previous versions if necessary.

• 

• GitHub and GitLab are web-based platforms that provide Git repository hosting services, along with additional features for project management and collaboration.
  • There are many comparisons available online, e.g. here
  • You could choose one for yourself / stick to the one of your organization / use both depending on the project
  • An analogy: Dropbox vs Google Drive

• What is git?
• Why use git?
• Basic concepts
  • How it works
  • Standart workflow
  • Explanation of git commands

Why use git

• History tracking:

  • Git maintains a detailed history of changes, allowing you to revert to previous versions of your code if something goes wrong.
    

• Backup: You ensure that your work is backed up

• Reusability: You always have access to your code, making it easier to find and reuse pieces from your previous projects.

• Centralized location of your code:
  • Access your code from anywhere - ideal for workflows where development happens locally but deployment or testing occurs on remote servers.
• Enchanced collaboration:
  • Git enables multiple developers to work on the same project simultaneously without interfering with each other's work.
• Project management:
  • Platforms like GitHub and GitLab offer additional tools for issue tracking, project management, and code reviews, making it easier to manage and collaborate on projects.

• What is git?
• Why use git?
• Basic concepts
  • How it works
  • Standart workflow
  • Explanation of git commands

How it works

• Your repository is a miniature filesystem
• Every commit is a “snapshot” of that system

  • Each commit saves a “snapshot” of all files at that moment. If files haven't changed, Git simply “skips” them.

    

• Your repository is a miniature filesystem
• Every commit is a “snapshot” of that system

  • Each commit saves a “snapshot” of all files at that moment. If files haven't changed, Git simply “skips” them.

    

• What is git?
• Why use git?
• Basic concepts
  • How it works
  • Standart workflow
  • Explanation of git commands

Standard workflow

• Make changes →git add path/to/changed/files → git commit → git push:
  

• Make changes →git add path/to/changed/files → git commit → git push:
  

• Make changes →git add path/to/changed/files → git commit → git push:
  

• Make changes →git add path/to/changed/files → git commit → git push:
  

• Make changes →git add path/to/changed/files → git commit → git push:
  

• Make changes →git add path/to/changed/files → git commit → git push:
  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

Other local repositories need to be updated in order to have the same version as remote repository:

• In another cloned repository: git pull

  

• What is git?
• Why use git?
• Basic concepts
  • How it works
  • Standart workflow
  • Explanation of git commands

Explanation of git commands

• git add:

  • a command you use to add changes into the git staging area. You could think of it as a command to tell the system changes in which files you want to save and upload globally.

    Git staging area is a space where changes are collected and reviewed before they are committed to the repository.

• git commit -m "[a short explanation of changes]":
  • a command to save changed files to the local repository. It records a snapshot of the project’s currently staged changes.
• git push:
  • a command to upload commits from a local computer to a remote git repository.

Supermarket analogy for Git commands

Supermarket analogy for Git commands

Supermarket analogy for Git commands

Supermarket analogy for Git commands

Supermarket analogy for Git commands

Supermarket analogy for Git commands

Supermarket analogy for Git commands

Supermarket analogy for Git commands

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?

What happens when you create multiple commits but don't push them?