Git is a version control system that allows users to work collaboratively by keeping track of changes to files. It creates a hidden .git directory that stores changes locally. Users commit changes to save them locally, then sync with a remote server to share changes. This allows multiple users to edit files simultaneously and merge their work together.
Git is a version control system that stores changes to files in a special hidden directory called .git. It allows users to commit changes locally, then sync them to a remote server for backup and collaboration. The basic git workflow involves editing files, committing changes locally with a message, then syncing to save to the remote server. This allows multiple people to work together by sharing changes through a shared remote server.
This document provides an overview of basic Git commands and workflows. It discusses what Git is, why it's useful for version control and collaboration, and how to install, set up, initialize and commit code to a Git repository. It also covers branching, merging, tagging, forking repositories, and resolving merge conflicts. The document recommends setting up a remote repository on a hosting service like GitHub and pushing and pulling changes between local and remote repositories. It challenges readers to participate in Hacktoberfest and suggests some GUI tools for Git.
This document provides an overview of using Git and GitHub for version control and collaboration. It begins with an agenda and explains why version control systems are useful, particularly for teams. It then defines Git and GitHub, describing how Git stores versions as commit objects in a repository and how GitHub hosts Git repositories. The document outlines basic Git commands like init, add, commit, status and push/pull. It provides guidance on setting up Git and GitHub accounts and using GitHub features like branches, commits, and forks for collaboration.
This document provides an overview of Git and GitHub for version control. It discusses why version control is useful, both for individuals and teams working on code. It then introduces Git and GitHub, covering basic Git commands, fundamentals of using GitHub, and how GitHub can be used for project implementation and collaboration. The document includes an agenda, explanations of key concepts, and links to GitHub documentation for setting up accounts and learning more commands.
Git is version control software that allows multiple users to work on projects together without overwriting each other's changes. It saves snapshots of changes and allows easy merging of revisions. The document then provides instructions on installing and configuring Git, initializing and cloning repositories, adding and committing changes, viewing history and branches, merging branches, and pushing and pulling changes between local and remote repositories hosted on services like GitHub. It also introduces commands like git fetch, git revert, git rebase, and git grep.
The document provides an introduction to version control systems and Git. It discusses why version control is useful, both for individual and team projects. It describes some key version control systems like CVS, Subversion, Mercurial and Git. It then focuses on explaining Git, including how to download, install and get started using it for version control of projects. It covers basic Git commands and workflows for making commits, working with remote repositories and keeping changes synchronized between local and remote versions.
The document provides an overview of version control systems and focuses on Git. It discusses why version control is useful, both for individual and team projects. It describes key features of Git like distributed repositories and branching. The document then provides step-by-step instructions for downloading, installing, and using basic Git commands like init, add, commit, clone, pull and push. It emphasizes committing changes frequently and keeping repositories up-to-date.
The document provides an overview of version control systems and focuses on Git. It discusses why version control is useful, both for individual and team projects. It explains that Git is a distributed version control system that is becoming more popular than centralized systems like CVS and Subversion. The document provides instructions for downloading, installing, and getting started with basic Git commands and workflows for creating and working with repositories.
Git is a version control system that stores changes to files in a special hidden directory called .git. It allows users to commit changes locally, then sync them to a remote server for backup and collaboration. The basic git workflow involves editing files, committing changes locally with a message, then syncing to save to the remote server. This allows multiple people to work together by sharing changes through a shared remote server.
This document provides an overview of basic Git commands and workflows. It discusses what Git is, why it's useful for version control and collaboration, and how to install, set up, initialize and commit code to a Git repository. It also covers branching, merging, tagging, forking repositories, and resolving merge conflicts. The document recommends setting up a remote repository on a hosting service like GitHub and pushing and pulling changes between local and remote repositories. It challenges readers to participate in Hacktoberfest and suggests some GUI tools for Git.
This document provides an overview of using Git and GitHub for version control and collaboration. It begins with an agenda and explains why version control systems are useful, particularly for teams. It then defines Git and GitHub, describing how Git stores versions as commit objects in a repository and how GitHub hosts Git repositories. The document outlines basic Git commands like init, add, commit, status and push/pull. It provides guidance on setting up Git and GitHub accounts and using GitHub features like branches, commits, and forks for collaboration.
This document provides an overview of Git and GitHub for version control. It discusses why version control is useful, both for individuals and teams working on code. It then introduces Git and GitHub, covering basic Git commands, fundamentals of using GitHub, and how GitHub can be used for project implementation and collaboration. The document includes an agenda, explanations of key concepts, and links to GitHub documentation for setting up accounts and learning more commands.
Git is version control software that allows multiple users to work on projects together without overwriting each other's changes. It saves snapshots of changes and allows easy merging of revisions. The document then provides instructions on installing and configuring Git, initializing and cloning repositories, adding and committing changes, viewing history and branches, merging branches, and pushing and pulling changes between local and remote repositories hosted on services like GitHub. It also introduces commands like git fetch, git revert, git rebase, and git grep.
The document provides an introduction to version control systems and Git. It discusses why version control is useful, both for individual and team projects. It describes some key version control systems like CVS, Subversion, Mercurial and Git. It then focuses on explaining Git, including how to download, install and get started using it for version control of projects. It covers basic Git commands and workflows for making commits, working with remote repositories and keeping changes synchronized between local and remote versions.
The document provides an overview of version control systems and focuses on Git. It discusses why version control is useful, both for individual and team projects. It describes key features of Git like distributed repositories and branching. The document then provides step-by-step instructions for downloading, installing, and using basic Git commands like init, add, commit, clone, pull and push. It emphasizes committing changes frequently and keeping repositories up-to-date.
The document provides an overview of version control systems and focuses on Git. It discusses why version control is useful, both for individual and team projects. It explains that Git is a distributed version control system that is becoming more popular than centralized systems like CVS and Subversion. The document provides instructions for downloading, installing, and getting started with basic Git commands and workflows for creating and working with repositories.
BLUG 2012 Version Control for Notes DevelopersMartin Jinoch
This document discusses using version control for Notes developers. It recommends using a version control system like Git or Subversion to track changes made during development. It describes how to set up Git for use with Domino Designer using the EGit plugin. It also discusses using a branching model like git-flow to manage features, releases, and bug fixes. Finally, it provides resources for learning more about version control systems and tools that can be integrated into the development workflow.
Git is a version control system that records changes to files over time. It was created by Linus Torvalds for development of the Linux kernel and is now widely used by software developers. Some key points about Git include that it is distributed, allows non-linear development through branches, and can handle large projects with millions of lines of code and thousands of commits from hundreds or thousands of contributors. The basic Git workflow involves initializing a repository, making changes, staging files, committing changes to the local repository, and pushing commits to a remote repository. Common commands include git init, git add, git commit, git push, git pull, and git log.
Git is a distributed version control system that allows developers to work simultaneously, prevents overwriting each other's changes, and maintains a history of every version. It uses a local repository that can be synced to remote repositories. The basic workflow involves modifying files in the working directory, staging changes, and committing to the local repository. Common commands are git init, git clone, git add, git commit, and git push. Branches allow isolated development and git merge combines changes.
In one of our weekly training, we’ve talked about Git. Here is a quick overview of the main concepts, basic commands and branching strategy, how to work with Git, how to contribute to an OSS project, …
This document provides an overview of using Git for version control. It begins with cloning a project from the internet and creating a local Git project. It then covers committing changes, pushing commits to a remote repository on GitHub, and pulling updates. The document also discusses branching, forking projects on GitHub, and sending pull requests to contribute changes back to the original project.
This document provides an overview of Git, a distributed version control system. It discusses Git's history, getting started, the three trees that make up a Git repository (HEAD, index, working directory), centralized vs distributed version control systems, basic workflows, branching and merging, and keeping workflows simple. Key points include that Git was created by Linus Torvalds for Linux kernel development, supports concurrent work and merging changes from multiple developers, and uses a commit graph and branching model to manage project versions.
GIT is a free and open source distributed version control system that allows users to work locally and share code remotely. It allows creating branches to work on features separately, and merging them together easily. The basic workflow involves initializing a local repository, making commits by adding and saving files, and pushing changes to remote repositories like GitHub to share code. Users can then clone repositories from GitHub to contribute code through pull requests.
This document provides an overview of Git and how to use it. It discusses version control systems and how distributed version control systems like Git work. It explains how Git was created by Linus Torvalds for Linux kernel development and why it gained popularity due to its speed and efficiency. The document then covers Git basics like setup, commits, branches and workflows. It also introduces tools for using Git in Eclipse and GitLab for code hosting and collaboration.
A Beginner's Guide to Git and GitHub, CLI version.
What is Git?
What is Github
Basic commands
Difference between Central and Distributed Version Controlling System
Git 101 - An introduction to Version Control using Git John Tighe
This document provides an introduction to version control using Git. It explains that Git allows for non-linear development through branching, which allows developers to work independently on different parts of a project. The document walks through setting up a local Git repository and making commits on different branches. It demonstrates how to merge branches together and delete branches that are no longer needed.
Git is a distributed version control system that allows developers to work collaboratively. It uses a local repository that is regularly synced with a remote repository. The document discusses Git basics like initialization, tracking files, commits, branches and common workflows like Gitflow. Specific commands covered are add, commit, checkout, rebase, stash, cherry-pick and how to undo faulty pushes. Key advantages of Git over SVN are also highlighted.
Git is a distributed version control system that was created by Linus Torvalds in 2005 to manage changes to files over time. It works by tracking changes made to files in a git repository and allowing users to commit snapshots of changes. The key git commands are git init to create a new repository, git clone to copy an existing one, git add to stage changes, git commit to commit staged changes, and git log to view the commit history. GitHub is a popular web-based hosting service for git repositories.
This document provides an overview of Git GUI tools, specifically reviewing GitHub Desktop and Sourcetree. It describes the basic features of each tool, such as cloning repositories, viewing commit histories, creating and switching branches, staging and committing changes. While GitHub Desktop focuses more on simplification and hosting on GitHub, Sourcetree offers more advanced features that better match terminal commands but could overwhelm beginners. Both tools have advantages and the document recommends trying multiple GUI tools as well as using a combination of GUI and command line.
Git Workshop
Daniel Laufer on September 15, 2021
Get an overview of Git and GitHub including what they are, their purpose, how they work, how they interact with each other, and much more.
You will learn about essential Git commands and concepts and go through several short demos using them.
Additionally, you will learn how to collaborate with others on a project using Git and GitHub, and learn how to contribute to open-source projects.
All of this combined will allow students to learn an essential skill that will follow them through their career in tech!
Git is a version control system for tracking changes to files, while GitLab is a web-based Git repository manager with additional features. The document discusses Git and GitLab workflows including continuous integration, continuous delivery, and continuous deployment using GitLab. It also provides examples of common Git commands like add, commit, push, pull, branch, tag, and undo.
This document provides an overview of version control systems and instructions for downloading, installing, and using the distributed version control system Git. It explains the basics of Git including configuring user information, choosing an editor, interacting with remote repositories, and common commands for viewing changes, staging files, committing changes, and viewing the commit history. Typical workflows and some helpful formatting options for the git log command are also demonstrated.
Beginner Workshop for Student Developers - Tratech-presentation.pdfGDSCKNUST
Version control allows tracking changes to code over time and collaboration between developers. Git is a version control tool while GitHub is a platform that integrates with Git. This document discusses setting up Git locally and linking a Git repository to a GitHub account for collaboration and backup of code. Key steps include installing Git, configuring user settings, initializing a Git repository for a project, adding and committing files, and pushing the local repository to GitHub to sync changes and make the code accessible to others.
This document provides an overview of version control using GIT and common GIT commands. It discusses initializing a new GIT repository with "git init" or cloning an existing one with "git clone". It emphasizes not directly modifying the master branch and instead working on feature branches. The steps covered include creating and checking out branches, deleting branches once merged, pushing branches to remote repositories, and merging branches back into master.
Git is the free and open-source distributed version control system that's responsible for everything GitHub-related that happens locally on your computer. This cheat sheet features the most important and commonly
used Git commands for easy reference.
Securing BGP: Operational Strategies and Best Practices for Network Defenders...APNIC
Md. Zobair Khan,
Network Analyst and Technical Trainer at APNIC, presented 'Securing BGP: Operational Strategies and Best Practices for Network Defenders' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
More Related Content
Similar to Lesson 0.5 Introduction to Git (1).pptx
BLUG 2012 Version Control for Notes DevelopersMartin Jinoch
This document discusses using version control for Notes developers. It recommends using a version control system like Git or Subversion to track changes made during development. It describes how to set up Git for use with Domino Designer using the EGit plugin. It also discusses using a branching model like git-flow to manage features, releases, and bug fixes. Finally, it provides resources for learning more about version control systems and tools that can be integrated into the development workflow.
Git is a version control system that records changes to files over time. It was created by Linus Torvalds for development of the Linux kernel and is now widely used by software developers. Some key points about Git include that it is distributed, allows non-linear development through branches, and can handle large projects with millions of lines of code and thousands of commits from hundreds or thousands of contributors. The basic Git workflow involves initializing a repository, making changes, staging files, committing changes to the local repository, and pushing commits to a remote repository. Common commands include git init, git add, git commit, git push, git pull, and git log.
Git is a distributed version control system that allows developers to work simultaneously, prevents overwriting each other's changes, and maintains a history of every version. It uses a local repository that can be synced to remote repositories. The basic workflow involves modifying files in the working directory, staging changes, and committing to the local repository. Common commands are git init, git clone, git add, git commit, and git push. Branches allow isolated development and git merge combines changes.
In one of our weekly training, we’ve talked about Git. Here is a quick overview of the main concepts, basic commands and branching strategy, how to work with Git, how to contribute to an OSS project, …
This document provides an overview of using Git for version control. It begins with cloning a project from the internet and creating a local Git project. It then covers committing changes, pushing commits to a remote repository on GitHub, and pulling updates. The document also discusses branching, forking projects on GitHub, and sending pull requests to contribute changes back to the original project.
This document provides an overview of Git, a distributed version control system. It discusses Git's history, getting started, the three trees that make up a Git repository (HEAD, index, working directory), centralized vs distributed version control systems, basic workflows, branching and merging, and keeping workflows simple. Key points include that Git was created by Linus Torvalds for Linux kernel development, supports concurrent work and merging changes from multiple developers, and uses a commit graph and branching model to manage project versions.
GIT is a free and open source distributed version control system that allows users to work locally and share code remotely. It allows creating branches to work on features separately, and merging them together easily. The basic workflow involves initializing a local repository, making commits by adding and saving files, and pushing changes to remote repositories like GitHub to share code. Users can then clone repositories from GitHub to contribute code through pull requests.
This document provides an overview of Git and how to use it. It discusses version control systems and how distributed version control systems like Git work. It explains how Git was created by Linus Torvalds for Linux kernel development and why it gained popularity due to its speed and efficiency. The document then covers Git basics like setup, commits, branches and workflows. It also introduces tools for using Git in Eclipse and GitLab for code hosting and collaboration.
A Beginner's Guide to Git and GitHub, CLI version.
What is Git?
What is Github
Basic commands
Difference between Central and Distributed Version Controlling System
Git 101 - An introduction to Version Control using Git John Tighe
This document provides an introduction to version control using Git. It explains that Git allows for non-linear development through branching, which allows developers to work independently on different parts of a project. The document walks through setting up a local Git repository and making commits on different branches. It demonstrates how to merge branches together and delete branches that are no longer needed.
Git is a distributed version control system that allows developers to work collaboratively. It uses a local repository that is regularly synced with a remote repository. The document discusses Git basics like initialization, tracking files, commits, branches and common workflows like Gitflow. Specific commands covered are add, commit, checkout, rebase, stash, cherry-pick and how to undo faulty pushes. Key advantages of Git over SVN are also highlighted.
Git is a distributed version control system that was created by Linus Torvalds in 2005 to manage changes to files over time. It works by tracking changes made to files in a git repository and allowing users to commit snapshots of changes. The key git commands are git init to create a new repository, git clone to copy an existing one, git add to stage changes, git commit to commit staged changes, and git log to view the commit history. GitHub is a popular web-based hosting service for git repositories.
This document provides an overview of Git GUI tools, specifically reviewing GitHub Desktop and Sourcetree. It describes the basic features of each tool, such as cloning repositories, viewing commit histories, creating and switching branches, staging and committing changes. While GitHub Desktop focuses more on simplification and hosting on GitHub, Sourcetree offers more advanced features that better match terminal commands but could overwhelm beginners. Both tools have advantages and the document recommends trying multiple GUI tools as well as using a combination of GUI and command line.
Git Workshop
Daniel Laufer on September 15, 2021
Get an overview of Git and GitHub including what they are, their purpose, how they work, how they interact with each other, and much more.
You will learn about essential Git commands and concepts and go through several short demos using them.
Additionally, you will learn how to collaborate with others on a project using Git and GitHub, and learn how to contribute to open-source projects.
All of this combined will allow students to learn an essential skill that will follow them through their career in tech!
Git is a version control system for tracking changes to files, while GitLab is a web-based Git repository manager with additional features. The document discusses Git and GitLab workflows including continuous integration, continuous delivery, and continuous deployment using GitLab. It also provides examples of common Git commands like add, commit, push, pull, branch, tag, and undo.
This document provides an overview of version control systems and instructions for downloading, installing, and using the distributed version control system Git. It explains the basics of Git including configuring user information, choosing an editor, interacting with remote repositories, and common commands for viewing changes, staging files, committing changes, and viewing the commit history. Typical workflows and some helpful formatting options for the git log command are also demonstrated.
Beginner Workshop for Student Developers - Tratech-presentation.pdfGDSCKNUST
Version control allows tracking changes to code over time and collaboration between developers. Git is a version control tool while GitHub is a platform that integrates with Git. This document discusses setting up Git locally and linking a Git repository to a GitHub account for collaboration and backup of code. Key steps include installing Git, configuring user settings, initializing a Git repository for a project, adding and committing files, and pushing the local repository to GitHub to sync changes and make the code accessible to others.
This document provides an overview of version control using GIT and common GIT commands. It discusses initializing a new GIT repository with "git init" or cloning an existing one with "git clone". It emphasizes not directly modifying the master branch and instead working on feature branches. The steps covered include creating and checking out branches, deleting branches once merged, pushing branches to remote repositories, and merging branches back into master.
Git is the free and open-source distributed version control system that's responsible for everything GitHub-related that happens locally on your computer. This cheat sheet features the most important and commonly
used Git commands for easy reference.
Similar to Lesson 0.5 Introduction to Git (1).pptx (20)
Securing BGP: Operational Strategies and Best Practices for Network Defenders...APNIC
Md. Zobair Khan,
Network Analyst and Technical Trainer at APNIC, presented 'Securing BGP: Operational Strategies and Best Practices for Network Defenders' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
Honeypots Unveiled: Proactive Defense Tactics for Cyber Security, Phoenix Sum...APNIC
Adli Wahid, Senior Internet Security Specialist at APNIC, delivered a presentation titled 'Honeypots Unveiled: Proactive Defense Tactics for Cyber Security' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
2. Learning Objectives
• At the end of this lesson you should be able
to explain:
– how git creates a mini-filesystem in your directory
– what commit, push, pull, and sync do
– the elements of the basic git workflow
– how git allows you to work across multiple
computers
– how git allows you and a partner to work together
2
3. Git is a distributed version-control
system
• You keep your files in a repository on your local
machine.
• You synchronize your repository with a repository
on a server.
• If you move from one machine to another, you
can pick up the changes by synchronizing with
the server.
• If your partner uploads some changes to your
files, you can pick those up by synchronizing with
the server.
3
4. Git is a distributed version-control
system
• Terminology: In git-speak, a “version” is called
a “commit.”
• Git keeps track of the history of your commits,
so you can go back and look at earlier
versions, or just give up on the current version
and go back some earlier version.
4
5. A simple model of git
• Most git documentation gets into details very
quickly.
• Here’s a very simple model of what’s going on
in git.
5
6. Your files
my-project docs manual.docx
user_docs.docx
src
main.rkt
module1.rkt
module2.rkt
module3.rkt
Here are your files, sitting
in a directory called my-
project
6
7. Your files in your git repository
my-project docs manual.docx
user_docs.docx
src
main.rkt
module1.rkt
module2.rkt
module3.rkt
.git
When you have a git repository, you have
an additional directory called .git, which
points at a mini-filesystem.
This file system keeps all your data, plus the
bells and whistles that git needs to do its
job.
All this sits on your local machine.
7
8. The git client
.git
This mini-filesystem is highly optimized and
very complicated. Don’t try to read it
directly.
The job of the git client (either Github for
Windows, Github for Mac, or a suite of
command-line utilities) is to manage this for
you.
8
9. Your workflow (part 1)
• You edit your local files directly.
– You can edit, add files, delete files, etc., using
whatever tools you like.
– This doesn’t change the mini-filesystem, so now
your mini-fs is behind.
9
10. A Commit
.git
commit
When you do a “commit”, you
record all your local changes into
the mini-fs.
The mini-fs is “append-only”.
Nothing is ever over-written
there, so everything you ever
commit can be recovered.
10
11. Synchronizing with the server (1)
.git push
At the end of each work session, you need
to save your changes on the server. This is
called a “push”.
Now all your data is backed up.
• You can retrieve it, on your machine or
some other machine.
• We can retrieve it (that’s how we collect
homework)
your local machine
a server, somewhere on the
internet, eg. github.com
11
12. Synchronizing with the server (2)
.git pull
To retrieve your data from the server, you
do a “pull”. A “pull” takes the data from the
server and puts it both in your local mini-fs
and in your ordinary files.
If your local file has changed, git will merge
the changes if possible. If it can’t figure out
how to the merge, you will get an error
message. We'll learn how to deal with
these in the next lesson.
your local machine
a server, somewhere on the
internet, eg. github.com
pull
12
14. The whole picture using GHFW
.git
your local machine
a server, somewhere on the
internet, eg. github.ccs.neu.edu
sync
commit
In Gihub For Windows or Github For Mac,
“push” and “pull” are combined into a
single operation called “sync”. So in these
clients, there are only two steps (“commit”
and “sync”) to worry about, not three.
sync
14
15. Your workflow (2)
sync
edit
commit
edit
commit
edit
commit
sync
Best practice: commit your
work whenever you’ve
gotten one part of your
problem working, or before
trying something that might
fail.
If your new stuff is screwed
up, you can always “revert”
to your last good commit.
(Remember: always
“revert”, never “roll back”)
15
17. Your workflow with a partner
sync
edit
commit
edit
commit
edit
commit
sync
sync
edit
commit
edit
commit
edit
commit
sync
sync
edit
commit
edit
commit
edit
commit
sync
You You
Your Partner (or
you on another
computer)
Your partner
gets your work
from the server
You get your
partner’s work
from the server
server server
17
18. The new github desktop
• In the next few slides, we’ll give you the
updates for 2015.
• We won’t be using github.com. Instead we
will be using “Github for Enterprise” at
https://github.ccs.neu.edu
• The user interface for GHFW/GHFM has
changed. It’s now called “Github Desktop”.
• In the next few slides, we’ll show you how
your daily workflow looks with new interface.
18
19. Starting your work session
• Here’s what your Github Desktop should look like when you
open it up. Observe that your repos will be in the section
labeled “Enterprise”.
19
20. Where am I?
• The open blue circle indicates that you are looking at the most
recent local files
20
21. Always start by syncing
• This will download any changes that you or your partner have
made on other machines
21
22. Click on a dot to see a commit
• Clicking on the last dot will show you what was in your last
commit
• The dot turns blue
22
23. • In this view, you can see the first 6 characters of the unique
identifier (“the SHA”) for this commit
• You’ll need it for your Worksession Report
This shows your commit SHA
23
24. Now let’s work on our file
• Now the screen shows an uncommitted change.
24
25. • We write a commit message. Then we’ll click on “Commit to
Master”
Next, we commit our work
25
26. • Now it says “No uncommitted changes” again.
• You can also undo the commit if you want.
Here’s what you’ll see after a commit
26
27. • Click on the open circle to see what was in your commit, and
to record the commit SHA. Here’s that screen again:
Be sure to record the commit SHA
27
28. • Your work is not saved on the server until you sync.
Be sure to sync!!!
28
29. Submit a Work Session Report
• At the end of your work
session, submit a work
session report via the web.
• The URL for the work
session report will appear in
each problem set.
• The report will ask for the
SHA of your last commit.
You can get this from the
Github Desktop, as we’ve
shown you.
29
30. Summary
• In this lesson you have learned
– that git creates a mini-filesystem in your directory
– what commit, push, pull, and sync do
– the elements of the basic git workflow
– how git allows you to work across multiple
computers
– how git allows you and a partner to work together
30