►
From YouTube: UX MR Review of Runner Group using GDK
Description
Gina Doyle (Product Designer, Verify::Testing & Runner) walks through an MR Review (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70151) for the Runner Admin area using her local GDK.
A
Hey
everyone,
I'm
jen
doyle
and
I'm
a
product
designer
for
the
testing
and
runner
groups.
Today,
I'm
going
to
be
reviewing
a
merge
request
around
something
that
we're
adding
in
the
runner
admin
area,
and
I
wanted
to
show
the
process
that
I
go
through
when
I'm
reviewing
one.
So
this
one
specifically
is
around
specifying
a
project
or
restricting
a
runner
to
a
project
and
updating
the
alert
to
give
you
like
this
thing
was
saved,
which
we
do
everywhere
else.
A
If
you
were
to
go
to
a
runner,
we
would
have
to
go
to
a
shared
one.
A
A
A
Okay
and
I
got
it
so
that's
a
simple
idea
of
how
I
am
usually
reviewing
and
from
this
I'll,
just
check
like
break
points,
make
sure
that
it
makes
sense
make
sure
it's
dismissible,
which
it
looks
like
it
is,
and
I'll
probably
do
it
to
a
couple
other
of
the
specific
runners,
and
I
might
just
want
to
check
even
the
shared
runners
are
working
the
same
way
once
I'm
done
I'll.
Come
back
to
this,
mr
and
just
leave
my
comments
for
this
one
specifically.
A
Actually
it's
a
little
bit
different,
because
there
is
something
that
miguel
has
pointed
out.
That
will
actually
have
to
be
created
as
a
follow-up
to
for
a
ux
debt
issue,
because
the
changes
saved
alert
isn't
the
right
styling.
But
it's
not
blocking
enough
to
be
able
to
not
approve
this.
Mr,
so
thank
you.