►
Description
Samantha (GitLab L&D) show the Learning & Development team how to install GitLab locally.
Learn more how to Edit the Handbook Locally: https://about.gitlab.com/handbook/git-page-update/#editing-the-handbook
Learn more about GitLab Learning & Development: https://about.gitlab.com/handbook/people-group/learning-and-development/
A
Yeah,
so
I
use
sublime
text
editor
adam
is
another
one
that
I've
heard
is
really
good
and
the
other
one
that
I've
heard
is
pretty
good
is
also
vs.
Code
sublime
is
really
basic.
It.
It
works.
Fine,
I
think,
if
I
was
doing
more
actual,
you
know
coding
writing
things
in
ruby,
whatever
other
language,
then
I
would
probably
want
something
beyond
sublime,
but
just
for
like
basic
html
index,
you
know
page
text.
Editing
I
find
sublime
is
fine,
but
what
I'll
do
is
I'll
just
share
my
screen
and
kind
of
go
through.
A
So
I'm
just
saying
that,
because
you
don't
have
to
put
it
in
this,
folder
is
now.
I
don't
need
this
extra
layer
of
a
folder
anymore.
It
could
just
be
this
on
my
desktop,
so
if
I'm
getting
ready
to
edit
something
or
create
a
new
page
or
anything
in
the
handbook,
the
first
thing
I
have
to
do
is
open
my
terminal,
and
I
have
to
navigate
to
this
folder
and
the
way
that
you
do
that
in
your
terminal
is
by
and
if
I'm
going
too
fast
on.
A
Anything
just
tell
me
to
stop
is
so
you
have
to
change
your
directory
and
also
just
want
to
note
too
that
I
use
the
commands
that
I
use.
I
don't
necessarily
completely
understand
why
I
use
them.
I
don't
have
a
full
understanding
of
the
commands
themselves,
but
I
know
what
they
do
and
like
what
order
to
use
them
in.
So
this
is
like
a
dumbed
down
version
of
git
lab.
I
think
I.
A
Yeah-
and
I
also
I
have
learned
that
google
in
the
and
the
get
like
documentation
is
my
best
friend
because
there's
a
few
commands
that
I
use
infrequently,
but
you
know
maybe
once
a
month
and
I
have
to
search
them
and
that's
something
I
learned
very
early
on
in
my
coding.
Bootcamp
is
like
learning
how
to
code.
It
means
you
know
how
to
use
google
so
usually,
if
you
type
whatever
command
or
whatever
error
comes
up
in
your
terminal
into
google,
you
can
find
the
answer
pretty
quickly.
A
So
I
open
up
my
terminal
and
I
need
to
get
to
this
folder.
So
first
I
have
to
do
change
directory
to
my
desktop
and
then
you
can
see
it
has
my
name
in
the
terminal
and
then
it
tells
me
what
folder
I'm
in.
So
I
know
that
I'm
on
my
desktop
and
then
from
there
I
have
to
go
to
my
project
folder
and
then
from
there.
A
I
have
to
go
to
gitlab.com.
So
I
think
that
there's
a
way
that
you
can
just
do
that
with
backslashes,
so
you
don't
have
to
do
three
different
commands.
You
can
just
do
desktop
backslash
gitlab
project,
backslash
www.gitlab.com,
but
it's
just
like
a
habit
that
I
have
that
I
do
it's
three
separate
so
now.
I
know
that
I'm
in
this
folder,
which
means
I
can
start
to
access
all
of
the
pages
that
are
within
gitlab.com.
A
The
first
thing
that
I
do
and
I'm
not
actually
going
to
run
the
whole
thing
right
now,
because
it
takes
a
lot
of
bandwidth
and
can
take
a
little
bit
of
time.
Is
I
check
the
status
of
my
of
my
local
copy
of
gitlab.com
in
comparison
with
the
remote
copy
of
gitlab.com.
So
when
you
download
gitlab.com
from
from
git
lab
to
your
local
computer,
you
have
to
make
sure
that
it
doesn't
update
automatically.
You
have
to
make
sure
that
you
update
it
all
the
time.
A
Otherwise,
changes
that
are
made
in
the
origin
of
the
project
aren't
going
to
show
up
on
your
computer.
So
the
way
that
you
kind
of
check,
if
you're
up
to
date
or
not,
is
a
few
different
commands.
So
you
can
type
the
command
git
status
at
any
time
and
what
it's
going
to
tell
you
is
what
branch
you're
on
and
the
status
of
that
branch,
and
it
will
give
you
some
information
as
to
like.
A
A
So
the
master
branch
is
the
name
of
the
main
branch
that
you
want
to
keep
up
to
date
with
the
gitlab.com
project.
At
all
times
you
never
make
changes
locally
to
master
master
is
just
there
to
keep
the
gitlab.com
project
up
to
date
on
your
computer
and
then
you
make
branches
from
that.
If
you
ever
make
a
change
to
master,
it's
never
going
to
get
mur
like
you
won't
be
able
to
merge
it
to
gitlab.com
it.
Won't
you
just
you
can't
it
won't
go.
It
won't
change.
A
A
It's
going
to
pull
that
whole
branch
to
your
local
computer
and
anything
that
matches
the
gitlab.com
is
going
to
just
stay
because
you
can
assume
it
hasn't
been
changed
since
the
last
time
I
updated,
and
so
it's
just
going
to
remain
the
same.
Anything
that's
changed
is
going
to
be
pulled
in
as
a
change
and
it's
going
to
update
your
local
version.
A
Origin
master
is
going
to
reach
out
to
gitlab.com,
say
what's
different
online
versus
locally,
and
it's
going
to
pull
all
those
changes
and
make
the
update
I'm
afraid
to
do
it
right
now,
because
sometimes
it
can
be
a
lot
of
changes
and
I
don't
want
it
to
like
slow
our
slow,
our
progress.
So
I'm
not
gonna,
I'm
just
going
to
delete
this,
but
essentially
what
happens.
A
A
Okay,
so
then,
once
and
the
reason
that
you
want
to
stay
up
to
date,
all
the
time
is
to
avoid
merge
conflicts
and
so
merge
conflict
is
going
to
happen
when
something
locally
that
you
change
is
different
than
the
origin,
the
master
branch
and
then
you're
going
to
have
to
you're
going
to
have
to
go
back
fix.
It
figure
out.
You
know
what
wasn't
up
to
date.
What
is
my
branch
missing
if
you
can
just
stay
on
top
of
it
and
keep
your
branch
up
to
date?
A
A
A
Okay,
so
then,
now
assuming
I
just
did
I
just
updated-
I
think
I
updated
mine
this
morning.
So
it's
I'm
pretty
confident
that
there
aren't
people
aren't
gonna,
go
change
the.
If,
if
anyone
was
gonna
go
change,
the
pages,
I'm
gonna
change,
it
would
be
youtube-
and
I
don't
think
you
have
this
morning,
so
I'm
not
worried
about
updating
it
right
now.
A
So
I'm
just
gonna
skip
that
get
pull
origin
master
step
and
I'm
gonna
move
on
to
what
I
would
do
next
and
I
think
the
best
thing
is
I'm
just
going
to
open
up
like
a
sample,
merge,
request
and
show
you
how
I
would
start
a
merge
request
from
here.
Instead
of
starting
a
merge
request
on
gitlab.com,
so
going
back
to
like
the
way
that
you're
editing,
gitlab.com
project
is
in
branches.
A
So
the
way
that
you
do
that
is
similar
to
this
command.
Before,
where
I
told
I
did
get
checkout,
and
I
told
the
branch
that
I
wanted
to
check
out
too,
the
thing
that's
different
about
this
time
is
the
branch
that
I
want
to
check
out
to
doesn't
exist.
Yet
I
have
to
create
it
so
the
way
that
you
do
the
way
that
I
do
that,
there's
different
ways,
there's
different
commands
that
you
can
use
the
way
I
do.
A
A
So
in
this
branch
that
I
was
working
on,
I
was
documenting
edcast
support
workflows,
and
so
I
named
the
branch
document
edcast
support,
similar
to
a
commit
when
you
want
to.
I
think
I
do
this
too.
At
gitlab,
I
think
we
get
lazy
with
commits,
and
we
just
like
update,
update
and
like
commits,
are
actually
supposed
to
tell
you
what
changes
are
being
happened
so
or
are
being
you
know
proposed,
so
that
you
can
go
back
and
say
like.
A
A
A
So
I
do
dash
b
and
then
I
name
the
branch
and
I'm
doing
it
test
dash
branch
and
then
I
hit
enter,
and
so
now
it
tells
me
that
I've
switched
to
a
new
branch
and
it's
called
test
branch
and
I
can
do
git
status.
If
I
want
to
to
confirm
that
I'm
on
the
branch
test
branch
there's
nothing
to
commit,
which
means
I
haven't
made
any
changes
yet
on
this
branch.
The
working
tree
is
clean,
so
I'll
show
you
what
happens
what
I
can
do
to
like
change
this
status?
A
Okay,
so
I've
opened
up
a
new
branch.
This
is
this
this.
What
I
just
did
right.
There
is
essentially
the
same
thing
you
do
on
gitlab.com
when
you
click
the
button
that
says,
create
merge
request
when
you
go
to
create
like
open
a
new
merge
request
from
the
gitlab.com
ui.
You
are
creating
a
new
branch
and
I
think
it
just
names
the
I
think
it
just
names
the
branch
by
number-
I'm
not
sure
I
so
rarely
use
it.
I'm
not
sure
if
you
can
change
the
name
of
your
branch
on
gitlab.com
yeah.
A
Okay,
so
then
now
so,
if
you
were
on
gitlab.com
and
you
clicked
create
merge
request,
you
would
then
navigate
to
the
files
that
you
wanted
to
change.
So
that's
exactly
what
I'm
going
to
do
locally.
So
I'm
going
to
open
up
my
text,
editor,
which
I
use
sublime
and
I'm
going
to
go,
find
the
file
that
I
want
to
change
in
this
merge
request.
A
So
I
go
file
open
and
then
you
have
to
navigate
to
the
right
file
in
the
www.getlab.com
project,
which
can
be
a
little
bit
of
a
pain
because
it's
a
little
bit
annoying,
but
you
go
to
gitlab.com
www.getlab.com,
which
is
thegitlab.com
project
and
you
go
to
sites,
I'm
just
sorry
it
like
you
know
it
remembers
where
I
am,
and
I
want
to
show
you
exactly
how
you
get
there.
So
you
go
to
sites
handbook,
source
and
then
handbook
again
and
then
from
here
is
where
all
of
the
groups
across
the
gitlab
organization
are.
A
A
So
I
don't
know
like
this
is
still
all
over
there.
I
think
these
are
empty.
I
think
they
haven't
deleted
these,
so
I
don't
know
why,
if
you
ever
want
to
edit
the
blog,
that's
where
the
blog
is,
and
then
this
marketing
page
is
where,
like
the,
I
think
this
is
where
the
culture
page
is,
it
is,
which
is.
This
is
annoying
and
I
actually
think
josh.
I
saw
a
note
from
sid
from
some
conversation
with
you
about
wanting
to
move
that
culture
page
over
to
the
handbook.
A
A
C
A
Yeah,
so
if
you
ever
are
updating
one
of
those
pages,
it's
in
this
part
this
company
and
then
it's
in
this
like
marketing
folder
scroll
back
up,
but
I'm
gonna
for
this
purpose.
I'm
just
gonna
say
that
we're
like
you
know,
I'm
gonna
mock
edit,
one
of
our
own
pages
in
the
handbook,
so
handbook,
source
or
sorry
sites,
handbook,
source
handbook
and
then
people
group
and
then
learning
and
development.
A
A
A
A
I've
made
my
edit,
you
know
whatever,
if
you're
opening
new
pages,
if
you
are
changing
a
lot
of
content,
whatever
you're
doing
you
do.
All
of
that
sublime
is
nice,
because
when
it
has
this
little
gray
dot
up
here,
it
means
there's
something
that
you've
changed
on
this
page
that
you
haven't
saved.
Yet
so
that's
like
a
good
catch.
A
So
then,
once
I
am
done-
and
I
would
do
this
multiple
times
as
I'm
working
but
once
I've
made
it
some
single
change
that
I'm
ready
to
save
and
commit,
I
save
the
file
and
then
I
come
back
to
my
terminal
and
if
I
do
get
status
check
right
now,
it's
going
to
tell
me
that
I'm
still
on
this
branch,
but
there's
some
changes
that
are
not
staged
yet
for
a
commit.
So
it's
telling
me
I've
changed
this
file,
but
I
haven't
committed
that
change
yet.
A
So
the
way
that
I
do
this
in
the
terminal
is
with
two
different
commands,
so
the
first
I
do
is
git,
add
dash
dash
all
and
that's
going
to
go
to
my
branch.
It's
going
to
pick
up
all
of
the
changes
and
it's
going
to
add
them
to
like
this
queue
to
get
them
ready
to
commit,
and
then
I
do
a
command
to
commit
the
changes.
So
I
do
get
commit
am,
and
then
I
name
my
change.
A
A
A
So
I
have
gotten
into
the
habit
of
trying
to
make
the
name
representative
of
what
I
want
the
mr
to
be
named,
but
you
can
always
change
that
when
you
get
to
gitlab.com
it's
just
like
saving
you
a
step.
If
you
make
this
first
commit
message
pretty
clear,
so
I
would
keep
going
keep
adding
changes,
commit,
save
save
the
file.
Git,
add
all
git
commit
am
name
my
commit,
keep
going,
keep
going
until
I'm
ready
to
push
it
to
gitlab.com
and
that
will
open
a
merge
request
on
gitlab.com.
A
So
I'm
going
to
check
git
status,
one
more
time
to
remind
myself
of
the
name
of
the
branch
and
now
similar
to
how
we
did
a
git
pull
command.
Now,
I'm
going
to
get
push,
which
is
I'm
pushing
something
up
to
gitlab.com,
so
I
would
do
git
push
origin
and
then
the
name
of
my
branch
and
if
I
hit
enter
on
this,
it
will
push
my
changes
up
to
gitlab.com
in
a
new
merge
request.