►
From YouTube: Solution Validation Summary: Branch rules MVC
A
A
A
Most
people
knew
that
it
was
within
the
repository
area
once
in
here,
and
this
is
how
the
prototype
worked.
If
you
expanded
a
session
section
that
wasn't
part
of
the
test,
you
would
have
this
empty
placeholder,
but
most
people
eventually
everyone
in
the
test.
We
tested
five
people.
They
were
able
to
find
the
branch
rules
through
looking
here
and
driving
into
here
to
find
whether
the
main
branch
was
protected
and
they
saw
this
area
here
to
understand
yep
it's
protected
with
these
settings
around
the
protective
branch.
A
So
that
was
really
good
to
know.
Asking
people
about
the
name
branch
rules.
They
felt
that
this
name
was
fitting
for
this
section
of
settings.
Some
people
suggested
branch
settings,
but
they
thought
that
was
kind
of
redundant
within
the
world
of
settings.
So
branch
rules
was
something
that
I
am
confident
if
us
recommending
this
to
go
forward
with
yeah.
Now,
let's
go
through
some
of
the
solution,
validation.
A
Four
out
of
five
gave
a
score
higher
than
of
four
or
five
one
person
gave
three
because
they
got
stuck
because
they
assumed
that
the
rules
would
be
a
monitor
and
they
couldn't
find
it.
So
they
were
actually
they
actually
did
not
complete
the
first
task,
the
second
task
of
finding
whether
the
main
branch
was
a
projected
branch
or
not.
But
after
they
found
out
the
keyword
or
branch
rules,
they
were
able
to
navigate
the
prototype
and
discover
the
branch
rules
within
the
repository
settings.
A
So
that's
good
to
know
so,
and
then
one
thing
one
thing
that
we're
going
to
follow
up
on
here
is
actually
taking
a
look
at
more
of
whether
we
should
explore
further
about
providing
overview
information
on
the
branch
rules.
So
at
the
moment
all
we
do
is
list
the
name
of
the
branches,
but
there
might
be
an
opportunity
here
to
help
users
understand
an
overview
of
what
the
branch
rules
are
without
needing
the
users
to
dive
through
each
single
branch
rules.
A
By
clicking
on
the
edit
to
see
what
the
details
are,
there
could
be
an
opportunity
to
surface
information
at
a
higher
level
so
that
they
can
take
a
look
at
the
high
level
information,
whether
they
want
to
jump
into
the
details
to
view
further.
That's
a
next
thing
that
we
want
to
explore.
So
I
created
a
follow-up
issue
for
this,
so
this
is
just
looking
at
the
overview
of
branch
rules
and
in
the
past.
A
This
is
something
that
was
explored
where
we
have
like
a
simple
kind
of
information
here
where
we
have
like
two
protections
and
a
few
approvals
and
here's
a
more
complex
view
that
was
explored
in
the
past,
ignored
this
tab
layout.
But
you
get
the
idea
where
there's
a
lot
more
information
at
this
level
yeah.
So
that
concludes
it
for
this
solution:
validation
around
the
source
code
of
bc.