►
From YouTube: Technical Bootcamp - Merge Request Approvals
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
A
A
A
The
merge
request
approvals
process
enables
a
workflow
to
be
implemented
that
balances
the
requirement
for
speed,
while
still
supporting
the
necessary
gates
and
controls.
Merge
requests
are
a
big
part
of
managing
code
and,
in
addition
to
that,
we'll
cover
a
few
other
features
that
make
merge,
requests
even
more
useful.
A
The
merge
request
approvals
feature
is
only
available
in
paid
tiers.
So
it's
not
supported
in
the
core
or
free
versions
of
git
lab,
merge,
request
approvals
require
specific
users
to
give
their
consent
and
agreement
to
the
changes
made
in
a
code.
These
are
presented
via
the
merge
request.
Without
merge
request,
approvals
orgs
would
depend
on
the
honor
system
or
some
other
process
to
find
outside
of
gitlab
when
it
comes
to
accepting
code
changes
and
not
enforced
within
gitlab.
A
If
we
look
at
the
screen
here,
we
can
see
this
merge
request
would
require
four
more
approvals
from
the
different
teams
listed
below
approval
rules
apply
to
branches,
and
this
is
useful,
with
long-lived
environment-based
branches,
it's
possible
to
choose
which
approval
rules
apply
to
a
given
branch
and
have
different
number
of
approvals
required.
We
also
have
several
other
configuration
options.
We
can
apply
to
merge,
request
approvals.
We
can
allow
approvals
to
be
overridden.
We
can
require
a
new
approval.
Every
time
there's
a
commit
and
several
others
around
how
approval
policies
should
be
handled
protected
branches.
A
Allow
you
to
apply,
read
and
write
permissions
to
your
entire
repository
or
specific
branches.
We
can
limit
creation
of
files
to
users
with
maintainer
or
owner
level.
Permission
and
we
can
restrict
pushes
to
users
only
with
the
allowed
permission,
protected
branches,
enforce
the
usage
of
merge
requests
and
they
act
as
an
additional
gate
to
prevent
forced
pushes
or
accidental
deleting
of
branches
wherever
needed.
A
A
The
code
owner's
file
lives
in
your
repository
and
it
defines
ownership
of
specific
files
or
paths
within
the
repository.
This
is
a
feature.
Gitlab
is
continuing
to
iterate
on
and
add
flexibility.
We
can
enable
granularity
and
approvals
and
also
informs
users
on
who
might
be
the
relevant
person
to
discuss.
Particular
persons
of
the
code
with
we
can
use
this
with
and
without
project
level,
merge,
request
approvals.