►
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
Hello,
my
name
is
Michael
Lee,
the
source
editor
group
and
today
I'm,
going
to
be
talking
about
approaching,
merge,
request,
approvals
and
editing
experiences
in
the
context
of
Branch
rules
So.
Currently,
this
is
merge,
request,
approvals
and
there's
two
areas
here
that
I
am
planning
to
address,
as
we
make
updates
to
editing
them
in
the
world
of
Branch
rules
and
that's
first
handling
making
it
clear.
What's
a
required
number
of
approvals.
A
So
that's
a
something
that
I
feel
that
we
have
an
opportunity
to
improve
and
dealing
with
scenarios
where
we
include
so
many
people
that
you
know
we're
listening,
300
people
individually
here
and
it's
not
very
clear
who
their
approvers
are,
in
my
opinion
right.
So
the
first
thing
is
one
feature
that
has
been
coming
up
from
group
level.
Settings
is
setting
a
minimum
number
of
approvers,
that's
required
for
all
merge,
requests
and
that's
handled
by
this
area
here.
A
So
we
approval
is
required
all
eligible
users
and
the
idea
here
that
at
the
moment
is
defaulted
to
zero,
but
eventually
from
a
group
level.
We
may
want
to
set
that
as
one
or
two
on
all
merge
requests
to
ensure
that
you
know
every
merge
request
at
least
has
those
number
of
approvers
in
a
pass
design.
A
We
can
see
that
these
are
the
rules
and
the
number
of
approvals
required
for
those
rules.
This
in
one
way,
I
saw
it
as
I
just
need
two
approvers
for
the
merge
request.
It
doesn't
matter
who
so
it
could
live
outside
of
here.
But
another
way
to
think
about
this
is
that
this
is
actually
just
a
rule
itself,
and
if
we
go
back
and
bring
that
back
into
the
world
of
our
list,
we
have
all
eligible
users,
and
this
is
where
I
think
we
can
make
a
small
change.
A
That
will
make
things
a
lot
more
clear.
So
all
eligible
users
are
actually
the
approvers
who
are
allowed
to
give
the
two
approvals.
But
this
rule
then
doesn't
have
a
name,
and
the
name
of
this
rule
is
actually
what
it
is
is
the
number
of
required
approvals.
So
if
we
do
something
like
this,
it's
actually
clear
from
the
merge
request.
Approval
list
that
this
rule
here
is
the
number
of
required
approvals.
We
can
change
the
labeling
here
to
make
that
more
clear,
whether
that's
the
required
number
of
approvals.
A
I
just
wrote
this
for
now,
because
it's
shorter
and
fits
but
open
to
suggestions
there,
and
here
the
approvers
list.
We
have
any
eligible
users,
and
if
you
hover
over
that,
we
would
display
the
same
pop-up
that
we
had
from
before
by
moving
by
keeping
this
stuff
in
the
pop-up.
We're
not
cluttering
the
UI.
A
With
all
this
information
of
who
can
improve
the
reason
I
brought
it
out
earlier
was
I
thought
that
by
taking
this
outside,
we
would
make
it
clear
that
this
is
the
number
of
required
approvals
overall,
but
I
feel
that
this
kind
of
sits
well
here
as
well
yeah.
So
back
to
this,
you
know,
by
giving
it
a
rule
name,
we
may
have
created
something
that's
more
clear
and,
of
course,
people
can't
edit
it
using
edit
buttons,
but
changing
the
numbers
here.
A
So
that's
why
I
changed
this
number
to
374
and
here's
seven
more
and
I
shall
have
here,
show
all
17..
So
for
this
case,
if
I
went
ahead
and
went
with
the
show
all
17,
we
could
do
the
classic
way
of
doing
our
displaying
all
the
heads
of
the
people
here
and
this.
This
could
be
good
for
MVC,
because
we
already
have
this
pattern
established
within
in
GitHub.
A
But
if
I
had
like
a
lot
of
people
and
I
wanted
to
scan
to
make
sure
that
those
people
are
there
if
I
know
what
their
Avatar
is
happy
days,
but
in
the
scenario
where
I
may
not
know
what
their
Avatar
is
or
they
change
the
Avatar
or
some
people
left
the
group
or
stuff
like
that.
This
list
would
change
and
reshape
so
an
alternative
way
to
present
this
would
be
on
click.
A
We
actually
display
all
the
list
of
the
people
in
a
modal
and
inside
this
model
the
list
will
be
scrollable
and
it
would
be
sorted
by
alphabetical
order
so
that
you
can
just
scan
and
see
whoever
you're,
looking
for
and
based
on
that,
whether
it's
sorted
by
first
name
last
name
or
a
username
I
think
that's
something
we
can
refine
and
update,
and
perhaps
we
could
have
a
filter
in
here.
But
at
the
moment
this
design
just
hints
at
sorting
by
people's
first
names
so
yeah.