►
From YouTube: 01.12 PA UX + FE Sync ✨
Description
Monthly sync meeting between Pipeline Authoring UX and FE.
A
A
As
part
of
this
research,
I
interviewed
five
gitlab
users
and
had
them
create
a
simple
pipeline
configuration
using
the
pipeline
editor
and
next
week
I
will
be
analyzing
the
interview
recordings
and
synthesizing.
The
insights
so
very
excited
to
share
the
results
with
you
soon
and
there's
going
to
be
lots
of
interesting
feedback
on
how
we
can
improve
the
winter,
specifically,
the
linter
output,
how
to
make
it
easier
to
navigate
and
also
learned
a
lot
about
how
our
users
interact
with
the
merged
yaml
view
and
how
we
can
improve
that
as
well.
A
One
of
the
versions
is
where
we
will
have
one
drop
down
where
you
can
select
between
either
non-pipeline
conditions
or
validating
your
pipeline
for
a
default
branch
commit,
and
then
you
can
have
a
look
at
the
issue.
There.
Isn't
the
solution?
Validation?
No,
it's!
Yes,
the
design
issue
that
I
like.
So
you
can
have
a
look
at
the
designs
in
that
issue
to
see
how
it
works
and
another
version
would
be
to
separate
pipeline
conditions
into
separate
drop-down
controls.
A
So
we
just
want
to
see
whether
the
future
is
easy
to
understand,
because
this
is
kind
of
something
that
we're
struggling
with,
because
the
current
implementation
is
very
limited.
We
only
have
one
specific
hardcore
coded
parameter
that
you
can
validate
your
pipeline
with
it's
only
for
the
default
branch
commit.
So
the
struggle
here
is:
how
do
we
present
it
in
the
ui?
So
you
you
understand
what
it
does
and
what
it
is.
It
would
be
easier
if
we
already
had
all
of
the
different
options,
so
you
can
see.
A
A
And
then
I
have
just
a
couple
questions,
so
I
know
that
you're
working
or
you're
going
to
work
on
the
trigger
job
page
issue,
and
I
was
wondering
if
you
have
any
other
questions
or
is
there
anything
I
can
do
to
help
and
the
illustration
I'm
still
working
on.
So
I
also
wanted
to
make
sure
that
I'm
not
blocking
you.
B
Oh
no
yeah,
so
I
was
actually
supposed
to
work
on
it
started
this
week,
but
I
was
out
on
monday,
tuesday,
so
I'm
actually
just
about
to
start
working
on
it
this
today,
and
so
the
illustration
wouldn't
really
be
blocking
for
me.
I
can
actually
just
use
like
some
random
illustration
for
now
and
then
just
you
know,
slap
the
new
illustration
in
so
it's
not
really
blocking.
B
A
B
Yeah,
I
actually,
I
just
saw
that
earlier
today
as
well,
so
I
don't
think
that
it,
it's
not
just
the
the
drop
down
that
was
gone
or
the
autocomplete,
but
I
feel
like
the
the
schema
isn't
being
used
at
all.
I'm
not
sure
what
happened
either.
It
feels
like
a
bug,
but
I
also
don't
remember
anything
that
has
been
worked
on
for
the
schema
or
the
integration
with
the
schema
in
pipeline
authoring.
B
So
I'm
I
haven't
checked
on
it
yet,
but
it's
either
there's
something
that
happened
with
the
editor
because
we're
using,
I
think,
under
the
hood.
This
uses
the
same
components
as
the
editor
light.
So
maybe
something
happened
there,
I'm
not
sure,
but
I
think
the
scheme
is
just
not
being
used
at
all
and
yeah.
It's
something
to
investigate.
B
Yeah
I'll
take
a
look
as
well,
because
it's
not
just
the
autocomplete,
it's
like
everything,
there's
not
like.
If
there's
an
error
that
I'm
expecting
it
doesn't
show
up
and
the
usually.
If
you
highlight
on
the
keywords,
you
would
see
an
annotation
with
the
definition
of
those
keywords
and
like
what's
the
expected
parameters
or
things
like
that,
but
those
aren't
showing
up
either.
So
it's
like
the
schema
is
just
not
being
used
at
all.
I
think
yeah,
okay,
might
be
a
bug.
A
Yeah
I'll
create
an
issue
for
this.
I'm
peeing
you
on
dove
and
the
editor
team
as
well
to
see
what
they
think.
Yeah
yeah
sounds
good.
I
know
that
they've
been
working
on
some
changes.
I
mean
they're,
always
working
something,
so
it's
possible
that
that
it
happened.
There
was
actually
an
mmr
that
I
was
reviewing
where
they
changed
some
styling
on
the
autocomplete,
so
it
could.
It
could
be
related,
though
I
think
it
only
changed.
The
styling
like
when
you're
hovering
over
the
keywords
in
the
autocomplete
drop
down.
A
B
If
something
changes
in
the
like
the
rules,
logic,
for
example,
then
the
bot
in
the
mr
will
tell
the
author
to
hey
to
just
kind
of
remind
them
that
hey
since
you've
changed
these,
you
might
need
to
change
the
schema
file
as
well,
so
just
kind
of
like
to
update
the
what's
being
used
in
the
front
end.
So
I'm
not
sure
if
that's
one's
been
merged,
yet
so
I'll
check
after
this
meeting.
I
don't
think
it
should
affect
this
bug,
though,
but
that's
the
only
thing
that
I
can
think
of.
A
B
Right,
okay,
so
I've
had
here.
Well,
you
mentioned
it
in
the
weekly
meeting
earlier
as
well
that
since
I
updated
the
styling
and
accessibility
of
the
pipeline
mini
graph
and
also
for
fred's
knowledge
as
well
hi
fred
there.
I
noticed
that
there
was
an
interesting
thing
about
accessibility,
where
mac
os
doesn't
enable
it
completely
for
some
reason.
So
there
are
some
steps
to
do
in
order
to
enable
it
on
mac
os
and
like
make
sure
that
testing
is
going
well.
B
So
that's
basically
how
we
paul
for
updates
on
the
back
end
and
make
sure
it's
like
a
lot
better,
but
I
think
that
one's
still
in
flight,
so
I'm
still
waiting
for
a
review
on
that,
like
I
said
earlier
today
and
for
the
rest
of
the
week
for
this
iteration
I'll
be
focusing
on
adding
the
trigger
job
page.
So
it
took
me
a
while
to
be
honest
to
kind
of
understand,
like
the
whole
context
around
the
issue.
B
I
think
we've
talked
about
this
in
the
retrospective
for
the
iteration
as
well,
and
I've
had
some
conversations
with
you
and
laura
about
it.
So
I
think,
but
I
think
now
I'm
ready
to
work
on
it
since
I'm
only
getting
started.
I
don't
have
many
questions
yet
or
more,
like
I've
already
asked
them
before
on
slack,
but
I
will
let
you
and
laura
know
if
there's
anything
else,
I
need
so
yeah.
I
think
for
now.
It's
just
the
illustration
yeah,
but
it's
not
blocking
so
it's
okay,
okay,.
A
Cool
sounds
good
yeah,
I'm
trying
to
get
it
reviewed
by
someone
from
the
ux
foundations
team,
who
is
usually
reviewing
all
of
our
visual
stuff,
like
that,
like
illustrations
and
icons,
and
I
think
he's
currently
at
capacity
so
worst
case.
I
will
just
create
an
svg
for
this
and
we
can
use
it
and
if
we
need
to
make
updates
in
the
future,
then
it
can
be
a
follow-up
like
it's
obviously
not
critical.
A
A
A
And
now
we
end
up
in
a
situation
where
we
have
discussions,
spread
over
a
design
issue
and
then
implementation
issues
and
then
maybe
also
an
epic,
so
it
gets
very
confusing
so
to
address
that
problem.
I
I
think
it's
important
that
if
any
questions
come
up,
that
we
move
the
issue
back
into
workflow
design
and
we
don't
create
implementation
issues
prematurely.
A
Because
that
way
we
will
have
those
discussions
there
around
the
design
contained
in
the
design
issue
and-
and
this
way
also
because
I'm
supposed
to
be
leading
the
design
process
and
leading
those
discussions
and
making
sure
that
all
of
the
questions
are
answered.
So
I
will
make
sure
that
we
move
the
issue
back
into
workflow
design.
A
If
there
are
some
open
questions,
so
hopefully
that
can
help
with
not
getting
issues
that
are
not
ready
into
planning
and
breakdown,
though,
there's
still
the
problem
with
just
generally
how
we
break
things
down
into
issues
and
what
issues
get
created
and
how
we
work
with
ethics.
But
that's
a
whole
different
story,
and
I
don't
I
don't.
B
Yeah,
I
think
it's
just
just
a
really
very
there's
just
a
lot
of
discussions
that
are
really
hard
to
summarize.
I
think-
and
I
think
the
issue
has
been
like
a
year
old,
at
least
so.
There's
definitely
like
a
lot
of
things
to
filter
through
and
for
someone
who's
jumping
in
really
late
into
the
discussion.
Like
me,
it
was
just
a
bit
difficult
to
kind
of
understand,
like
I
do
understand,
like
the
main
problem
and
what
we're
gonna
do.
B
I
think
the
one
that
I
would
have
appreciated
to
be
included
is
why
this
particular
solution
was
decided
on.
So,
for
example,
we
decided
on
creating
a
trigger
job
page
instead
of
the
just
adding
the
button
right
away
on
the
pipeline
graph
or
creating
a
model,
or
something
like
that.
So
I
think
the
skip
in
that
part
of
the
line
of
thinking
was
one
that
I
wasn't.
I
didn't
quite
understand
very
well.
While
I
was
reading
the
issue
yeah.
So
that's
just
that's
just
for
me,
but
what
I've
noticed
yeah.
A
Okay,
yeah
so
I'll,
try
to
add
more
context
around
the
design
decisions
to
the
issue,
description
and
speaking
of
just
generally
having
a
more
complete
picture
in
the
issue
description.
This
is
something
we
can
also
improve,
so
I've
been
creating
issues
often
times
where
I
just
have
the
problem
section.
Then
the
proposal
section
that
focuses
largely
on
just
the
you
know
like
higher
level
design
proposal.
A
A
It
provides
more
context
also
about
the
problem
that
we're
solving
what
needs
to
be
done
documentation
as
well,
so
I
will
be
using
the
complete
issue
template
that
will
hopefully
help
us
provide
more
structure
to
that
information
and
also
I'll
make
sure
to
summarize
the
discussions
in
the
issue
description
as
well,
because
yeah,
I
think
I
understand
when
the
issue
is
so
long
and
there's
one
year
worth
of
discussions,
it's
very
difficult
to
navigate
that.
I
think
part
of
that
is
that
it's
difficult
for
me
to
navigate
yeah.
I
don't
blame
you.
B
B
There
are
just
some
issues
that
come
up
like
this
one
that
ends
up
being
really
complicated
or
had
has
a
lot
of
context
that
stumps
us,
but
for
the
most
part
it
hasn't
been.
I
mean
there
have
been
some
issues
but
like
there
are
also
some
issues
where
it's.
It
hasn't
been
a
problem
either,
and
we've
been
doing
good
with
that
as
well.
So
yeah,
okay,.