►
Description
This video walks you through the steps of migrating a GlDeprecatedButton to GlButton. It also walks through fixing multiple types of jobs and test failures, as well as when to ask for help.
- UX OKR Migration Epic: https://gitlab.com/groups/gitlab-com/-/epics/758
- GlDeprecatedButton Epic: https://gitlab.com/groups/gitlab-org/-/epics/3459
More resources for getting help: https://gitlab.com/groups/gitlab-com/-/epics/758#getting-help
A
Okay,
today,
I'm
going
to
walk
through
migrating
a
button
from
gitlab
deprecated
button
to
our
new
get
lab
button
button.
So
I'm
going
to
start
just
from
the
main
epic
that
we
have
for
q3,
which
is
to
make
gitlab
development
pajamas
first
and
first.
I
just
want
to
point
out
that
there
is
a
getting
help
section
here.
So
if
you
do
get
stuck
along
the
way,
there's
multiple
variants
for
different
issues
that
we
have,
and
you
just
don't
know
what
to
do
next,
like
just
reach
out
for
help,
there's
lots
of
different
options
here.
A
A
So
there
is
a
lot
of
documentation
here
in
this
epic
in
order
to
help
you
along
the
way,
make
sure
to
read
through
this
epic
and
have
kind
of
a
basic
understanding
of
what's
going
on,
but
I'll
walk
you
through
all
of
this
anyway.
So
then,
hopefully,
it'll
feel
more
familiar.
The
first
time
you
are
working
on
one.
So
once
you
go
through
you'll
see
that
there's
a
number
of
issues,
163,
there's
still
104
open.
A
So
a
number
of
people
have
already
picked
up
the
issues
which
is
great
you'll
just
want
to
scroll
down
until
you
find
one
that's
available,
and
you
can
read
the
file
names
here
that
are
going
to
be
migrated
and
potentially
pick
one
up
that
is
related
to
your
area
of
the
product.
You
may
already
have
it
set
up
in
jdk
which
will
make
it
easier
to
test.
A
So
I
went
ahead
and
chose
this
issue
here
and
I
assigned
it
to
myself
immediately.
I
the
first
thing
I
do
is
just
look
at
the
file
name,
so
I
can
see
from
this
file
that
it
is
related
to
the
admin
area.
It's
related
to
users
in
some
way,
and
then
this
last
part
here
tells
me
that
all
right,
this
is
about
deleting
a
user
and
it's
referencing
a
modal.
A
You
can
also
hover
over
the
file
name
and
it'll
show
the
full
path,
and
you
can
make
sure
that
that
exactly
matches
what
you're
working
on,
which
looks
like
this
one
does
so
that's
great
searching
for
deprecated
in
the
file
will
show
you
all
the
instances
of
where
deprecated
is
currently
being
used,
and
the
first
step
of
this
is
really
to
replace
the
gitlab
deprecated
button
with
gitlab
button.
But
before
I
start
doing
that,
I
want
to
make
sure
I
can
find
these
within
the
actual
application.
A
So
looking
at
the
what
needs
to
be
migrated
here,
I
can
see
that
there
are
three
instances
of
buttons
here
and
the
reason
I
know
that
is
because
there
are
three
opening
tags,
one
two
three
and
then
there
are
also
three
closing
tags.
So
three
buttons
within
this
file
need
to
be
migrated
to
the
gitlab
button.
A
A
So,
on
the
left
hand,
side,
here's
users
and
then
I
can
see
a
list
of
users
within
my
instance.
So
I
want
to
find
out
where
I
would
delete
a
user,
and
I
want
a
modal
to
pop
up
so
potentially
within
this,
and
I
can
see
that
there's
multiple
different
options
here,
but
we
want
delete
user.
So
if
I
click
that-
and
I
see
a
modal
and
it
has
three
buttons-
so
that
looks
pretty
promising
at
this
point.
A
So
now
I'm
going
to
go
to
my
terminal
and
I
need
to
check
out
a
branch
in
order
to
make
these
changes
and
I'm
in
the
get
lab
folder.
You
can
see
that
here
you
make
your
changes
in
the
gitlab
folder
you
run
git.
Are
you
on
git
lab
development
kit
in
the
gitlab
development
kit?
Folder?
So
that's
where
you
would
run
gdk
so
checking
out
my
branch.
A
Great
now
I
can
see
that
I
am
within
this
branch
and
I
can
start
making
my
changes
so
I'll
go
back
to
my
code
editor
and
follow
the
steps
within
the
issue.
So
it
says
using
the
migration
steps
or
by
manually
editing
the
files
you
want
to
replace
instances
of
gitlab
deprecated
button
with
getlab
button.
So
I
don't
want
to
worry
about
the
migration
script.
Maybe
I
don't
know
what
that
is,
and
it
doesn't
look
like
there's
much
to
change
here.
A
A
A
And
I'm
going
to
save
just
to
keep
my
progress,
then
the
next
step
says:
convert
each
variant
attribute
to
the
new
very
category
combination
using
the
very
mapping
guide.
The
very
mapping
guide
is
just
right
below
within
the
issue.
So
if
I
take
a
look
at
the
first
button
I
have
here,
I
see
that
the
variant
equals
secondary
and
if
I
look
here
variant
secondary,
says,
remove
attributes.
So
I
can
just
remove
this
completely.
A
It
doesn't
tell
me
to
add
anything
else,
so
I'm
just
going
to
do
that
and
then
the
second
one
it
looks
like
variant
equals
warning
so
for
variant
equals
warning.
I
want
very
warning
and
category
primary,
so
I'm
going
to
take
category
primary,
just
copy
paste
and
then
let's
see
this
last
one
is
variant
danger.
So
look
at
the
mapping.
A
A
I'll
reopen
the
modal,
and
I
want
to
look
to
make
sure
that
these
buttons
have
actually
changed.
I'm
going
to
type
in
this
name,
so
they
don't
appear
disabled
anymore,
and
I
can
see
that
it
does
look
like
the
styling
has
changed
slightly,
so
the
buttons
the
new
buttons
aren't
drastically
different
from
our
old
buttons.
They
have
improved
contrast
for
accessibility,
so
one
easy
way
to
tell
that
the
buttons
have
updated
is
when
you
hover.
They
have
this
darker
border
around
the
buns.
A
You
can
see
that
on
each
of
these
another
way
to
know
is
to
inspect
the
element
and
ensure
that
they
are
32
pixels
tall,
our
old
buns,
many
of
them
that
are
in
production
are
34
pixels.
So
if
you
see
something
that
is
still
34
pixels,
then
something
is
probably
off
so
from
here.
I
can
see
that
all
three
of
these
buttons
have
been
updated.
They
look
as
I
expect
them
to,
and
they
do
look
to
be
this,
the
correct
colors.
So
I'm
going
to
go
ahead
and
take
a
screenshot
of
these
updated
buttons.
A
A
A
A
A
A
A
And
after
preview
it
just
make
sure
it
looks
all
right
and
you
can
see
that
you
may
be
able
to
see
it's
kind
of
small,
but
the
cancel
button
in
particular
has
a
darker
border,
so
I
can
tell
which
one's
before
and
after
a
lot
of
these
steps
in
in
the
march
request,
template
are
unrelated
to
this
work.
So,
like
all
these
security
things,
you
can
just
put
little.
A
A
A
That's
the
issue
I
was
working
on
and
it
automatically
has
that
because
I
overhearing
name
my
branch
with
that.
So
it
just
automatically
adds
it
into
the
merge
request,
description
and
we'll
close
the
issue
once
the
merge
request
is
merged.
So
from
here
I'm
going
to
go
ahead
and
submit
my
merge
request.
A
A
A
Okay,
I'm
back
and
my
pipeline
is
finished
and
I
can
see
that's
failed,
which
is
okay,
I'm
just
going
to
go
and
look
at
what
jobs
have
failed
and
try
and
figure
out
why
they're
failing
so
go
ahead
and
click
on
this
first
job
and
in
order
to
see
why
your
job
is
failing.
You
want
to
look
through
the
job
log,
which
is
all
of
those
texts
in
this
kind
of
black
square.
So
the
error
here
isn't
very
helpful.
A
I
don't
really
know
what's
going
on,
so
I'm
just
going
to
keep
scanning
up
until
I
find
something
that
tells
me
either
what
failed
and
how
to
fix
it
or
just
a
general
failure
notice
and
that
I
can
kind
of
work
from
and
figure
out
what's
going
on.
So
if
I
keep
going
up,
I
do
see
this
here
where
it
says
one
snapshot
failed
from
one
test:
suite
inspect
your
code
changes
or
run
this
command
to
update
them.
So
I'm
going
to
go
ahead
and
just
do
what
they
tell
me
and
run
this
command.
A
So
this
can
take
a
little
bit
of
time
between
like
four
and
five
and
a
half
minutes.
So
while
that's
running,
let's
go
ahead
and
look
at
our
secondary
job
that
failed,
and
this
says
that
job
failed
also
not
very
helpful.
So
I'm
going
to
look
at
this
other
red
text
that
stands
out
to
me
and
it
says,
get
lab
uses
prettier
to
format
all
javascript
code.
A
Please
format!
Each
file
that's
listed
below
or
run
this
command
that
would
update
all
of
them.
So
since
we
only
have
one
file,
it'll
be
a
lot
faster
to
just
run
this
one
command.
So
I'm
going
to
go
ahead
and
pause
this
recording,
while
this
command
finishes
and
then
once
it's
finished,
we
can
run
this
command
together.
A
Okay,
that
command
finished
and
just
as
a
recap,
so
we
were
on
this
first
job
here
and
it
told
me
to
run
this
command.
We
ran
that
command
and
if
I
do
a
git
status,
I
can
see
that
two
files
were
changed
after
running
that
command.
So
then
we
were
going
on
to
our
second
job
that
failed
and
it
was
telling
us
that
prettier
it
formats
the
javascript
code
and
that
we
need
to
run
a
command
for
each
file
that
is
listed
below
and
it
looks
like
there's
only
one.
A
A
A
A
A
A
A
Let's
take
a
look
at
the
second
test,
that's
feeling
now
this
is
a
new
test.
I
wasn't
failing
previously,
so
it
looks
like
it's
telling
me
to
update
the
snapshots
again,
but
that
seems
pretty
weird,
because
we
just
did
that.
So
I
don't
see
why
we
would
need
to
do
that
again.
So
I'm
just
going
to
try
and
figure
out
what
snapshot
it's
complaining
about.
A
A
A
A
All
right,
so
this
is
a
good
example
of
if
you
simply
don't
know
why
something
is
the
way
that
it
is
just
ask
for
help
from
someone
and
then
they'll
be
able
to
answer
and
provide
support
and
then
you'll
get
through
it
a
lot
faster.
So
I'm
gonna
stop,
recording
and
then
come
back
once
I
hear
from
him.
A
Okay,
I'm
back,
and
I
have
heard
from
zach
and
his
reply
was
that
it's
really
rare
that
this
is
happening.
The
snapshot
that
was
deleted
shouldn't
be
deleted
when
you
run
that
command.
It's
weird
that
that
is
occurring-
and
I
also
talked
with
jerick
there's
another
designer
here
at
get
lab
on
the
foundations
team
and
he
was
running
into
the
same
thing
in
his
merch
request.
A
So
what
is
happening
is
that
there's
a
bug
with
this
command
and
we
want
to
solve
that
separately
from
this
merge
request
that
we're
working
on
so
what
I
ended
up
doing
was
just
adding
back
that
snapshot.
So
if
we
go
to
my
commits,
I
added
the
snapshot
back
and
the
way
I
did.
That
was
just
adding
a
new
file
and
I
copy
and
pasted
the
contents.
I
thought
that
would
be
the
easiest
and
fastest
way,
and
then
I
committed
that
change
and
push
it
up
to
my
merge
request.
A
So
the
pipeline
has
ran,
and
you
can
actually
see
that
I
have
another
failure.
So,
by
going,
I
do
see
that
the
the
the
job
that
failed
before
with
from
deleting
that
snapshot
is
now
fixed,
which
is
great.
But
if
I
go
and
look
at
this
job
that
is
failing,
I
can
see
that
it's
failing,
because
I
didn't
capitalize
the
first
letter
of
my
commit
message.
So
this
is
fairly
common.
If
you
forget
it'll
pop
up,
all
you
have
to
do
is
come
to
amend
your
commit
message.
A
You
would
go
back
to
your
terminal.
Do
a
get
commit
double
dash,
amend
and
it'll
pull
up
your
last
commit
and
you
can
make
those
changes
there,
but
that
would
mean
that
I
have
to
run
the
entire
pipeline
again
and
there's
actually
an
easier
way
to
do
that.
So
I'm
going
to
go
ahead
and
show
you
all
what
that
looks
like.
So
I
have
four
commits
here
and
really
I
don't
need
all
four
commits
the
only
one
that
really
matters
is
this
first
one.
A
What
that's
going
to
do
is
that
when
the
merge
request
is
merged,
it's
going
to
take
all
your
other
commits
and
and
squash
them
into
one
your
first
one
here
so
now
that
I
have
that
selected,
I
can
go
ahead
and
re-run
this
job.
So
now
I
just
have
to
wait
for
this.
One
drop
to
run
instead
of
the
entire
pipeline,
which
I
would
have
had
to
do
if
I
updated
my
commit
here
and
then
pushed
up
my
change.
A
Okay,
I'm
back
and
my
job
has
finished
and
you
can
see
that
it
succeeded,
which
is
great.
So
if
you
look
up
here,
you
can
still
see
that
the
commit
subject
must
start
with
a
capital
letter.
But
now
it's
just
a
warning
and
the
reason
for
that
is
because
we
selected
that
option
for
squashing
the
commits
on
merge,
which
is
right
here
so
now
that
the
commits
will
be
squashed
on
merged.
That
means
that
this
commit
that
I
have
that
doesn't
have.