►
From YouTube: Introducing the Branch Rules Overview Feature
Description
Introducing https://gitlab.com/groups/gitlab-org/-/epics/8578
Please, provide your feedback in https://gitlab.com/gitlab-org/gitlab/-/issues/388149.
A
Hi
I'm
tolston
and,
on
behalf
of
the
source
code
management
team,
I'm
very
proud
to
introduce
this
new
feature
on
Branch
rule
overview.
You
may
know
that
we
have
many
settings
in
source
code
Management
on,
for
instance,
under
settings,
merge
requests,
you
can
set
merge,
request
approvals
for
different
branches,
you
can
say
which
groups
and
which
individuals
should
approve,
and
how
many
approvals
will
you
require?
You
also
have
coverage
checks,
license
checks.
We
also
have
security
approvals
again.
A
Then,
under
the
repository
settings
you
have
the
opportunity
to
protect
branches.
For
instance,
the
development
Branch
was
allowed
to
merge
with
an
outer
push
and
other
settings.
You
can
protect
this
and
then
here
you
have
the
list
of
Branch
rules
of
different
rules
that
apply
to
different
branches.
A
Now
we
realize
that
having
so
many
different
settings
about
branches
in
different
places
is
not
ideal.
Therefore,
we
introduced
this
new
feature,
which
is
brand
rules.
It
takes
an
entirely
different
perspective
on
the
rules.
It
takes
the
herb
Branch
perspective,
so
for
each
of
the
branches,
and
also
for
collection
of
branches
like
all
branches
or
Wildcat
branches
like
this
one,
you
see
all
the
rules
that
apply
to
it
and
you
can
then
go
to
the
details
to
the
the
details
of
those
rules.
A
A
You
will
still
need
to
go
to
the
existing
places
that
I've
shared
with
you
just
a
minute
ago,
but
we
are
starting
to
work
on
also
making
these
editable
in
this
one
place
and
for
this
I
would
like
to
ask
you
feedback
so
that
we
learn
how
you
appreciate
or
not
appreciate,
Branch
rules.
Please
add
any
feedback
to
this
issue
here:
I
linked
it
to
the
Epic,
so
any
feedback
is
welcome.
It
will
help
us
do
the
right
thing
for
the
next
iteration
of
this
work,
which
is
making
branch
rules
editable
thanks
a
lot.