►
From YouTube: Framework for source code rules walkthrough
Description
A
A
A
What's
not
locked
down,
so
the
thought
was
well.
Maybe
we
can
combine
some
of
these
sets
of
rules
together
in
a
way
that
that
allow
organizations
to
operate
a
little
bit
better
so
born
out
of
this
was:
was
this
effort
framework
for
source
code
rules,
so
first
I'll
kind
of
walk
through
like
what
has
been
done
so
the
first
thing
we
kind
of
did
was
not
to
just
limit
it
to
the
things
that
I
was
talking
about
to
kind
of
look
at
all
sorts
of
stuff.
A
So
this
table
is
really
like
a
comparison
of
you
know,
kind
of
just
different
attributes
of
these
settings
to
try
and
look
and
see
what
where
are
the
consistencies
and
where
are
the
overlaps,
and
where
are
things
that
maybe
wouldn't
fit
into
here.
So
we
looked
at
approval
rules,
protected
branches
code
owners,
status,
checks,
scan
results
for
security
policies,
push
rules
and
protected
branches,
protect
protected
tags
and
push
rules.
Don't
have
a
lot
of
overlap.
A
Most
of
these
other
things
kind
of
do
so.
This
is
out
there.
I'm
not
going
to
go
through
it
in
much
more
detail
than
that,
but
this
was
kind
of
a
first
large
effort
was
kind
of
collecting
all
of
this
data
together
one
place,
then
we
also
kind
of
took
the
approach
of
not
like
going
solution
first.
So
when
I
was
first
introducing
I
was
talking
about,
you
know
these
might
be
branch-based.
We
didn't
make
that
assumption
upfront,
we've
kind
of
come
to
that.
A
So
I
went
through
a
number
of
kind
of
like
data
finding
issues,
so
I
created
like
knowns
and
unknowns,
and
I'm
just
walking
through
this
just
so
you
know
you
might
have
a
sense
of
like
where
you
might
want
to
go
and
look
at
this
information.
Most
of
these
have
been
closed
at
this
point,
so
they're
kind
of
efforts
that
happen,
but
there's
some
information
that
was
gathered
in
here.
So
the
idea
here
was
just
kind
of
look
through
things
that
we
know
and
things
that
we
don't
know
have
discussions
about
them.
A
So
this
basically
was
a
collection
of
kind
of
the
things
that
we
know
about.
These
types
of
rules
here
also
took
a
look
at
like
what
is
the
data
set
so
similar
to
that
kind
of
table
that
I
showed
earlier
like
what
are
the
data
attributes
that
are
involved
in
all
these
settings
and
trying
to
come
up
with
like
what
what
data
set?
Can
we
operate
against.
A
And
out
of
that,
it
came
clear
that,
well,
let
me
actually
go
into
this
one
here
that
the
crux
of
this
was
like
how
these
should
be
organized
right,
like
what
is
the
best
way
to
organize
these,
and
we
started
off
not
assuming
that
branch
would
be
the
first
way.
So
this
one
was
really
talking
about
like
different
ways
that
we
could
organize.
These
rule
sets
together.
A
Out
of
this,
it
was
the
the
theory.
Was
that
by
branch
is
the
obvious
choice
here,
but
we
also
did
some
research
on
that
so
worked
with
ben
and
pedro,
and
we
went
through.
We
put
this
through
a
research
study
put
in
front
of
some
users
and
basically
confirmed
that
belief
that
that
branches
as
an
organizational
system
is
the
proper
way
to
move
forward
with
this
so
kind
of
answered
the
the
data
set
and,
basically
all
of
this
kind
of
culminated
in
all
right.
A
I
then
kind
of
went
through
like
like
a
long
extended
like
greenfield
ui
exploration,
where
I
went
through
like
every
way
under
the
sun
that
the
ui
might
look.
Ultimately.
Most
of
this,
I
think,
maybe,
is
better
taken
as
an
exploration,
because
I'll
show
you
here
the
mvc
in
a
second
and
most
of
this
is
kind
of
irrelevant,
but
it
might
be
useful
for,
like
future
iterations,
to
kind
of
push
it
into
this
point
and
then
there's
this
one
as
well.
A
It's
related
efforts,
so
this
touches
a
lot
of
stuff
so
felt
the
need
to
document.
You
know
the
groups
that
are
affected
by
this
and
some
of
the
ongoing
efforts
that
they
have
so
like
compliance
container
security,
obviously
code
review
the
access
group,
particularly
around
our
back.
We
did
take
a
look
at
you
know
there.
There
was
this
ongoing
effort
from
from
a
design,
pod
roll
based
security,
basically
and
kind
of
looked
at
like
whether
it
makes
sense
to
combine
these
efforts.
Like
should,
should
this
be
an
extension
of
role-based
security.
A
A
So,
instead
of
picking
those
things
independently
and
applying
branches
to
them,
pick
a
branch
and
apply
those
to
that
which,
I
think
solves
the
problem
of
you
know,
lets
you
organize
these
things
generally.
The
branches
that
you
care
about
for
protection
reasons
are
the
branches
that
you
care
about.
A
For
approvals,
so
top
level
branch
selection
up
here
and
then
put
the
branch
protections
here
and
the
merge
requests
here
and
if
you're
familiar
with
the
current
ui,
this
is
basically
just
a
retread
of
that
and
take
out
the
few
like
like
this,
has
a
target.
Currently
this
has
a
target
branch,
and
this
has
a
target
branch,
but
since
you've
chosen
it
up
here,
it's
it's
that
so
it
is
very
much
the
ui
that
exists
today,
just
reorganized
into
kind
of
this
structure.
A
A
So,
like
the
name
of
this
thing
has
kind
of
gone
back
and
forth,
should
it
be
called
branch
rules
should
be
called
protection
safeguards,
it's
kind
of
how
there's
some
things
like
that.
That
could
probably
use
a
little
research,
so
I've
met
with
ben
the
researcher
and
kind
of
walked
him
through
this
some
of
this
stuff.
A
So
he's
aware
of
it,
and
I-
and
if
it's
the
kind
of
thing
that
I
think
that
maybe
could
benefit
from
research,
I've
kind
of
noted
it
here,
so
this
is
kind
of
the
where
we're
at
today
and
where
I
think
we
might
need
to
go
kind
of
not
complete
discussions
but
like
stubbed
out
threads
for
future
discussions,
and
then
the
last
thing
that
I
did
was
create
issues
for
like
future
improvement
kind
of
stuff.
So
that's
what
you'll
see
is
a
lot
of
these
other
ones
here.
A
A
Maybe
we
could
refine
that
and
then
several
other
things,
so
the
mvc
was
really
just
protected
branches
and
approval
rules,
but
there's
lots
of
other
features
that
could
potentially
move
over
there.
So
status
checks
might
be
an
interesting
one
to
move
over
there,
merge
checks,
push
rules,
merge,
request
options,
and
so
that's
what
this
set
here
is
is
is
other
features
that
we
might
want
to
move
over
there
in
the
future
post
mvc
and
then
just
a
few
like
nice
to
haves.
So
from
the
branches
page,
I
created
an
issue.
A
It
might
be
nice
once
this
exists.
If
on
the
branches
page,
if
you
could
just
launch
directly
into
the
editing
of
the
rules
there,
so
you
don't
have
to
go
to
settings
and
find
it,
this
might
be
a
nice
to
have
the
ability
to
duplicate
it
might
be
nice
to
have,
and
I
think
that's
it
so,
like
I
said
we
kind
of
have
an
nvc
laid
out
kind
of
have
some
discussions
stubbed
out
and
have
some
future
enhancement
issues
kind
of
laid
out
and
that's
kind
of
where
we're
at
today.