►
From YouTube: How to use approvers in MRs during code view
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,
my
name
is
sarah,
and
I'm
here
with
david,
we're
part
of
the
product
team
within
the
dev
section
here
at
get
lab
and
recording
a
short
video
demonstrating
how
code,
review
and
merge
request
approvals
work.
B
So
if
we
expand
that
you
can
see,
you
can
have
any
eligible
user
approve
on
any
branch
and
we're
going
to
set
this
to
one.
So
that
way,
it's
at
least
one
approval
needed
to
do
the
merge
also
by
default.
We
have
require
new
approvals
when
commits
are
made,
as
well
as
prevent
mr
approvals
by
the
author,
but
to
help
enforce
this.
B
We're
also
going
to
prevent
users
from
modifying
the
mr
approval
roles
within
their
merge
request,
as
well
as
prevent
mr
approvals
from
users
who
have
made
a
commit,
and
that's
where
the
authors
come
in.
So
in
this
example,
I'm
going
to
make
a
code
change
sarah's
going
to
review
and
approve
it.
However,
if
sarah
didn't
make
a
change,
she's
now
part
of
the
author,
so
we
would
not
want
her
to
approve
that
so
I'll
hit,
save
changes
here
and
the
final
area
is
to
work
on
the
protected
branch.
B
So
those
settings
are
under
repository
and
under
protected
branches,
and
here
you
can
see
we
have
our
default
branch
today
is
only
allowing
maintainers
to
merge.
However,
we
do
want
to
allow
any
eligible
user
developer
and
above
so
we
are
going
to
check
developers
plus
maintainers
and
with
that
setting
change
now
any
developer
who's.
Not
the
author
can
approve
and
merge
the
merge
request.
B
B
B
This
is
going
to
open
up
a
merge
request
and
allow
me
to
add
a
comment
and
I'm
just
going
to
hit,
create
merge
request
and
what
we're
going
to
see
is,
as
this
begins
it's
automatically
going
to
say.
I
need
approval,
because
I
am
not
someone
who
did
not
author.
The
part
of
the
change
and
with
that
also
the
merge
request.
Button
is
also
a
grayed
out
for
me
now
to
get
that
merged.
A
All
right
so
since
david
opened
nmr-
and
he
is
the
author
of
that,
mr
he
does
not
have
the
ability
to
approve
and
merge
his
own
changes,
and
so
I'm
going
to
do
that
for
him
as
a
developer.
In
this
project,
I
am
considered
an
eligible
user
navigating
to
merge
requests.
I
see
the
merge
request
that
david
opened.
That
needs
my
approval
and
merge,
and
we
can
see
that
the
button
is
enabled.
A
So
I'm
able
to
approve
this
go
ahead
and
approve
that,
and
then
we
can
see
that
the
merge
button
is
enabled,
because
I
didn't
make
any
changes
here
and
I
have
the
correct
permissions
within
the
project.
As
a
developer,
I
can
merge
to
the
main
branch,
should
go
ahead
and
merge
that
or
should
I
leave
that
unmerged
feel
free
to
merge
that
cool
thanks
david.