►
Description
Join Phil Bossman and the rest of the RTPSUG leaders as we host the first of two hands-on, interactive git learning sessions. You will participate in follow-along demos to create and commit to your first repo. The RTPSUG leaders will help you master your first steps in git with one-on-one help.
Phil will lead a learning session that will cover the core commands of git. Learn the difference between push and pull, adding vs committing, local vs remote repos and how to undo everything when you have completely borked it up.
This is a Working Session, there will be background noise throughout the presentation as we help users make their first git repository.
A
A
And
what
that
really
means
at
this
point
is
we
want
to
take
someone
who's,
never
seen
get
and
try
to
make
sense
of
granting
we're,
not
gonna
go
down.
You
know
the
rat
bones,
I
call
it,
but
we
certainly
want
to
go
down
the
rabbit
trail.
Okay
is
if,
if
there
is
a
question
that
you
have-
and
there
is
something
that
that
is
interesting
to
you
and
like
I-
don't
understand
that
concept.
A
We
certainly
want
to
encourage
that,
especially
here,
especially
in
his
environment
and
one
of
the
things
that
people
online,
the
people
who
are
in
the
room.
We
have
resources
to
do
to
help
you
and
that's
what
this
user
group
is
all
about.
This
is
a
user
group.
We
want
to
get
people
to
interact
with
each
other,
but
we
also
want
to
assist
users
themselves.
A
So
this
is
your
resource,
and
we
want
you
to
know
that
we
source
in
the
room
as
much
as
you
can
I
mean
doing
that
we
want
to
just
say
a
level
set
of
what
we
can
do.
So
you
have
questions,
let
us
know
and
we'll
go
from
there,
so
yeah.
So,
let's
first
talk
about
what
is
gay,
so
it's
a
couple
slides
slide.
That
kind
of
thing
so
git
is
a
distributed,
distributed,
source
control
system,
okay.
A
So
what
that
means-
and
people
use
this
before
is-
is
a
mechanism
to
take
a
snapshot
of
source
code
of
files,
okay
and
keep
versions
of
that
source.
Okay
and
then
it
has
deep
mechanisms
to
keep
differences,
those
ports.
Okay.
So
if
you
have
a
place
where
hey
I
need
my
code
to
change
and
keep
track
of
it,
that
is,
it
can
be
a
place
for
that.
So
one
of
the
examples
when
you're
working
with
your
scripts
and
stuff
like
that,
you
may
have
nigo,
you
may
have
a
folder
basically
looks
like
this.
A
So
I
have
all
this.
This
is
one
of
my
actually
working
folders
and
so
one
of
the
stuff
that
I've
used
in
the
past.
So
here's
like
hey,
move,
em,
ru
and
then
I
got
this
one
called
PS
build
and
I
got
the
temp
point
and
then
I
have
all
these
other
scripts
over
here
with
like
an
underscore
in
front
of
them,
I'm
not
sure
I'm
working
on
this
one.
This
is
not
production
ready,
so
we're
gonna
put
some
stuff
at
the
beginning
of
it,
and
then
I
also
have
this
folder
called
like
working
scripts.
A
Hey.
This
is
other
stuff.
That's
kind
of
temporary
hey
get
these
dashes
in
front
of
it.
So
that's
typically
what
someone's
that
they're
trying
to
do
some
version
control.
This
is
like
a
poor
man's
version.
Control-
hey,
we
just
renamed
this
and
you
know
something
to
the
end
of
it.
All
that
stuff
so
get
allows
you
to
improve
upon
that
process
and
some
versioning
in
that.
A
A
So
if
you're
confused
certainly
ask
questions,
but
also
we're
going
we're
I,
don't
I
kind
of
have
a
roadmap
for
what
this
top
should
be,
or
what
this
session
to
be
I'm,
not
really
gonna
talk
about
this
session
is
the
regard
that
we
want
to
go
down
different
paths,
but
the
point
being
actually
I
lost
my
train
of
thought.
What
I
want
to
just
try
and
do
Oh?
So,
yes,
you
have
multiple
versions
of
this
file,
but
now,
if
you,
if
you
Virgin
it,
you
think
it
there
are
tools.
A
You
know
github
for
desktop
I
just
found
out
today
those
keep
cracking
and
then
there's
BS
code
and
some
other
tools
and
even
get
you,
though
itself
right
in
the
Bosch
console,
will
allow
you
to
find
differences
between
the
same
file.
So
here
is
my
working
file.
You
can
also
go
home
before.
What's
the
difference
one
day,
what
did
I
in
it
inside
of
this
file,
what
changed
inside
this
file
I
have
no
idea.
I
added
this
part
I
want
to
remove
this
part.
A
You
don't
know,
and
so
those
other
tools
allow
you
to
expand
upon
that.
So
everybody
there
are
multiple
ways
to
install
it.
You
kind
of
actually
exactly
worry
so
I'm
getting
ahead
of
myself
so
get
to
install
everybody
here
should
have
install
it
at
this
point.
Okay
get
is
totally
cross-platform,
so
install
it
on
to
UNIX
machines,
Linux
Windows
Mac,
so
anywhere
get
is
available
to
you
it's
there.
So
it's
the
same.
That
component
is
the
same,
so
they
can
tooling
that
you
use
yes
code
getting
out
github
desktop
even
the
github.
B
Read
about
was
that
Microsoft
themselves
is
moving
the
development
of
Windows
10
into
a
single
gate
repository
right.
So
if
you
guys
you
guys
using
Windows
10,
it
was
created
using
git
with
a
single
repository.
So
it's
it's
used
everywhere
and
it's
a
common
platform
were
developed
for
developers,
but
for
operations
type
folks,
a
lot
of
people
have
it
exposed
to
it.
A
So
one
of
the
other
things
is
that
I
want
to
do
a
quick
primer
and
he's
gonna
go.
This
is
gonna
kind
of
deepen
with
the
part,
but
I
want
this
to
I
want
to
discuss
this.
Is
that
what
is
being
effectively
at
this
point?
It's
this
version.
It's
not
a
software
application.
It
effectively
is
a
software
application,
but
as
I've
heard
it
described-
and
we
kind
of
very
beneficial
to
me
and
if
anybody
else
has
any
other
ways
to
sense
for
them,
please
certainly
share,
but
the
there
is
a
when
a
repository
is
defined.
A
Okay,
it
is
effectively
a
local
folder.
Okay.
That
then
has
a
logo
to
get
repo
git
repository
folder
system.
Okay,
that
is
now
managing
that
system.
It
is
a
a
git
repo,
so
it's
a
local
folder,
it's
a
dot
git.
So
if
you
have
enabled,
if
you've
initialized
get
into
a
folder,
you'll
always
see
a
hidden
folder
and
it
starts
with
dot
git.
So
on
a
Windows
system,
it's
going
to
be
hidden,
so
we
unhide
the
hidden
files.
Hey
the
folder
just
disappears.
A
So
if
you
look
there,
it's
not
there,
but
if
I
show
hidden,
there
is
a
hidden
folder
called
dot,
git
and
I'm
in
a
UNIX
environment,
it's
called
dot,
git
and
it'll
be
hidden
by
default,
but
you
just
do
a
dir.
So
that's
one
of
the
reasons
that
it's
there,
but
what's
inside
of
it
is
there
is
the
entire
structure
of
data
that's
inside
of
there,
and
so
we
kind
of
talked
before
is
that
when
you
do
things
when
you
initializing
a
git
repository
and
stuff
like
that,
it
takes
a
snapshot
of
the
stuff.
A
You
have
right
now:
okay,
compresses
it
and
then
takes
a
hash
of
it
and
then
just
fix
it
in
this
database
inside
this
boat
so
get
as
a
whole
is
inside
this
folder.
Okay,
folder
that
you're
working
out
its
side
is
called
a
working
folder.
That's
where
the
code
is
and
that's
where
everything
is
and
then
all
of
that
data
and
the
version
and
the
the
metadata
as
we
call
it.
It's
all
dumped
inside
of
this
underscore
git
folder.
Okay,
so
understand
that
there
is
this.
Folder
was
a
ton
of
data
in
there.
A
We
don't
need
to
go
down
that
rabbit
hole
or
that
rat
hole
as
far
as
I'm
concerned
is
to
what's
inside
of
here,
there's
some
details.
So
if
you're
fairly
need
to
get
there's
a
lot
of
you
don't
need
to
know
it's
there
just
know
that
there
is
something
there.
So
if
you
have
a
problem
later
on,
that
may
be
somebody
where
you
can
get
some
more
information,
but
you'll
go
down
some
documentation
again.
A
There
are
stages
when
you're
managing
stuff.
There
are
file
just
know
that
there's
something
called
people
modify
file,
so
it's
now
being
monitored.
It
is
not
being
tracked.
We
didn't
get
files
now,
it
can
be
modified
to
be
staged,
it's
ready
to
be
committed,
and
then
finally
it
has
been
committed,
and
so
files
are
in
those
stages
later
on.
So
that
kind
of
thing.
So
this
is
we're
going
to
start
off
with
getting
it
so
get,
and
it
is
so
you're
at
the
console.
A
We're
live
in
the
console,
there's
a
good
connect,
so
here's
my
zero
zero
folder
and
that's
that
folder
I
was
just
referencing,
so
I
want
to
get
enable.
This
fuller
house,
like
hey
this,
is
the
folder.
This
is
my
bunch
of
junk
stuff.
Okay,
what
are
we
gonna
do
with
this?
We
want
to
start
with
get
so
viciously
get
in.
B
It
it's
something
to
be
in
dude.
Remember
here
is
that
this
has
nothing
to
do
with
github
or
get
lab,
or
bit
like
this
all
local
on
the
file
system,
correctly
just
local
to
your
file
system.
So
without
ever
pushing
anything
to
any
web
service,
you
can
track
your
files
and
all
of
those
things
you
can
branch.
You
can
prepare
your
data
and
merge
them
back
in
local
on
your
file
system.
B
A
There's
no
and
and
inside
I'll
get
determines
remote,
and
so
it's
remote
and
the
point
like
I
want
to
say
he
says
the
web,
but
I
want
to
think
of
his
remote
because
it's
almost
too
much
the
same
but
remote
can
be
a
website
could
be
a
github
could
be
a
remote
repository,
but
it
could
also
be
a
file
share
somewhere
else.
It's
just
another
place,
so
there
is
a
possibility
that
I
can
put
my
repo,
my
remote
repo.
You
just
want
some
file
share,
so
it
doesn't
have
to
be
in
there.
B
A
A
And
that's
so
you
kind
of
see
at
this
point:
yes
just
created
this
empty
folder
for
me.
So
now
again
nothing
really
happened
at
this
point,
and
at
this
point
here
we
are
now
it's
just
an
empty
repository,
but
it
didn't
kind
of
like
what
did
that
do
for
me.
Didn't
do
anything
at
this
point.
Okay,
so
now.
A
A
B
A
Grab
it
grab
it
alright.
So
now
it
says
that
hey
there
are
211
files
that
have
changed.
It's
not
211
files
of
chains.
There
are
211
files
that
I've
added
to
this
folder,
my
working
folder,
and
so
now,
in
this
fashion
we
can
uncheck
them
all
and
just
add
a
couple
files
I
want
to
choose.
I
want
to
do
that.
At
this
point,
I'm
gonna
say
these
two
files
and
I'm
gonna
commit
them
initial,
commit.
A
Draft
one
I
meant
to
master,
so
they
come
off
this
change
history,
but
there's
also
now
a
history.
These
three
files
have
been
added,
so
we're
gonna,
then
add
the
next
one.
So
this
is
this
whole
idea,
actually
I'm
going
to
jump
out
and
do
this
here.
So
now
we
have
git
status
and
the
list
has
changed.
Nothing
has
changed
on
the
system
itself,
so
as
far
as
the
folder
structure
itself,
so
the
zero
zero
folder
structure
hasn't
changed
at
all.
A
D
B
A
We
will
get
to
that
at
the
end:
okay,
okay
and
that's
ultimately
what
whole,
but
like
level
two
is
gonna,
be
that
the
next
you
know
is
interacting
with
others.
So
the
idea
is
that,
in
this
folder
is
this
git
folder
is
local
to
this.
This
machine
and
the
reason
I
say
this
user
and
this
machine.
Actually
it's
effectively
to
this
folder,
okay
cuz,
then
I
could
have
a
different
folder.
That
is
another
git
repository
itself
and
then
kind
of
why
I
wanted
to
talk
about
the
file
system.
Is
that
dot
git
folder?
A
D
Way,
it
gets
to
be
a
little
bit
more
black
magic
than
science,
because
you
can
decide
what
you
want
to
do.
So
if
you
were
a
traditional
software
developer
and
you
were
working
on
some
project
that
probably
be
a
repository
for
that
software
project,
okay,
and
that
software
project
would
contain
five,
ten
hundreds
of
files
that
make
up
that
code
for
people
that
do
operations
or
write
PowerShell
scripts
that
are
like
one
script,
yet
ad
user
is,
you
know,
get
my
IDs
get.
D
D
It's
whatever
you
work
with
this
is
how
I
personally
do
it
if
I
need
to
share
my
code
with
somebody
else,
it's
you
know
if
I
want
to
have
a
product,
I
have
a
repository
for
my
work
code
and
I
have
a
repository
for
my
code,
and
my
code
goes
out
to
github,
and
anybody
can
browse
it
and
I
know
that
anything.
That's
in
that
repository
has
no
company
information
in
it
and
no
passwords
any
of
that
right.
That
may
not
be
the
exact
same
thing:
that's
in
a
company
private
repository
right.
D
A
So
if
you
want
to
put
your
files
into
one
folder
or
group
into
multiple
there's,
no
reason
why
you
can't
have
85
different
repositories
and
effectively
you
don't
really
think
so.
You
almost
want
to
know
that
there
that
that
git
folder
is
that
dot
git
folders
there.
But
you
don't
want
to
know
this
there,
because
it
just
doesn't
really
matter
so
you'll
go
into
that
folder
you'll,
do
a
git
push,
get
pull
or
you'll
do
git,
add
get
remove
and
then
it'll
just
black
magic
it
for
you
good
guys.
A
So
as
far
as
even
can
it
kind
of
stick,
it
take
a
step
back
and
on
your
own
computer,
open
up
a
command
prompt,
go
to
to
any
folder
that
you
want
to
put
some
code
into.
You
have
some
code
for
and
then
just
like
get
em
in
okay,
then
we'll
go
get
status,
yo-dee-hey!
Here's
all
this
files
that
we
currently
have
I'm
going
to
add
some
more
folders.
D
A
D
A
number
of
apposite
aureus
in
my
kidney,
the
guys
here
as
well,
if
anybody
is
just
curious
later
on
and
stop
by
I'll,
show
you
how
I
organize
my
stuff
and
I
think
you'll
find
that
each
one
of
us
probably
has
our
own
organization
system
yeah.
That's
the
that's
kind
of
the
beauty
of
get
its
it's
flexible
enough
that
you
can
do
what
you
want
to
do
and
the
next
person
can
do
what
they
want
to
do
and
all
those
scenarios
will
work.
Yeah.
A
So
we're
gonna
kind
of
maybe
I
should
just
keep
going
through
a
bunch
of
stuff,
and
then
we
can
just
talk
about
the
generic
stuff.
We're
gonna
skip
over
get
config,
so
some
git
commands
that
you'll
absolutely
need
it
later
on.
So
one
thing
too
is
that
this
is
get.
This
is
not
PowerShell.
Beware!
Our
powers
will
use
your
group
says
so
it
doesn't
conform
to
the
whole
verb.
Now,
I'm
kind
of
thing,
so
you
say
you
can
get
out
so
get
add,
is
adding
a
file
to
be
tracked.
A
So
a
file,
that's
not
currently
being
tracked,
you're
gonna,
add
it
to
the
tracking
okay
get
removed.
It
removal
does
exactly
the
inverse
hey,
remove
this
folder
from
being
trapped
completely.
There's
a
kid
log
to
tell
you
what's
been
happening
inside
what
you
can
add
in
what
you
can
removing
and
all
that
kind
of
stuff
commit
we'll
talk
about.
Some
more
is
what
that
is.
Naturally,
the
finalization
of
that
and
then
get
revert,
is
the
reverse
of
that
is
to
I
want
to
them.
Revert
one
of
those
commits
okay.
C
Right
now,
you're
saying
when
you
do
get
in
any
directory,
you're
saying
I
want
to
create
a
little
posit
over
here,
because
I'm
going
to
add
files
that
I
want
to
track
the
changes
desktop
get
in.
It
will
create
that
hidden
folder,
and
this,
like
we
said
before
this,
has
nothing
to
get
home.
This
is
an
online.
This
is
just
that
single
folder
that
you
ran
that
get
anything
it's
going
to
start
creating
the
structure.
If
you
do.
D
B
B
A
It's
my
land
online
info,
so
as
simple
as
that
good
status
and
so
kind
of
in
this
same
fashion.
So
now,
if
I
didn't
get
add
again,
is
that
this
is
where
I
was
talking
about.
This
is
a
staged
file,
desert
files,
waiting
and
ready
to
be
committed.
Okay,
so
this
now
and
you
get
my
land
file
and
actually
I'm
gonna
be
the
so
I
want
to
it
add
you
Mr
you
and
so
kind
of
in
this
fashion.
A
I
want
even
show
the
desktop,
because
so
we
kind
of
see
at
this
point
is
that
hey,
you
can
individually
add
individual
files
so
get
now
we're
going
to
these
two
files
are
ready
to
be
committed.
So
in
that
same
fashion,
what
you'll
do
is
you
get
a
commit,
and
then
you
need
to
give
it
a
message.
So
also
it's
kind
of
great
too
is,
if
you
don't
know
all
the
syntax
tells
you
hey.
You
have
to
give
me
a
good
commit
message.
You
need
to
tell
me
what
I
just
did
adding.
C
B
A
And
so
you
test
it
in
this
fashion,
it's
kind
of
good
in
the
desktop.
It
shows
you
instead
of
the
death
instead
of
the
desktop,
so
it
created
a
snapshot
of
those
files
used
to
gave
it
the
hash
name
and
there's
the
description
it
had.
It
said
two
files
had
been
changed
and
it
did
you
know
that
many
answers.
Basically
that's
so
many
lines
were
in
the
file
and
then
it
created
these
notes.
That
kind
of
thing.
D
So
in
get
when
you
add
messages,
you
can
add
a
one-line
commit
message
or
you
can
want.
You
can
make
almost
like
if
you
were
writing
an
email
with
a
subject
and
more
details
in
the
body
like
comments
about
your
commit
message,
the
better
practice
is
to
write
sort
of
subject,
you
know
Rev
to
of
code
and
then
in
the
body
you'd
say
you
know,
fix
these
bugs
that
other
than
a
lot
of
us
just
say
you
know,
push
new
file
a
one-line
or
commit.
A
Yeah
look
actually
a
lot
of
my
commit
messages.
Are
this?
You
know
event
long
stuff
done,
you
know,
so
it's
not
really
so
this
is
also
kind
of
thing.
You
know
we're
not
really
developers
and
so
we're
using
some
of
their
tools,
but
you
know
I've.
Actually,
some
developments
are,
you
know
just
as
worse
with
commit
messages
but
effectively.
This
is
you
know
so,
just
like
in
github
desktop
you
saw
here,
hey
I
can
put.
This
is
the
get
message
and
then
this
here
is
an
extra
description.
A
B
D
When
you
make
a
commit
message,
you
can
think
of
that
as
making
a
message
to
your
future
self,
because
what
you
would
use
that
commit
message
for
is,
if
you
want
to
go
back
and
look
at
previous
changes
to
figure
out
what
the
hell
you
were
doing.
So
what
Phil's
talking
about
is
you
can
be
as
verbose
or
as
minimal
in
your
commit
messages
as
you
want,
it
really
depends
how
much
you're
able
to
figure
out
from
what
you
did.
D
So,
for
example,
if
you
made
10
commits-
and
you
commit
messages-
was
stuff
stuff
to
stuff
3,
some
more
stuff-
that's
kind
of
hard.
When
you
look
at
your
change
history
to
say
how
did
I
do
and
stuff,
you
may
be
able
to
look
at
the
files
to
figure
it
out,
but
it
would
be
better
to
say,
like
added
a
new
file
to
address
an
issue
removed
above
remove
this
file.
D
That
was
conflicting
because
then
your
future
self
can
go
back
and
look
at
it
and
say
oh
I
kind
of
understand
what
I
was
doing
there
and
then,
when
we
go
to
next
month
and
you're
committing
code
in
a
group.
And
someone
is
gonna,
look
at
your
code
and
try
to
figure
out
what
you
did
and
if
they
should
add
it
to
the
repository
stuff.
Connor
doesn't
help
them
figure
out
what
you've
done.
A
There's
a
size
limit
in
there's
a
size
limit
I'm
guilty,
but
but
it
can
be
as
big
as
at
once
because
effectively
I'm
using
certain
words
and
its
own,
so
I
don't
want
to
download
into
the
rabble,
but
it's
taking
a
snapshot
of
that
file
and
then
puts
it
inside
the
metadata
inside
there.
So
it
can
be
as
big
as
it
needs
to
be,
but
then
it
becomes
unmanageable
and
untransferable
later
on.
So
it
has
a
thing,
but
you
can
even
get
hub.
A
B
A
B
B
And
another
correct,
so
when
you
store
it
in
your
text
file,
when
you
get
that
hash,
it's
only
storing
the
difference
between
their
five.
It's
not
actually
100%
packing
in
your
five.
The
reason
for
that,
so
that
when
you
look
at
your
history,
you
can
be
able
to
see
all
of
your
changes.
So
when
you
hit
something
like
a
bland
or
something
like
that,
where
it'll
show
you
at
this
time,
Paris,
we
have
changed
these
five
learners
and
John
made
a
line
just
what
it's
really
doing
is
doing
like
what
we
do
with
bitcoins.
B
It's
sort
of
creaking
a
journal
of
all
your
changes,
okay,
and
by
combining
all
those
key
changes,
that's
where
you
are
named
right,
so
it's
just
keeping
a
history
of
that.
So
you
think
the
of
that
you
can
go
back
and
any
time
to
get
a
change
that
you
made
all
right.
So
it's
all
at
the
end
of
a
steel
version,
another
version.
So,
if
I
take
a
line
this
blank
and
I
say
that
initially
this
point
add
one
line.
This
is
Paris
on
it
and
the
hash
is
going
to
say
Paris.
B
A
So
so
we
added
a
bunch
of
files
in
there
now
committed
now
what
what
has
changed
in
your
folder,
your
app.
Nothing
has
changed
so
now.
There's
nothing.
You've
committed
all
of
those
things,
and
so
the
status
is
not
empty
because
there's
nothing
you.
It
is
untracked
and
you've
made
no
changes
to
the
file,
so
that's
actually
where
I'm
at
right
now.
So,
while
you
guys
were
talking,
I
now
made
a
fun
way
to
change
to
a
file.
So
now,
if
I
do
get
status,
I
need
to
change
the
file.
A
A
A
A
A
B
Do
it
anybody
could
put
in
class
logs
and
that's
a
buzz
trees,
but
I,
wouldn't
even
do
that?
A
lot
of
this
a
lot
personally
right,
I've
seen
that
that's
for
a
lot
of
things
break
down
and
that's
that's
what
what
shouldn't
be
in
there
binaries
P
secrets,
yadda
yadda,
there's
a
lot
a
lot
of
tooling
around
making
that
work
right,
because
a
lot
of
your
code,
it's
gonna,
be
in
get
so
you're
gonna
have
to
reference.
You
know
other
resources
that
require
authentication
right
and
there's
methods
around.
B
B
B
B
B
A
We've
we've
done
a
bunch
of
things
at
this
point,
and
so
now
we
can
come
back
to
effectively
one
of
the
next
commands.
We
have.
This
point
was
get
laws
kind
of
talked
about
some
of
that
stop.
Okay,
so
one
of
the
things
that
that
we
need
to
understand
well
with
get.
Actually
you
know
what
I'm
gonna
do
one
more
time.
B
B
A
A
You
can
then
see
differences
from
files,
so
you
talked
about
using
github
test
op
and
you
then
see
versions
and
as
things
go,
and
so
one
of
the
points
that
we
kind
of
talked
about
before
is,
if
you
use
a
GUI
GUI
tool,
you
crack
in
getting
a
desktop
or
vyas
code,
or
anything
else
like
that.
You
can
see
dips,
okay
and
say:
hey
I,
remove
this
line.
I
added
that
line
this
line
was
added
this
language
for
me
in
that
fashion.
So
this
is
one
of
the
beneficial
points
about
using
git
itself.
A
B
C
A
At
this
point,
it's
kind
of
what
you're
talking
about
you.
You
think
it
you're
talking
to
your
remote
repository
and
so
that's
kind
of
what
we're
getting
to
perfect
right
now,
but
that
but
again
to
to
Mike's
point
yes
toad
kind
of
abstract,
some
of
that
and
they
call
it
sinking
and
they
call
it
other
things.
A
They
don't
use
those
GUID
terms,
and
so
it's
sometimes
tough
to
try
and
and
piece
it
all
back
together
and
it's
doing
a
bunch
of
stuff
for
you
and
it's
adding
a
bunch
of
stuff
to
you,
your
your
config
file
itself.
So
it's
not
that
simple
to
put
it
back
together.
If
you
worked
up
cuz
you
90
percent
of
time,
you
get
down
to
the
console
and
two
big
commands
themselves
do
want
rebase
or
something
like
that
to
kind
of
get
yourself
back
together.
But
that's
where
we
are
at
this
point.
A
So
we're
gonna
talk
about
good
points,
so
everything
you've
talked
about
at
this
point.
It's
been
in
local
repository
so
think
again,
I'm
coming
back
to
it,
because
it
makes
sense
to
me
and
certainly
please
people
have
more
experience
with
it
if
they
have
a
different
vision
of
what
it
is,
certainly
share
it,
but
I
keep
thinking
it's
that
git
folder.
Okay,
so
I
currently
have
this
copy
of
what
I
have
but
is
more
weird.
The
snapshot
is
a
time
so
now
I
want
to
take
that
on
a
picture
somewhere
else.
A
D
A
A
Okay,
we
said
hey
make
that
a
remote
repository,
the
link
to
this
one
and
then
we
assigned
the
Latin
second
part
is
in
the
same
command
pushed
to
that
as
an
upstream,
and
so
now
we
can
patient
to
that
in
the
future.
So
now,
if
we
refresh
and
get
itself
hey,
look
at
all
these
changes,
I
just
did
anything,
but
the
beauty
here
is
that
we
notice
now
two
sets
hey
seven
minutes
ago.
We
had
this
code
here
and
then
twenty
minutes
ago
we
had
this
code.
A
We
added
all
these
pieces
of
code
to
this
as
we
went
along.
So
very
simply.
We
now
have
a
remote
repository.
You
now
have
a
remote
repository
that
has
a
copy
of
everything
we
did
along
with
all
the
changes
we
made.
We
added
some
stuff
we're
going
to
come
here
to
actually
this
file.
Okay-
and
we
can
can
then
come
here
to
also
history
and
see
that
hey
this
code
has
been
changed
three
times
so
I
went
through
three
iterations
of
this
until
hey
this
was
initially
added
at
this
point,
then
we
updated
this.
B
B
A
C
A
B
B
A
A
The
whole
P
point
here-
this
is
all
over
stuff
that
got
here
but
points
that
I'm
looking
for
is
hey
this
remote
thing,
so
I
can
find
an
option.
That
is
just
normal
other
paths.
It
can
be
some
other
thing
and
so,
as
I
get
added
pushing
on
from
this
folder,
it
just
propose.
You
know
remotes
that
never
yeah,
so
that
is
now
my.
A
I
think,
then
you
do
a
push
upstream
origin/master
or
you
can.
Do
you
same
thing?
Git
push
you
origin.
So
what
are
you
pushing?
So
you
say
git
push
to
the
upstream.
What
I
want
to
push
and
then
what
branch
you're
using?
So
we
didn't
I
didn't
really
want
to
talk
about
branches,
because
that's
kind
of
like
a
level
two
kind
of
thing
as
far
as
I'm
concerned.
So
most
90%
of
all
you
know,
you're
just
getting
work.
You're
all
going
to
live
inside
is
called
master.
It's
master
branch.
A
If
you
want
to
then
work
on
some
other
stuff,
we'll
talk
about
it
next
time.
Yes,
you
can
branch
out
and
say:
hey
I
want
to
work
on
just
this
other
part.
I
want
to
keep
it
separate
from
this.
I
want
to
live
within
the
same
working
folder.
Then
you
can
branch
off
and
then
they
keep
branches
can
merge.
Franchis,
you
can
branch
off.
Yes,
so
that's
kind
of
a
different
topic.
B
A
You
have
this:
is
you
have
this
work
here
and
we
pushed
it
up
to
our
remote
repository?
Okay.
So
now
what
do
I
do
so
now?
Hey
now,
I
have
my
remote
repository
and
so
in
this
vision
of
what
is
happening.
Typically
to
is
hey
I'm
working
here
in
this
PowerShell
console.
This
is
me
working
at
work.
Okay,
so
now
I'm
going
to
go
home
and
actually
access
that
same
repository,
actually
I'm
going
to
jump
out
so.
A
Let's
take
it
home
yeah,
so
I'm
going
to
work
on
github,
okay,
I
want
to
work
on.
Might
this
is
my
in
this
powerful
seven
console
is
now
home
all
right,
so
I
want
to
get
my
code
that
I
had
in
my
repo
okay,
if
you're
using
github
itself
the
website
you
can
go
to
clone,
there
is
something
called
globe,
and
that
is
the.
A
So
don't
give
it
a
name
at
the
very
end:
it'll
simply
use
the
20
2000
name,
or
you
can
name
it
to
something
else
you
want,
so
it
doesn't
have
to
be
the
same
thing.
So
I'm
gonna
simply
do
it
and
see
it
says
cloning
20
2000.
It
got
that
entire
thing.
What
it
happens
is
it
downloads
that
entire
git
folder,
ok,
the
git
folder,
the
dot,
git
folder
and
then
an
extra
minute
actually
checks
it
out
master
director.
So
now
in
this
older
is
an
exact
there's.
A
Exactly
what
we
kind
of
talked
about
before
it's
gonna
be
so
now
here
is
another
copy
and
think
this
is
tutor
computer,
so
I
can't
do
it.
So
this
is
a
remote
computer.
So
now
I
have
at
home.
I
have
an
exact
copy
of
what
was
in
my
repository
from
work
that
I
had
pushed
up
my
code,
so
I
took
my
time
at
work
and
pushed
it
to
github,
and
now
I
pulled
it
down
from
github
to
my
home
computer.
Looking
here,
okay,
so
does
everybody
kind
of
understand
that
at
this
point
or.
A
A
All
right,
and
so
just
like
before
now
we're
at
home.
What
do
we
need
to
do?
We
can
just
push
it
in
this
fashion.
In
this
case,
especially
so
you
know
Steven
to
point
out
is
that
we
don't
need
to
add
a
an
upstream
here
because
we
cloned
it
from
the
remote.
So
in
this
fashion
we
went
and
got
somebody
else's.
Repository
won't
affect
mental
powers.
A
E
A
And
you
may
not
in
moon
stream,
okay
in
that
spring
and
he
had
work
or
whatever
we
call
this
in
the
blue
screen
II,
we
initialized
a
brand
new
empty
repository.
We
added
a
bunch
of
files.
There
was
no
remote
there,
so
we
had
to
add
you
that
git
remote
add
right,
then
that
URL,
which
is
our
kid
hubba,
3pi
okay.
So
we
added
that
remote
inside
of
that
local
repository.
Okay.
A
So
then
one
came
home
came
home
into
this
black
window,
okay,
we
then
to
sub
git
clone
the
remote
to
me,
and
so
now
we
have
a
local
copy
of
whatever
that
was
now
I
have
my
local
copy.
So
if
you
push
you
push
back
to
where
its
remote
is,
it
came
down
with
the
remote
okay
work.
The
remote
has
been
set
to
where
it
came
from
okay,
so
kind
of
in
that
control.
L
again,
you
can
kind
of
see
here
at
this
point:
okay,
git,
config
L,
it
tells
you
hey.
The
origin
is
exactly.
A
B
A
B
A
D
It's
working
that
different
than
the
way
we
normally
do,
creating
the
local
filter
or
end
or
remote
folder,
and
they
want
to
together
basically
say
this
local
folder
should
point
to
this
remote
I.
Don't
normally
do
that
way.
I
usually
make
a
remote
and
clone
it
or
I
work
local
and
push
it
up,
I'm,
not
sure
how
to
define
guys
made
a
local
repository.
Yes
called
repository
one.
Yes,.
D
B
D
A
Didn't
work
because
somebody
or
that
something's
not
working
one
of
the
things
that
that
we
may
have
a
problem
with
some
of
that
is,
if
you
created
the
the
github,
the
github
repository
and
you
initialize,
you
actually
created
a
new
commit
into
it
with,
like
the
initialization,
hey,
you
know,
have
a
readme
and
all
the
things
that
you
created
a
new.
You
know
you
diverged
the
the
heads
or
the
last
commit
okay.
So
that's
this
plan,
cept.
A
B
C
Okay,
so
when
you,
when
you
create
it,
I
get
a,
but
you
said
you're
a
lot
of
times
if
you
create
a
readme
and
all
icon,
stuff,
you're,
initializing
and
you're
creating
files
in
that
repository,
even
though
we
didn't
actually
make
the
files
it
creates
a
readme
inside
right.
So
you
end
up
with
your
local
house
file
a
B
and
C.
Your
remote
has
five
DB
now
you're
trying
to
say
all
this
stuff
up
there.
It's
like
I
already
have
stuff
up
there
and
you
don't
have
that
stuff
there.
So
you
don't
in
two
weeks.
B
D
Remember
when
you,
when
you
commit
when
you
make
holder,
if
you
get
out
or
you
make
the
folder
and
your
local
repository
you're,
making
them
folder
when
you
initialize
that
creating
the
reference,
what
Kevin
just
said
and
the
reference
says,
there's
no
files
and
then
you
create
another
one
on
the
other
side
and
it
may
be
a
little
different
and
if
I
was
going
to
try
to
figure
out
the
differences
between
it's
gonna
say
do
something
now,
because
these
to
focus
or
not,
but
they
mean
it's
nice
cuz.
They
reference
points.
D
D
A
The
last
point
I
want
to
put
out
is
that
kind
of
now.
We've
escalated
to
the
point
where
now
we
have
effectively
two
local
repositories
on
different
computers.
We
have
one
remote
repository
in
github
bitbucket,
something
some
remote
okay
and
then
we
got
to
keep
then
what
we
want
to
describe
at
this
point.
A
So
I'm
gonna
come
back
to
hey,
so
I
was
back
here
at
home
in
the
black
screen
and
I
fixed
I
created
a
new
commit
I
did
some
edits
back
to
the
file
and
I
pushed
it
back
up
to
remote
O's
and
so
now
back
into
work.
I'm
gonna
come
back
to
work
on
the
blue
screen
and
then
how
do
I
get
it
back?
So
this
is,
we
were
we.
A
We
initially
pushed
it
up
to
the
dirt
there
and
now
I
want
to
get
it
back.
Okay,
the
first
time
I
got
it
back
as
I
had
nothing
so
I
cloned
from
there.
So
I
created
it,
but
effectively
it
was
a
poll
we
did
a
poll
and
a
check
out.
We
don't
you
talk
about
the
point.
Neither
pull
a
check
out
for
that.
This
point.
I
already
have
my
local
repository,
it
knows
what
it's
remote
is
and
knows
what
its
upstream
is.
At
this
point,
all
we
do
is
get
pull,
and
now
we
see
hey.
A
The
remote
repository
is
beyond
where
I
am
so
I
need
to
pull
any
new
changes.
Those
changes
can
be
in
five
different
files.
I
can
move
five
files
and
everything
you
see.
It
says
here,
hey
and
I.
Have
this
get
let
my
file
two
lines
were
changed.
One
final
change
and
inserted
more
here
and
it
delete
in
one
line.
So
Kevin
says
when
I
now
pulled
back
in
from
the
remote
here's,
how
I
do
it
so
we
have
first
get
your
initial
line.
So
yeah.
A
That's
at
this
point,
then,
is
everybody
kind
of
understand
that
so
the
practice
when
you're
working
with
two
repositories,
both
on
two
different
computers,
is
you're
going
to
be
pushing
and
pulling
from
those?
Typically
okay,
when
you
first
start
out
you're
going
to
do
some
other
stuff,
you
know,
do
a
clone,
typically
and
then
you'll
have
to
maybe
you
know
fix
it.
If
you
don't
keep
starting
from
branding
places,
could
you.
D
A
C
Because
that's
we
do
that
in
the
issue.
No,
because
what
ends
up
happening
is
when
you
try
to
rectify
that
it
says.
I
have
this
response
so
essentially
ends
up
happening
as
you
guys,
like
yeah,
there's
a
commit.
That's
up
here,
it's
not
down
there
and
it
happened.
They're
not
like
in
mind.
Since
what
happened
says
hey.
We
have
different
files
here
than
out
here.
C
How
do
you
want
to
merge
these
different
commits
that
don't
exist
in
both
location
has
to
be
right
and
we
have
a
readme
here
so
I'll
be
here
and
a
B
and
C
here
it
says
actually
a
B
and
C
to
get
to
the
point
where
I
just
have
Dean
or
do
you
want
me
to
create
a
B
and
C
and
delete
de
all
right
has
no
idea
what
to
do
so.
As
long
as
when
you
create
that
repository
link,
it
you
don't
initialize
it
and
have
files.
B
A
Remote
is
robot
built
and
then
he's
doing
the
clone,
which
is
the
form
along
with
doing
the
remote,
the
remote
connectors
all
at
the
same
time,
and
so
when
he
builds
the
opal,
it
is
from
the
master.
It's
probably
either
remote,
so
do
it
through
me,
absolutely
can
do
that
one
is
differently,
and
so,
if
you
start
with
the
remote
I
mean
start
with
the
local,
so
now
I
just
added
it
here.
So
now
this
new
folder
called
99.
A
Okay,
it's
20,
20,
99
I'm,
going
to
come
back
to
github
and
add
a
new
repository,
and
actually
you
know
what
I'm
gonna
do
is
I'm
gonna
call
this
thanks
to
that
point.
Is
that
doesn't
have
to
be
anything
okay,
we're
gonna,
say
your
private
fixed
example,
and
then
we're
not
gonna
check
this,
so
I'm
gonna
call
it
whatever.
This
is
just
some
repository
name.
It's
just
the
name
doesn't
matter,
okay,
we're
gonna,
call
it
private,
because
I
want
to
show.
A
And
I'm,
not
gonna
initialize,
this
or
actually
you
know,
I
think
we
will
initialize
it
okay,
so
we're
gonna
exit
that
with
the
example.
So
we're
gonna,
let
it
know
initialize,
but
you
know
here
what
it
says
it
says:
hey
there
is
an
initial
commit
called
the
readme.
It
created
the
reason
for
me
alright.
So
in
this
example
now
here
so
I
get
all
right
here.
I
have
an
initial
commit
array.
My
local.
C
B
A
A
A
B
A
B
D
So
while
we
while
we're
doing
this,
does
anybody
have
any
questions
fulfill
that
they
they
want
to
think
through
or
online?
Is
there
any
questions
that
we
want
to
post
to
the
room
or
anything
like
that?
Yes,
it's
8
o'clock,
we're
pretty
close
to
where
we
would
normally
end
the
weekend.
Go
as
long
as
people
have
questions,
they
don't
understand.
B
Sorry
so
one
of
my
classic
things
yet
is
I've
got
a
repository.
I
got
much
files
in
there
I
refactor
my
code.
A
little
bit.
I
no
longer
need
a
file,
so
I
delete
it
yeah,
okay,
I
you
do
the
commit,
and
so
on
a
couple
of
weeks
later
I'm
like
there's
something
in
that
file
I'd
like
to
see
don't
want
to
go
back
and
see.
B
E
Yeah,
so
if
you
go
through
the
log
and
if
you've
got
a
specific
commit
message
in
there
from
when
you
deleted
that
file,
you
can
do
a
git
checkout
from
that
file
from
that
using
that
using
the
sha-1
hash
and
you
can
check
out
the
repository
from
that
point
in
time.
You
can
also
get
a
branch
from
that
time
and
then
you
can
pull
files
between
branches
using
git
checkout,
but.
A
B
E
E
You're,
relying
on
the
get
log
log
being
able
to
go
back
in
time
to
see
what
it
looked
like
at
a
specific
point
in
time,
so
you
can
say
git
checkout
shall
one
hash
in
which
you
can
from
the
gate
log
and
see.
If
that
is
there,
if
not,
you
can
go
back
to
the
print.
The
next
committee
at
the
next
commit,
and
you
can
compare
the
branches
back
in
time
to
see
how
they
differed
and
you
can
use
them.
E
A
few,
if
you
click
on
any
of
the
files
in
there
so
get
from
Quinn
cute
or
anything
like
that,
blame
at
the
top
they're
all
blame
in
history
and
then,
if
you
scroll
down
the
left,
you
see
on
38
minutes
ago.
You've
got
like
the
little
squares.
Click
on
that
and
it'll.
Take
you
back
to
how
that
looked
prior
to
that
change.
E
When
it
was
made
38
minutes
ago,
I'll
show
you
the
previous
change,
and
then
you
can
click
back
again
and
go
back
through
the
history
on
that
that
file
was
when
that
file
was
last
changed.
So
if
you
know
a
specific
change
was
made
in
that
file,
you
can
use
the
blame
to
go
back
to
see
who
made
that
change
in
when.
E
No,
no!
That's
where
you
have
to
use
git
log
I'll
find
out
when
that
file
was
changed.
Yeah.
You
need
a
rough
idea
of
when
it
happened,
and
then
you
can
see
get
check
out,
use
the
sha-1
hash
that
you
retrieve
from
git
log,
and
you
can
check
the
repository
out
as
it
looked
at
that
point
in
time
when
that
commit
was
made
in
the
log.
Yes,.
B
E
So
I've
done
that
before
I've
done
that
before
restructure,
the
entire
get
posit
ory
and
then
decided
the
oops,
that
structure
doesn't
work,
but
I
need
to
keep
the
files.
How
I've
currently
got
created
a
branch
from
where
I
was
and
then
pulled
files
between
the
branches
you
can
get
check
out.
You
do
get
my
check
out
branch
that
you
want
to
pull
it
from
and
the
file
you
can
even
do
particular
lines
from
a
file.
E
If
you
really
want
to
6
to
38
was
changed,
you
can
do
it
get
checkout
master
branch
for
this
file
and
these
lines
are
all
pull
those
changes
in
your
code-
yeah,
that's
not
right,
but
that,
but
but
all
I'm
demonstrating
there
is
that
the
log
has
everything
in
it.
That
was
changed
throughout
time.
That's
that
that's
how
powerful
the
log
is.
You
can
go
back
in
time,
see
how
things
used
to
look.
You
can
check
out
those
at
any
point
in
time
and
then
pull
changes
between
previous
changes.
E
Previous
commits
previous
branches,
it's
it's
really.
It
gets
very
in-depth
very
quickly.
This
is
the
whole.
Do
I
just
start
again
and
clawed
my
repo
again
and
then
redo
all
my
work
or
do
I
spend
a
little
bit
of
time
figuring
out
how
to
undo
whatever
totally
broken
record
everything
so
but
yeah
you
could
do
you
can
do
git
log
find
it
find
the
sha-1
you
get
to
check
out
of
that
she'll
one,
not
take
you
back
in
time.
E
A
A
E
E
Yeah,
and
as
long
as
you
know,
you
can
recover
your
files,
because
it's
in
the
history
of
your
git
repo,
you
can
save
yourself
a
lot
of
pain
by
just
one
that
it's
in
there.
Someone
to
get
the
word
from
the
log
and
good
checkout
is
how
you
would
do
that.
Whether
you've
got
a
page
that
whether
you
use
some
magic
or
sacrifice
your
firstborn
to
get
that
it
back
about
your
report.
It
makes
no
difference
as
long
as
you
know
it's
there
and
you
know
how
to
get
it
rich.
You
could
see
yourself.
E
C
E
One
of
the
one
of
the
stories
that
I'll
tell
when
I
give
my
get-ups
and
session,
which
I
we
deliver
when
a
PS
convey.
You
is
I
learned
in
German
from
messages
I
got
given
a
new
system
that
I
didn't
know
was
in
German
was
all
in
Linux,
which
I'm
terrible
at
the
guy
who
left
and
left
me.
This
system
had
a
zero
ticket
number
messages
which
told
me
exactly
what
he
was
doing
in
a
way
so
I
was
able
to
steer
right.
Okay,
he
gives
him
one
axis
at
this
moment
in
time.
E
A
So
at
this
point
kind
of
like
this
is
the
great
point
where
we've
now
kind
of
discovered
that
hey
there's
more
information
here
and
there's
more
that
we
can
really
do,
and
so,
ideally,
what
we
try
and
use
some
of
the
things
we've
talked
about.
I'm
gonna
put
all
these
little
repos
kind
of
thing
when
we
kind
of
template
like
up
in
our
github
repo,
so
you're
free,
frites,
actually
pull
that
down
the
artisan
repo
has
stuff
in
there.
A
A
Okay,
we're
going
to
play
with
a
lot
more
check
out
we're
gonna,
forking,
other
people's
branches,
we're
going
to
be
merging
with
other
people
and
trying
to
really
break
things
so
that
we
can
figure
out
how
to
work
with
this
and
working
with
other
projects
and
contributing
to
other
projects,
and
that's
kind
of
better
you've
checked
it
into
the
next
part.
So,
hopefully,
we
went
down
some
rabbit
holes,
but
also
we
didn't
get
too
deep
where
you
couldn't
get
things
operational
and
we
wanted
you
to
get
at
least
something
operational.
A
You
certainly
want
you
to
practice
some
more
and
so
that
when
we
come
back
again,
you'll
have
really
good
questions.
We're
really
good!
You
know.
Examples
of
hey
I
tried
this,
but
it
didn't
work,
but
also,
certainly
don't
wait
till
a
month
from
now.
Anyway.
Hey,
let's
talk
about
this
and
well
want
to
covers
their
topics,
but
we
also
want
to
answer
your
questions
in
that.