►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
james
and
everybody
else
who's
going
to
be
looking
at
this
video.
So
in
this
I'm
going
to
try
to
explain
why
we
created
this
epic,
which
is
much
immediately
possible
in
invalid
scenarios
with
merge
trains
enabled
this
actually
came
out
of
a
discussion
that
happened
in
the
issue,
which
was
created
approximately
a
year
back
that
said,
project
setting
to
allow
merge
before
pipelines
complete.
A
So
while
doing
some
investigation
for
this,
it
was
somewhere
around
here.
Okay,
we
had
a
really
long
discussion
in
this.
So
while
doing
the
investigation
for
this
issue
marcel-
and
I
discovered
a
few
discrepancies
in
our
current
implementation
of
different
world
strategies-
and
I
would
start
from
the
very
like,
with
the
most
basic
thing
that
we
started
to
look
at
so
we
started
to
look
at
how
merge
immediately
was
implemented
for
for
different
scenarios.
A
So
usually
you
see
a
merged
immediately
button.
When
a
pipeline
is
running,
it
is
supposed
to
bypass
the
running
pipeline
and
merge
immediately,
as
the
name
suggests,
and
if
the
pipeline
succeeds,
the
merge
immediately
button
it
just
vanishes.
It
doesn't
show
anymore
now
this
makes
sense
in
all
kinds
of
cases,
including
when
we
have
pipeline
for
merge
results
enabled,
but
the
merge
trains
is
not
now.
What
happens
when
the
merge
train
is
enabled?
A
So
what
we
see
as
much
immediately
when
merge
trains
is
enabled
is
actually
a
normal
merge
action,
so
we
are
providing
users
with
an
alternative
that
hey.
Do
you
want
to
add
this
to
your
to
the
train,
or
do
you
want
to
like
do
a
regular
merge
with
this,
mr,
and
it
does
not
essentially
emerge
immediately
because
nothing
is
being
bypassed
in
this
case,
so,
based
on
this
discussion,
what
we
decided
was
to
go
with
this
plan,
which
was
to
work
in
three
steps.
A
The
first
was
arika
toggle
in
the
enable
merge
strain
in
the
settings
to
disable
merge
immediately.
So
we
propose
that
in
the
settings
where
we
are
where
we
have
the
settings.
That
said,
that
says,
enable
merge
request
pipeline
and
the
cascading
setting
says
enable
merge
strain
if
the.
If
the
predecessor
is
checked
there,
we
should
add
a
toggle
that
says
yeah
that
that
says
only
allow
merging
via
merge
train.
A
That
means,
in
that
case,
users
would
not
see
a
merge
immediately
option
at
all
and
how
it
would
work
in
different
scenarios
has
been
chalked
out
here
and
also
like
when
it
is
not
checked.
What
would
happen
that
is
also
kind
of
defined
here,
and
so
this
is
how
we
want
to
control
whether
or
not
teams
would
want
to
have
an
alternative
if
they
have
enabled
merge
trains
for
their
groups
of
projects.
A
Now
this
is
the
first
step
like
to
make
this
happen.
We
first
have
to
work
on
this
backend
issue
which
is
created
for
the
same
because
currently
we
don't
have
the
capability
in
the
back
end,
so
there's
no
point
creating
something
on
the
ui
to
enable
it
I
mean
to
add
this
toggle.
A
So
definitely
this
particular
front-end
issue
is
blocked
by
the
backend
issue,
and
the
next
step
that
would
be
is
like
changing
the
copy
and
treatment
of
the
merge
immediately
button
to
rightly
communicate
the
action
so
like
I
said,
we
are
saying
that
it
has
a
merge
immediately
action,
but
essentially
it's
just
like
skipping
merge
train.
So
this
is
just
a
tentative
proposal
of
what
the
button
text
could
now
be
like
when
we
are
communicating,
rightly,
the
action
that
users
would
be
performing
when
they
click
on
that.
A
That
comes
next
and
that,
of
course,
is
blocked
on
the
first
one,
because
until
we
have
this
in
the
settings,
the
second
part
of
the
issue
second
issue-
it
just
doesn't
make
sense
as
a
standalone
item.
A
And
lastly,
we
have
an
issue
that
says:
improve
the
copy
for
pipeline,
must
succeed,
section
to
reflect
critical
changes,
and
in
this
one
like
once,
we
have
implemented
the
above
two
items
we
would
be
making
some
changes
in
how
we
are
communicating
about
pipeline
must
succeed
because
again,
merge
immediately
bypasses
a
pipeline.
If
we
have
selected
pipeline
must
succeed.
A
That
means
that
merge
immediately
option
has
to
go,
and-
and
this
is
not
communicated
anywhere
in
our
docs
or
the
ui-
the
settings
yeah,
and
that
is
all
and
that's
the
reason
that
we
have
these
three
issues:
blocked
they're,
actually
blocked
on
the
back
end
issues
and
that's
where
we
should
be
picking
up
from
that's
all.