►
From YouTube: GitLab Community coders - pair programming
Description
Join Marco Zille, Andrew Smith, and Lee Tickett as they are walking us through their thought process on identifying an issue and contributing to GitLab
B
B
C
A
B
A
C
A
First
was
I
looked
at
the
screenshot
in
the
issue
and
saw
some
wordage
that
I
thought
was
probably
specific
to
that
view
or
that
component
or
page
or
whatever
and
yeah.
You
can
see
exactly
what
I'm
looking
at.
So
I'm
guessing
that
this
is
the
com
or
one
of
the
components.
It
might
be,
that
there's
multiple!
A
A
C
A
A
A
Yeah
flory
changed
this
19
months
ago,
so
we
could
try
and
find
the
mr
to
see
if
this
was
added
or
whatever.
But
if
we
look
at
the
cancel
method,
we
might
be
able
to
see,
because
my
suspicion
is
that
we're
preventing
the
hide
on
purpose,
because
whatever
our
council
method
is,
should
maybe
be
doing
something
that
includes
kind
of
ultimately
hiding
it.
B
B
A
B
B
B
B
B
B
C
C
Yeah
the
comment:
sorry,
the
comment
before
the
one
I
linked
to
actually
says
from
alexis.
First
thing:
users
shouldn't
be
able
to
click
out
of
that
modal.
The
only
way
they
should
be
able
to
exit
is
by
applying
cancelling
or
pressing
the
x
icon,
since
I'm
able
to
click
out
of
the
modal,
I'm
seeing
some
strange
behavior
until
I
explicitly
click
one
of
the
buttons
or
x,
I
see
the
same
model,
no
matter
where
I
click
and
the
edit
board
button
doesn't
trigger
the
model.
One
all.
C
C
C
C
A
B
A
A
B
A
So
what
I
was
thinking
is:
could
there
be
a
difference
between
a
what
I
call
it
like
a
view,
only
component
versus
a
sort
of
one
that
allows
you
to
modify
data
because
on
the
time
log
report,
it's
if
you
close
it,
it
doesn't
matter
you
reopen
it
again.
If
you're
on
like
an
edit
or
create
screen,
you
start
filling
all
the
fields
in
and
then
you
accidentally
click
off
or
close.
It
dismiss
it.
Then
it's
going
to
be
a
bit
annoying
because
you've
lost
the
data
that
you
entered.
Maybe
they.
A
A
It's
been
so
quick
to
change
it.
Let's
run
these
couple
of
specs
see
if,
if
there's
much
effort
required,
if
there's
any
effort
required
to
fix
them
and
then
we'll
just
yeah,
we'll
push
it
up
and
we'll
start
the
discussion.
There's
no
harm
done.
If
we
spent
15
minutes
gonna,
but
yeah
either
way,
it
should
close
those
two
issues,
whether
it's
a
sort
of
close,
because
that's
not
how
we
want
it
to
behave
or
close,
and
maybe
we
need
to
check
documentation.
A
B
A
B
B
A
Pajamas
explicitly
says
there
should
always
be
multiple
ways
to
close
or
dismiss
this
type
of
model
yeah,
including
allowing
the
user
to
click
outside
the
modal
area
or
use
the
escape
key.
This
is
important
as
some
modals
can
be
tall,
and
we
want
to
avoid
making
the
user
scroll
up
to
close
a
modal.
I
mean
that's,
obviously
not
that
appropriate
in
this
instance,
but
if
that
guidance
has
changed,
we
definitely
need
to
update
update
the
pajamas
guidelines.
C
A
A
A
B
A
B
A
B
A
C
B
A
B
C
B
A
A
Yeah
must
they
well
I'm
going
to
jump
off
now
guys?
Maybe
we
don't
have
one
later
in
the
week,
because
this
was
so
well.
I
hope
it
was
successful
anyway
and
yeah
just
picking
a
ping
of
cmr
link
once
you've
got
it
I'll,
assign
alexis
and
if
there's
anything
that
I
feel
like,
I
can
add
I'll,
add
and
we'll
go
from
there.