►
From YouTube: TT120: GitLab Workshop 1
Description
This is a Tanuki Tech session on 2/1/2021.
For more on Tanuki Tech, see here: https://about.gitlab.com/handbook/marketing/revenue-marketing/sdr/tanuki-tech/
For more on the speaker, see here: https://www.linkedin.com/in/christopher-wang-0835b226/
A
All
right
welcome
to
get
lab
workshop,
one
whitney.
How
are
you
doing
today.
A
I'm
doing
great
and
I'm
excited
about
this
class
that
we
have
and
the
reason
why
is
because
I
feel
like
a
lot
of
the
time
when
we're
doing
training
and
onboarding
it's
more
like
listen,
this
video!
Listen!
This
guy
talk,
listen
to
this
more
stuff,
read
this
stuff,
but
this
class
is
a
little
bit
different.
What
we
are
actually
doing
here
today
is
that
we
are
going
to
use
gitlab
ourself,
so
you
are
going
to
be
using
git
lab
to
update
a
website.
B
A
And
that's
not
something
where
it's
like
hey.
You
need
to
know
a
lot
of
different
technical
stuff.
I
just
went
through
this
with
brady
and
we
didn't
run
into
any
snags
at
all.
So
once
again,
the
goal
of
this
session
is
to
become
more
confident
in
discussing
gitlab
by
seeing
it
in
action
a
lot
of
times
it's
just
sort
of
like
we
sort
of
know
about
this
stuff,
but
then,
once
we
actually
do
it
for
ourselves,
then
we
can
more
authentically
articulate
yeah.
It's
really
easy,
like
I've
done
it
myself.
A
It
took
me
five
minutes
to
do
this
and
to
be
able
to
speak
from
a
place
of
authenticity.
So
that's
our
goal
for
today.
A
So
the
agenda
for
how
we're
going
to
do
this
is
we're
going
to
do
a
brief
demo
of
git
lab
talk
about
how
our
customers
use
gitlab
and
then
the
main
part
of
today's
session
is
to
do
the
workshop
itself
and
that'll
take
maybe
around
20
minutes.
So
how
does
that
sound
to
you.
A
Okay,
yeah,
okay,
cool
all
right;
okay,
so
let's
talk
real
briefly
about
our
customers.
Really,
when
we're
talking
about
gitlab,
there's
really
five
things
that
our
customers
are
using
gitlab
for
so
one
of
that
is
workflow
management.
We
have
this
really
complicated
project.
We
are
planning
some
we're
planning
to
like
do
some
really
really
complicated
thing
that
has
to
do
with
400
different
people
right
so
having
some
sort
of
process
management
tool
to
break
that
down
into
the
make
sense
of
it
all.
That's
what
we're
talking
about
here.
A
Another
thing
that
our
customers
do
is
they
use
git
lab
as
an
interactive
coding
platform,
so
they
can
code
on
the
internet
and,
as
we
talked
about
before,
it's
not
good
enough
for
people
to
just
code
stuff.
We
need
to
have
some
way
in
which
people
can
review
each
other's
work.
The
reason
why
is
because
we're
an
open
source
project?
A
A
You
combine
these
two
together
and
now
we've
saved
time
money,
energy-
and
this
is
how
we
allow
organizations
to
become
more
efficient,
so
yeah,
and
then
let's
actually
do
a
demo
of
this
real,
quick
and
feel
free
to
chime
in
here
and
if
there's
anything
else
that
you
want
to
see
more,
then
just
let
me
know,
but
I'm
just
going
to
go
through
this
real
quick,
so
this
is
get
lab
source
code.
A
Ultimately,
we
are
a
tool
for
storing
code,
so
just
like
how
you
can
have
a
folder
in
google
drive
and
you
put
like
word
docs
and
excel
spreadsheets
git
lab
is
basically
a
repository
in
which
we
can
keep
track
of
all
of
your
code,
so
over
here
we
have
many
different
files.
I
can
take
a
look
at
this
particular
file
over
here.
It's
got
a
bunch
of
text
on
here.
Gitlab
is
the
tool
that
stores
all
of
these
code
all
of
this
code.
A
Another
thing
that
we
do
is
we
give
you
that
history,
that's
really
important.
So
a
lot
of
times
when
you're
an
engineer,
you're
trying
to
find
out
hey
the
website
was
working
great
and
then
it
broke
sometime
three
days
ago.
Well,
let
me
go
back
into
history
and
see.
Were
there
any
changes
made
three
days
ago.
Oh,
there
were,
let's
go
see
what
they
were.
This
actually
corresponds
with
exactly
what
the
customer
is
seeing.
So
maybe
we
need
to
go.
That's
the
that's
like
the
smoking
gun
right
so
over
here.
A
I
just
took
a
look
at
one
file.
Here's
all
of
the
people
that
made
changes
to
this
file.
If
I
scroll
in,
I
can
see
what
exactly
the
change
was.
They
took
out
all
of
these
remove
these
red
lines
edited
in
the
green
line.
That's
basically
what
we're
talking
about
here
so
storing
the
code.
The
other
thing
is
workflow
management.
A
Let's
just
actually
take
a
look
at
this.
This
view
right
here,
so
here's
all
the
individual
items
for
our
engineers
to
take
a
look
at
it
could
be
something
small
like
hey,
go,
make
some
graph
or
chart
go,
make
this
front
page
a
little
bit
nicer
and
then
so
what
inevitably
happens
is
that
someone
creates
all
of
the
issues
and
then
this
is
basically
like
go
update.
Our
website
go
change
this
and
then,
once
all
these
issues
are
done,
our
project
is
done.
A
So
when
I
was
an
engineer
at
the
start
of
a
new
project,
I
would
get
assigned
maybe
20
issues
and
if
I
got
done
with
them
on
time,
that's
when
I
was
a
happy
engineer.
If
I
didn't
get
them
done
on
time,
then
that's
when
I
was
really
stressed
out-
and
I
was
working
on
saturdays,
so
basically
fulfilling
and
resolving
all
these
issues
is
basically
what
engineers
do.
A
The
next
thing
that
they
do
is
they
need
to
go
and
have
you
put?
Did
you
use
the
interactive
web
editor
for
when
you're
onboarding
and
making
a
change
to
the
handbook
page.
A
B
A
Okay,
awesome,
so
anyone
can
go
make
changes.
The
next
thing
that's
important
is
through
a
peer
review
process.
Once
again,
we
need
to
have
some
sort
of
gate
for
people
to
review
code.
So
here
is
what
we
call
a
merge
request.
What
a
merge
request
is
is
that
it
is
a
request
to
change
the
code
right
because
we
don't
accept
it
from
everyone.
It
has
to
get
approved
by
someone.
So
some
developer
name.
A
Came
in
made
a
big
change.
You
can
see
all
the
changes
here
or
adding
in
these
green
lines,
removing
the
red
text,
and
then
you
can
see
that
people
have
the
right
to
challenge
frederick,
so
people
can
make
different
comments.
People
can
say:
hey.
Have
you
thought
about
doing
it?
This
other
way.
Have
you
thought
about,
like
maybe
streamlining
it
like?
Would
you
mind
prefixing
this
right?
A
A
So
that's
almost
the
end
of
the
tour
of
get
lab.
The
only
other
thing
I
want
to
talk
about
is
all
the
automation
that
happens.
This
saves
our
engineers,
hundreds
of
hours
of
time
and
energy,
and
so
all
of
this
stuff
over
here
is
something
that
might
take
someone
20
minutes
to
do.
Some
of
these
things
might
take
someone
100
hours
to
do,
but
when
you
combine
all
of
this
stuff
happening
in
a
completely
automated
fashion,
this
is
going
to
greatly
increase
the
speed
in
which
our
development
teams
can
work.
A
B
A
Yeah,
exactly
and
basically,
what
we're
talking
about
here
is
making
sure
that
our
code
still
works
and
that
it's
secure,
that's
all
all
right
awesome
can
I
help
clarify
anything
or
else
we're
gonna
jump
right
into
the
interactive
demo.
A
A
A
This
is
this
is
the
project
and
if
I
go
over
here,
sim
farm
get
lab
docusaurus.
Then
this
is
actually
the
website
that
I
created
for
this.
So
it's
yup,
it's
a
simple
website
for
children's
stories.
If
I
go
to
this
blog
section,
then
you
can
see
that
brady
made
this
mystery.
B
A
I
wrote
a
story
about
hiking
and
we're
going
to
write
our
very
own
story.
So
how
do
you
are
you?
What
do
you
think.
A
That's
awesome
all
right,
so
I'm
going
to
give
you
a
link
to
this
real,
quick
and
the
link
is
going
to
be
here,
go
to
gitlab.com,
simpfarm
docusource
and
then
after
that.
Let
me
know
when
you
are
done.
B
A
All
right
awesome,
cool.
Well,
you
are
now
a
proud
member
of
our
repository,
and
so
the
first
thing
that
we're
going
to
do
is
we're
going
to
pretend
like
we
are
developers
on
this
team
right
and
in
this
story.
A
Basically,
if
marketing
is
saying
hey,
we
want
to
have
more
stories
in
our
website,
so
we
need
to
now
code
out
these
new
stories.
We
take
a
look
at
some
of
the
stories
that
we
have
over
here.
B
B
B
A
B
A
B
A
Nice
semi-colon
use
you
can
tell
like
that's
advanced,
very
cool,
so
I
have
my
issue
assigned.
You:
have
your
issue
assigned
so
now.
What
we're
going
to
do
is
now
that
we
know
what
to
write
about.
Let's
go
fulfill
this
issue
right,
we're
developers
and
we
get
paid
for
solving
these
issues.
So,
let's
solve
them.
A
B
B
B
B
B
B
A
B
A
B
A
B
B
B
B
B
A
All
right
awesome
so
before
we
hit
save
just
quick
check,
we
should
have
this
copied
and
pasted
the
only
two
fields
that
should
be
updated,
or
these
two,
the.
B
B
B
A
All
right,
great
okay,
so
now
what
we're
going
to
do
is
we
have
to
save
this
and
the
way
to
do
it
is
we
do
this
thing
called
a
commit?
What
a
commit
is
basically
just
saving
our
stuff,
so
I'm
going
to
hit
the
blue
commit
button
and
we
need
to
have
what
we
call
commit
message
so
once
again,
it's
just
sort
of
like
if
there
are
100
people
hitting
save,
because
our
project
is
a
global
project
and
we
have
a
thousand
people
working
on
it.
A
A
A
All
right
awesome,
so
now
we
are
creating
a
request
to
change
the
code
right.
So
this
is
a
request
and
someone
else
has
to
edit
it.
So
that's
why
you
need
to
have
a
title,
a
description
and
then
you
need
to
assign
it
to
someone.
So
I'm
going
to
sign
this
to
you
because
you're
my
colleague
and
for
my
description,
I'm
going
to
say
this
fulfills
request
from
product
marketing
about
creating
a
story
about
monsters.
A
A
All
right
awesome,
great
story
about
vegetables.
So
now
I'm
I'm
reviewing
your
merge
request,
and
so,
if
I
were
a
developer
in
this
situation,
what
I'm
going
to
do
is
I
want
to
see
what
the
changes
are
right.
A
Vegetables
are
awesome
by
whitney
person,
hey
kids,
have
you
heard
of
broccoli?
How
about
cauliflower
bell
peppers
ringing?
A
bell?
Kids,
let
me
tell
you:
vegetables
are
awesome,
they
are
totally
dope
and
all
the
kids
these
days
are
really
loving,
showing
off
their
new
vegetable
eating
skills
to
all
the
other
fifth
graders
on
tick
tock.
A
B
A
And
what
I
want
to
do
now
is:
I
have
to
approve
it
right
and
then
I'm
going
to
merge
this.
So
why
don't
you
go
if
you
like
my
story,
then
why
don't
you
do
something
similar
to
this
merge
request
this
the
ad
story
about
monsters.
B
Okay,
so
I'm
gonna
look
at
your
changes.
There
were
once
many
monsters
under
the
bed
and
the
children
of
the
house
gave
them
names.
As
the
children
grew
older.
They
grew
wiser
and
realized
that
the
monsters
had
needs
too.
The
children
made
friends
with
the
monsters
and
eventually
set
the
monsters
to
college.
These
monsters
went
to
monsters
university.
He
began
that's
good
monsters
in
closet,
christopher
wang,
all
right
good
to
go.
B
A
Very
awesome
so
notice
we
didn't
do
any
crazy
technical
stuff,
we're
just
using
the
ui
to
click,
everything
and
notice.
Now
what
gitlab
does
completely
automatically
without
us
doing
anything.
If
I
go
to
this
pipeline
section,
there's
two
pipelines
that
are
running
and
then
let's
take
a
look
at
what's
happening
automatically.
So
if
I
go
to
this
pages
thing,
it's
doing
this
technical
stuff
right.
So
what
this
is
doing
right
now
is
it's
actually
updating
our
website
completely
for
us,
so
saving
us
a
ton
of
time
so
yeah.
A
B
A
A
A
B
A
A
So
now,
let's
talk
about
a
little
bit
about
like
who
does
what
right,
so
the
people
who
determine
all
the
issues
that
are
created.
A
These
are
people
called
product
managers
and
they're
in
charge
of
saying,
like
you
know
what
I
think
our
product
would
be
better
if
it
could
do
this
and
this
so
then,
all
that
stuff
that
the
product
manager
deems
should
be
in
the
next
version
of
our
product.
That's
what
the
engineers
start
working
on
right.
So
he
creates
all
the
issues
the
engineering
manager
then
comes
in
and
says
I
have
five
people
on
my
team.
I
know
that
whitney's
really
been
trying
to
get
into
kubernetes.
A
I
have
this
one
kubernetes
issue,
so
I'm
gonna
give
it
to
whitney
right.
I'm
we're
a
little
bit
understaffed
right
now,
and
I
know
that
sarah
is
really
good
at
user
interface
issues.
So
I'm
going
to
give
all
the
user
interface
issues
to
sarah.
So
first,
a
product
manager
determines
all
the
work,
creates
all
these
issues
for
all
the
work,
the
engineering
manager.
That
knows
the
team.
The
best
assigns
who
does
what
then
the
developers
which
was
us
in
this
example.
They
completed
all
the
issues
they
created,
merge
requests.
A
Then
we
also
reviewed
the
merge
request
and
then
really
the
next
two
sort
of
depends
on
the
organization,
but
the
two
people
that
are
really
in
charge
of
making
sure
that
everything's
up
and
running
is
operations
and
site
reliability.
Engineers,
if
you
ever
see
someone
with
the
title
site,
reliability,
engineer,
think
netflix,
right
or
think
amazon.
If
that
website
ever
went
down
for
a
minute
or
for
five
minutes,
then
they'd
lose
a
lot
of
money
right
so
site.
A
Reliability,
engineers
are
making
sure
that
their
website's
really
reliable
and
it's
fast
and
then
obviously,
security
verifies.
That
platforms
are
secure.
A
B
A
B
Basic,
it
doesn't
seem
like
I
need
to
know
the
ins
and
outs.
Of
course,
it's
important
to
know
those
as
well,
but
for
the
purposes
of
our
exercise
it
was
really
straightforward.
A
Yeah
and
the
beauty
of
having
a
good
technology
solution
is
that
it
should
be
simple
if
we
can
make
something,
that's
really
really
complicated
simple,
then
that's
when
we
actually
add
value
to
our
customers.
There's
a
lot
of
tools
out
there
that
it's
like
they
can
do
a
lot,
but
it
takes
four
to
six
months
to
get
up
and
running
if
you
have
two
people
working
on
it
all
the
time,
so
it's
just
like
too
complicated
yeah.
So
I
I
love
that
idea
yeah.
A
So,
let's
just
let's
just
what's
what's
the
take-home
point,
it's
exactly
like
you
just
said
right.
A
What
we
just
did
most
businesses
have
between
five
to
ten
different
tools
to
do
all
of
that,
so
they'll
have
one
tool
for
scm:
they'll
have
one
tool
for
they'll
prob
for
maybe
like
for
tickets,
they'll
have
one
tool
for
ci,
maybe
another
tool
for
cd,
and
then
you
have
to
integrate
everything
together.
The
great
thing
with
git
lab
is
that,
as
opposed
to
having
to
buy
six
things,
evaluate
six
things,
set
up
six
things
and
then
integrate
six
things
together.
A
If
you
just
get
gitlab
all
of
a
sudden,
you
just
save
a
lot
of
time
in
a
lot
of
cases.
You've
also
saved
some
money
too,
and
we're
really
unique
in
the
fact
that
we
do
this.
There
are
other
businesses
that
are
trying
to
do
this,
but
they're
really
playing
catch-up
right.
Now
we
are
the
best
all-in-one
solution
in
the
market
and
ultimately,
what
that
allows
people
to
do
is
to
make
engineering
more
efficient.
A
How
do
we
do
that?
One
by
automating
manual
tasks,
two
by
having
better
crossteam
collaboration?
So
just
imagine
a
scenario
where
one
developer
team
was
on
github.
Another
developer
team
was
on
jenkins.
Another
developer
team
was
in
charge
of
something
else
that
just
creates
a
lot
of
opportunities
for
miscommunication,
but
if
everyone's
on
gitlab,
then
everyone
can
communicate
on
gitlab
and
then
the
last
thing
is,
if
you
have
one
solution,
as
opposed
to
maybe
510,
then
you're,
probably
at
that
point,
saving
in
license
costs
as
well.
A
So
this
is
why
we're
unique-
and
this
is
how
we
drive
value
for
our
customers-
all
right,
awesome,
that's
today's
class
thanks
for
attending,
and
I
can
stick
around
to
help
clarify
anything,
but
otherwise
thank
you
for
attending
today's
session.
B
Thank
you.
No,
I
think
I've
got
everything
cleared
up
like
I
said
it
was
super
straightforward,
but
yeah.
Thank
you
for
hosting
it.
It
was
good
to
have
like
a
walk
through.
Finally,
rather
than
having
to
figure
it
out
like
with
the
team
space.