►
From YouTube: Updating Direction pages - Review apps
A
A
So
we
have
a
general
description
here
about
what
review
apps.
Are
that
hasn't
changed,
so
I'm
not
going
to
go
ahead
and
change
anything
here.
A
There's
links
to
the
maturity
page,
the
issue
list,
which
is
filtered
by
review,
review,
apps
the
overall
vision,
our
documentation
and
the
ux
there's
a
reference
here
to
visual
reviews,
which
is
under
verify,
but
it's
closely
tied
to
review
apps
on
it's
that's
why
it's
here
in
the
direction
page,
and
then
we
have
what's
next
and
why
and
if
you
can
see
right
now,
it
says
that
we're
working
on
bug
fixes
related
to
review
apps
and
we're
asking
the
community
to
send
us
some
feedback.
A
If
there's
specific
issues
that
they're
interested
in,
but
in
this
release
we
actually
have
something
coming
up.
So
I
want
to
update
this
section
about
what's
next
and
why
so
I
have
a
board
that
is
filtered
by
the
current
release,
which
is
13.6
and
I
will
just
add.
A
So
what
I'm
going
to
do
is
just
add
this
here
and
I'm
gonna
right
here.
A
A
Issue
and
I'll
add
some
information
here
that
expiry
used
to
be
sent
according.
A
To
the
deployment
today,
but
some
environments
never.
A
And
then
we
have
the
second
issue,
so
I'm
going
to
look
at
the
current
we
have.
The
review
app
dynamic
environment
created
from
child's
pipeline
does
not
show
up
in
merge
requests
so.
A
A
A
They're
really
exciting
stuff,
so
this
is
one
the
the
first
one
that
we
mentioned
is
one
of
the
it
was
broken
off
from
an
additional
issue.
Let
me
find
it
it's.
This
one
provide
a
mechanism
to
clean
up
stale
environments,
and
this
is
one
of
the
most
popular
issues
that
we
have
in
progressive
delivery.
A
It
currently
has
54
up
votes
and
we've
been
doing
quite
a
lot
of
progress
around
this
for
the
past
year,
so
we
first
added
the
option
to
have
auto
expiry
for
deployments,
and
we
also
added
an
api
support
for
that
and
now
we're
adding
the
ability
to
extend
this
creation
of
environment
as
well.
So
you
can
see
in
the
yaml
file,
you
have
the
auto,
stop
in
keyword
and
now
it's
either
reset
according
to
the
creation
date
or
by
the
deployment
it
will
reset.
A
If
there
is
a
deployment
so
really
exciting,
and
the
other
issue
is
that
we
talked
about,
which
is
the
review
app
for
child
pipeline,
so
verify
delivered
a
really
really
cool
option
to
create
pipelines
and
child
parent
pipelines,
but
we
didn't
extend
the
additional
functionality.
So
now,
if
you
have
a
child's
parent
pipeline,
it's
really
cool
visually
in
the
pipeline,
but
the
review
app
only
opens
up
from
the
parent.
So
you
can't
see
the
effect
of
your
mr
in
the
child
pipeline.
A
Okay,
I
put
this
in
the
wrong
place,
so
I'm
gonna
just
undo
my
changes
and
just
cut
it
and
paste
it
again,
because
that
happens.
A
Yeah,
so
we
don't
want
that
in
the
visual
reviews
we
wanted
it
in
the
what's
next,
then
we
have
a
maturity
plan
and
the
category
is
currently
incomplete,
where
you
want
to
move
it
to
lovable.
To
be
totally
honest,
we
haven't
put
a
lot
of
effort
in
this
to
move
it
towards
lovable,
because
our
other
categories
are
in
much
worse
shape.
So
we
were
investing
a
lot
of
times
on
over
future
flags,
cd
advanced
deployments
to
make
a
real
impact
there.
A
I
actually
suspect
that
we
may
already
be
unlovable
for
review
apps
because
from
customer
interviews
it's
one
of
the
features
that
customers
love
the
most
in
gitlab,
but
there's
still
some
work
to
do
around
the
visual
reviews
and
the
ability
to
support
review
apps
for
mobile.
We
also
talked
about
maybe
supporting
review
apps
for
future
flex.
So
there's
a
lot
still
to
do
in
this
in
this
area.
A
So
then
we
have
the
competitive
landscape
which
our
biggest
competitor
is
hiruko.
I
don't
know
if
you
guys
have
seen
the
video
that
sid
posted
about
how,
when
you
want
to
start
building
something
haruko
is
awesome.
It's
really
easy
to
do,
but
when
you
need
to
to
start
pushing
to
production,
you
really
need
to
change
the
way
that
you
work.
So
one
of
the
advantages
that
we
have
to
get
in
gitlab
is
that
review.
Apps
is
part
of
the
workflow
and
it's
part
of
the
workflow
even
before
pushing
to
production.
A
So
it's
a
big
advantage
that
we
have
so
now.
I
want
to
just
make
sure
that
the
next
sections
are
up
to
date,
so
we
have
the
top
customer
success
issue
the
customer
issue,
internal
customer
and
the
top
vision
issue.
So
what
I'm
going
to
do
now
is
I
want
to
look
at
the
issues
that
we
have
under
our
group
and
then
I'm
going
to
filter
similarly
to
what
we
did
in
the
board
under
the
category
of
review
apps
and
then
what
I
will
do
is
it's
filtered
right
now
by
popularity.
A
So
that's
the
most,
the
most
popular
issues,
so
the
top
issue.
So,
let's
see
the
top
issue
regardless,
the
customer
or
non-customer
is
provide
a
mechanism
to
clean
up
steel
environments
which
we
discussed,
and
it's
also
an
internal
customer.
So,
let's
just
make
sure
it's
in
the
right
place,
so
you
can
see
it's
mentioned
here
under
top
internal
customer
issue.
A
So
I'm
going
to
leave
that
as
is,
and
there's
no
point
in
like
copying
the
same
issue
many
many
times.
So
what
I
want
to
check
now
is
what
is
the
top
customer
issue,
and
this
is
a
little
bit
tricky
because
it's
not
always
labeled
correctly.
A
A
A
A
A
way
to
clean
up
the
the
sale
environment,
so
that's
what's
written
here
to
clean
up
environments,
whether
the
they
have
expiration
dates
or
not,
and
then
there's
also
a
reference
to
review
apps
for
gitlab
pages,
which
I
will
open
up
here.
A
The
reason
it
didn't
come
up
in
our
filter
is
because
it
is
under
the
release
management
group,
but
I'm
still
going
to
leave
this
in
the
this
direction
page
because
they're
tightly
coupled
so
I
think
it
makes
sense
to
leave
this
as
as
a
highly
requested
issue
and
let's
just
go
over
management
review.
Apps
can
be
a
challenge,
particularly
in
cleaning
them
up,
and
to
highlight
the
severity
of
how
this
issue
can
grow.
A
A
The
first
thing
we
did
was
introduce
this
expiration
date,
which
is
that
keyword
that
I
showed
you
auto
stop
in
the
problem.
Is
that
didn't
really
solve
their
problem
because
most
of
the
review
apps
there
didn't
really
have
deployment
so
we're
expanding
on
that
in
this
release,
as
I
mentioned,
and
let's
see
what
this
issue
is.
A
Yeah
this
is
the
top
issue,
so
provide
a
mechanism
to
clean
up
still
environment.
So
we've
been
breaking
off
of
this
issue.
Many
different
small
issues
just
to
complete
it
so
we're
in
the
right
direction,
but
there's
still
some
work
to
do
so.
I'm
gonna
leave
that
one
in
as
well.
So
all
of
these
are
pretty
much
up
to
date
and
last
week,
but
not
least,
is
the
top
vision
item
and
our
focus
is
to
bring
review
apps
to
mobile
workflows.
A
There's
an
epic
here
linked
to
do
that.
I'm
still
gonna
leave
that
in,
even
though
I'm
in
a
dilemma
whether
or
not
to
change
that
to
the
connection
between
future
flights
and
review
apps.
But
it
is
definitely
one
of
the
really
cool
offerings
that
we
can
do,
which
is
connecting
mobile
development
to
review
apps
and
there's
a
lot
of
buzz
around
that
actually
andrew
has
written
a
blog
post
about
how
you
can
collect,
connect
an
emulator
called
appetiziel
to
the
gitlab
workflow.
A
So
it's
really
cool,
and
that
was
the
first
step
that
we
did
in
this
direction.
I'm
still
going
to
leave
this
in
because
it's
still
a
high
priority
in
terms
of
leadership
and
maybe
the
connection
between
review,
apps
and
feature
flags
I'll
put
in
the
feature
flag
direction
page
so
stay
tuned.
To
see.
To
see
that
I
hope
this
was
helpful
and
you
know
if
you
have
any
questions,
feel
free
to
bring
me
on
the
mr.