►
From YouTube: Design concept - Viewing resolved rules by branch
A
Equally
of
the
source
code
group
and
today,
I'm
going
to
talk
about
resolving
rules
for
a
branch,
so
rules
in
this
context
talk
about
protective
branches
and
merger
press
approvals
coming
down
to
status
checks
as
well.
So
at
the
moment,
what
we
have
in
our
branches
view
is
a
whole
bunch
of
branches
and
we
have
a
button
that
allows
you
to
view
all
the
branch
rules.
So
it
navigates
you
within
two
settings,
and
this
allows
you
to
see
the
branch
rules
that
have
been
defined
for
the
project.
A
As
you
can
see,
there's
some
wildcard
rules
here
and
with
two
matching
branches.
But
if
I
wanted
to
know
you
know
what
are
the
rules
that
I
applied
to
like
feature
Branch
123
or
Branch
ABC?
We
don't
have
that
mechanism.
Yet
in
settings
where
we
do
have.
Is
that
kind
of
resolved
state
of
approvals
within
the
merge
request
itself.
A
A
So
let's
say
we
were
able
to
click
on
protected
for
branch
ABC.
We
could
display
the
branch
rules
in
a
drawer.
This
is
a
concept
that
I
explored
a
few
months
ago,
taking
the
read-only
view
of
what
we
have
in
Branch
rules
right
now
and
kind
of
resolving
all
the
different
branch
rules
that
match
into
into
one
this
that
you
can
consume
as
a
user
to
understand.
Okay,
have
I
set
up
these
branches.
Branch
rules
correctly
is
the
intended
result.
What
I
want
to
see
this
is
viewed
in
the
context
of
branches.
A
I
want
to
expand
this
further
to
think
about
both
accessing
this
from
branches
and
as
well
as
the
settings
pages.
So
let's
jump
into
what
that
might
look
like
once
again
we're
here
in
the
branches
with
the
badge.
This
is
one
approach
when
we
click
on
the
badge
and
that
navigates,
whether
we
introduce
a
button
to
do
that
over
here
and
that's
another
possible
thing
too.
So
if
I
click
on
Branch
23,
rather
than
opening
it
within
a
drawer,
we
could
open
it
on
a
separate
page.
A
Now
this
creates
a
separate
landing
page
for
the
URL
and
we
can
reference
this.
If
we're
sharing
it
within
teams,
we
can
say:
hey
check
out
the
resolve
rules
for
this
branch
and
it
would
navigate
to
this
special
page
here.
I
can
see
that
Target
Branch
123
has
a
three
matching
Branch
rules
from
here,
I
can
edit
them
or,
but
this
is
still
not
really
helpful
for
me,
as
someone
trying
to
understand
what
the
end
result
is
of
these
Branch
rules
and
I
would
have
to
dig
through
each
of
these
ones.
A
Take
a
look
at
the
approvers
here
and
in
this
scenario
you
know
we
have
a
list
of
three
different
approvers
or
are
they
the
same
approvers?
So
it's
not
100
there,
but
this
would
be
a
good
iteration
to
list
all
the
matching
Branch
rules.
The
Next
Step
would
actually
be
to
be
looking
at.
What
do
these
different
branch
rules
resolve
to
one
example
of
how
this
might
work
is,
if
I
click
on
this
and
it
opens
up
and
the
different
rules
that
have
been
approved.
A
So
in
this
scenario
here
this
is
the
exploration
I
did
where
I
convert
a
lot
of
the
branch
rules
UI
that
we
have
right
now
into
GL
card,
which
is
an
initiative,
that's
being
pushed
in
settings
to
kind
of
standardize
that
so
this
one
is
what
it
might
look
like.
We
have
our
Branch
protections
and
you
know
required
changes
to
be
submitted,
merge,
quests,
who's
allowed
to
merge
and
those
who
are
allowed
to
push
and
merge
and
and
merge
request
approvals.
A
This
one
is
a
very
elaborate
example
of
a
future.
Looking
example
of
how
a
merge
request
approvals
could
look
like
at
the
moment,
I
see
that
we
would
only
have
coverage
to
check
front-end
back
end,
but
thinking
about
inherited
approval
rules.
We
could
see
where
their
rules
have
been
inherited
from
different
groups
or
whether
it
could
be
something
that
would
be
injected
from
a
security
policy.
If
there
was
a
scan
to
be
a
run,
it
could
show
up
here
and
the
wording
and
Concepts
here
is
to
be
refined.
A
Like
I
said
that
is
coming
from
the
branches
view
so
clicking
on
the
badge.
But
if
we
look
at
our
Branch
rules
within
settings,
I
think
this
is
an
area
where
we
could
leverage
this
to
miss
our
Branch
rules
but
at
the
same
time,
have
a
way
to
view
the
rules
for
a
branch,
and
this
would
be
really
useful
to
verify
and
check
to
see,
did
I
set
up
my
Branch
rules
correctly
and
that's
what
we're
looking
at
when
we're
talking
about
resolving
Branch
rules.
So
I
will
click
on
this.
A
It
would
take
me
to
that
page
that
we
were
just
talking
about
wherever
that
may
live,
Branch
resolving
page
I
would
select
a
branch
and
then
there
I
would
see
all
the
different
rules
here.
This
allows
people
to
open
this
in
a
separate
tab,
allows
them
to
view
all
the
branch
rules
and
the
resolve
this.
At
the
same
time,
in
two
separate
tabs,
it
could
improve
the
workflow,
it's
something
that
we
could
explore
further
in
the
solution.