►
Description
Team members of the Digital Experience who don't typically work with code learn how to create a branch, make an edit to the handbook, commit a change, push the branch up to GitLab, and finally create a merge request with their change.
A
B
A
And
I
have
in
the
agenda
I'm
highlighting
like
for
for
me
what
that
command
is
so?
Oh
there
you
go
so
your
users
so
do
an
ls
which
will
list
all
the
directories
in
that
there
we
go.
Where
do
you
have
your
oh
get
lab
repos
there
you
go
so
do
a
cd
space,
get
lab,
repos
and
that'll
open
that
directory.
A
A
That
did
nothing
oh
just
type,
the
the
whole
repo
name
or
cut
and
paste
it
that
dub
dub
dub
daft,
get
lab
dash
calm,
it's
a
little
bit
below
nope,
not
there
that
terminal
you'll
have
to
delete
it.
One
by
one
yeah
go
up
three
lines
and
you'll
see
the
dub
dub
dub
dash
get
lab
dash,
calm,
yeah
that
one
that's.
B
A
A
Make
your
screen
a
little
s
or
bring
it
up
or
you're
there.
Oh
yeah
yeah
you're
totally
there,
so
it
sees
macbook
pro
colon
and
you
see
the
dub
dub
dub.
That
means
that's
the
director
you're
in
and
if
you
do
an
ls
it'll
list,
all
the
files
in
it
and
see
that
gem
lock,
readme
config
a
whole
bunch
of
real
kodi
files.
A
Okay,
so
yeah
we're
on
step
b
did
too
so
now
we're
gonna
check
out
the
master
branch.
We're
gonna
fetch
the
latest
version.
I
call
it
the
cloud
but
well
I
don't
really
call
it
the
cloud,
but
that's
what
it
is
like
we're.
Gonna
pull
the
latest
version
of
the
website
from
the
cloud
which
is
git
lab
and
we're
gonna
update
our
local
master
branch
to
be
exactly
like
the
cloud
version,
so
we're
all
up
to
date,
because
our
master
branch
is
updated
like
400
times
a
day.
A
So
if
you
open
a
branch
and
don't
touch
it
for
a
couple
weeks,
your
branch
is
going
to
be
really
super
out
of
date.
So
this
yeah
yeah,
we
gotta
do
that.
So
we're
gonna
do
the
first
command
a
yeah
and
you
do
these
sequentially
from
the
root
so
get
checkout
master
and
you'll
see
you
switch
your
branch
to
master
and
it'll.
Tell
you
how
far
behind
your
branches,
I'm
only
82
commits
I'm
kind
of
interested
to
see
how
far
your
your
master
branches
are
behind.
A
A
Awesome,
so
if
you
do
a
get
status,
is
my
favorite
git
command
in
the
world
status
yeah
space
yeah-
and
this
tells
you
what
the
status
is
where
you're
at
what
you're
doing
what
branch
you're
on
all
the
things?
I
do
this
all
the
time
it's
just
like
a
mental
check
of
where
I'm
at
and
what
I'm
doing
so.
A
You
have
a
change
to
your
team
member
file
that
has
not
been
saved
and
you
are
on
the
branch
jh
dash,
adding
myself
gitlab
org
chart
so
go
ahead
and
copy
that
whole
branch
name,
the
jh
dash
this
one
yeah
yeah
yeah
just
copy
that
to
your
clipboard
and
we're
gonna.
Add
your
change
so
get
space,
add
space,
dot
and
that's
gonna.
A
A
A
A
A
All
the
windows
cool
now
we're
gonna
do
a
get
fetch
and
this
is
gonna,
get
everything
up
from
get
lab.
Yep
and
that's
gonna
take
a
while,
because
our
repo
is
super
big
so
and
I'm
actually,
everyone
should
do
the
get
fetch
right
now,
because
it's
gonna
take
a
minute,
get
the
loading.
Now
I
get
to
hang
out
and
talk
for
a
while.
C
A
A
A
A
A
C
C
A
A
This
is
the
the
important
one
and
we
have
it
split
into
two:
the
marketing
directory,
this
houses,
all
of
the
files
for
building
the
marketing
site
and
then
handbook-
and
this
is
all
the
stuff
for
making
the
handbook-
and
in
here
we've
got
source
and
then
another
handbook
directory,
and
so
that's
the
spot.
We
gotta
get
to
sites
handbook
source
handbook.
A
Two
handbook
pages
that
you're
all
probably
interested
in
are
the
our
handbook,
page
digital
experience,
handbook
page
and
the
netlify
cms,
one
pick,
whichever
one
you
feel
like
making
a
change
to,
and
then
you
have
to
navigate
through
the
folder
structure
down
to
those
pages,
and
this
folder
structure
is
what
creates
the
url
structure.
So
if
you.
B
A
A
handbook
page,
you
want
to
make
an
edit
to
look
at
that
url
structure
and
that's
going
to
be
the
files
that
you
have
to
navigate
to
to
get
there,
because
our
our
handbook's
really
big,
there's
tons
of
tons
of
sections.
So
I'm
down
into
the
marketing
netlify
cms
and
then
here's
my
index
markdown
file.
C
A
A
There
we
go
digital
experience,
we
have
a
lot
of
handbook
pages
in
our
section,
so
any
of
these
ones
are,
you
know,
grabs,
go
and
edit
and
then
that
index.html.md
at
the
bottom
of
the
directory.
That's
that's
our
root!
Yeah
open
that
guy,
which
one
the
one
up,
yeah
that
one
you
just
click
on
it
yay
there
you
go
mark
down.
That
is
that's
our
handbook
page
go
ahead
and
and
make
a
change
to
it.
A
A
A
E
A
A
B
A
A
Yeah,
that's
it
it's!
Okay,
the
secret
silent
command,
that's
stuff
in
the
background,
but
it
doesn't
really
tell
you
what
it's
doing
and
then
c
git
commit
dash
m
and
your
super
cool
commit
message
and
it
could
be
whatever
you
want.
But
you
want
these
commit
messages
generally
to
say
what
changed
and
why
it
changed
and
there's
lots
of
philosophical
conversation
about
what
should
be
in
your
commit
message
and
how
it
should
be
organized
and
all
of
that
but
basic
says.
Yeah.
D
F
B
C
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
Nope,
okay-
and
I
like
writing
these,
mr
descriptions
to
myself
like
if
myself
was
coming
back
to
in
the
future,
and
I
had
no
idea
what
I
was
doing
here
like
why
this
is
author
checklist.
You
don't
have
to
do
that
right
now,
but
you
kind
of
as
this
mr
goes
through
the
process
you're,
you
click
those
boxes.
A
A
B
A
Here's
where
you
could-
and
you
know,
add
all
our
fancy
labels
if
you're
working
on
something
related
to
digital
experience.
I
don't,
I
wouldn't
add
any
labels
right
now,
because
I'm
not
sure
but
yeah
to
sign
yourself
done
the
title
description
here.
You
can
see
your
commit.
Let's
submit
that
merge,
request.
C
A
A
B
A
And
I'm
going
to
show
you
guys
something
real,
quick
and
then
I
gotta
hop
off
to
another
meeting,
but
so
that
is
really
important.
That's
the
process
of
creating
a
merge
request,
getting
your
changes
up
there
and
you
guys
should
do
that
a
few
times
to
really
get
the
hang
of
like
what
this
process
is
and
what's
happening
in
the
background.
A
A
Easy
way
it's
really
cool,
but
you
guys
shouldn't
do
this
way
until
you've
at
least
done
one,
mr,
the
other
way,
but
gitlab's
built
tools
to
pretty
much
enable
that
so
there's
one
called
on
all
our
handbook
pages.
We
have
you'll
see
at
the
sidebar
these
links
up
here
view
source
is
going
to
take
you
to
exactly
where
this
page
exists
in
the
repo,
so
sites
handbook
source.
A
Whatever
you
can
see
the
last
person
that's
made
a
change
to
this
page,
and
here
is
the
page
and
you've
got
some
other
options
here,
but
we'll
go
over
that
later,
there'll
be
a
link
to
open
this
page
in
the
web
ide.
So
this
is
the
web
version
of
sublime
or
visual
studio.
It's
a
code
editor
in
the
web
that
allows
you
here's
our
folder
structure,
here's
the
page.
I
could
come
in
here
and
say
whoa
and
I
can
commit
it
and
that's
gonna
make
a
commit.