►
From YouTube: Merge Trains Vision walk through
Description
Epic referenced in video: https://gitlab.com/groups/gitlab-org/-/epics/5122
A
So
we
have
an
epic
in
place
as
you
can
see,
and
it
contains
pretty
much
all
the
issues
that
you
plan
to
work
on
in
near
future
and
if
you
find
something
missing
or
something
out
of
place,
please
feel
free
to
add
a
comment
or
even
add
an
issue
to
this
today.
I
would
mostly
be
giving
a
very
high
level
update
on
the
list
of
issues,
but
in
case
you
need
to
dig
deeper
and
get
to
know
about
our
exact
plans
with
each
of
these
issues.
A
A
Moving
to
the
next
one,
it
says,
allow
users
to
add,
merge,
requests
back
to
merge
stream
when
dropped
due
to
an
accidental
action
or
due
to
failed
pipeline.
So
this
is
not
something
that
doesn't
happen
today,
but
it
doesn't
happen
in
a
very
in
a
very
simple
way.
So,
on
discussion
and
investigation,
we
figured
out
that
what
happens
today
is
we
are
not
able
to
differentiate
between
the
python
events
when
surfacing
the
message
and
action
when
the
situation
occurs.
A
So
we
are
working
on
those
capabilities,
but
in
the
meantime,
we
have
worked
on
an
mvc
solution
which
just
kind
of
changes,
the
ui
instructions
and
kind
of
hints
to
the
user-
that
this
could
have
happened
because
of
n
number
of
reason
and
links
them
to
a
section
in
the
dock
and
that
section
in
the
dock.
It
lists
the
probable
reasons
and
the
related
actions
that
they
need
to
take.
A
So
I
mean
it
makes
things
much
more
clearer
for
our
users,
the
next
one
is
a
very
important
one
and
it
it's
the
fast
forward,
merge
support
for
most
screens.
What
this
would
eventually
do
is
is
it
would
make
moisturize
much
more
efficient
if
enabled
all
right
so
for
this
particular
epic
we
had
to
take
like
there
were
multiple
rounds
of
discussions
and
since
it's
a
very
complex
one,
we
have.
A
Finally,
I
think
we're
finally
at
a
stage
when,
where
we
are
sorted-
and
we
kind
of
have
an
idea
about
what
improvements
we
need
to
make
on
the
technical
side
as
well
as
on
the
designs.
So
if
you
go
to
this,
if
you
go
to
this
epic
you'll
find
that
there's
a
long
list
of
issues
which
are
a
part
of
this
and
yeah
so,
and
the
new
workflow
proposal
looks
something
like
this
like
when
fast
forward
merge
and
merge
trains.
A
It
doesn't
break
the
mental
model
of
our
users,
so
there's
a
lot
of
work
that
needs
to
be
done,
but
things
are
underway
and
we
are
hopeful
all
right
and
the
last
one
is
visualize,
merge,
strains
so
moisture
in
itself.
It's
it's
kind
of
an
abstract
concept.
It's
very
difficult
to
understand
how
exactly
this
thing
works.
So,
when
users
are
interacting
with
this
feature
this
it
would
be
great
if
they
have
some
sort
of
a
representation
in
front
of
them
so
that
they
are
able
to
make
better
decisions.