►
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
So
the
first
feature
I'd
like
to
share
with
you,
is
a
new
API
for
overriding
merge,
request,
approval
rules,
so,
in
a
previous
release
of
get
lab,
get
lab
11.8,
we
released
significant
upgrades
and
enhancements
to
the
merge
request,
approval
rules
so
that
you
could
define
lots
of
different
rules
and
the
specific
requirements
associated
with
those,
and
one
of
the
features
that
we
have
is
the
ability
for
the
author
of
merge
request
to
override
and
edit
those
rules.
This
is
an
optional
feature.
A
The
next
important
feature
I'd
like
to
draw
your
attention
to
is
logging
of
get
push
actions.
So
this
is
an
audit
logging
feature
as
part
of
the
premium
tier
of
gitlab,
and
all
the
logging
is
very
important
for
enterprise
and
corporate
customers
who
need
to
know
exactly
who
is
doing
what
and
we
have
many
different
audit
log
events.
But
one
of
the
events
that
we
don't
currently
have
is
who
and
when
changed
the
git
repository.
A
Obviously
it
has
logs
in
a
sense
in
the
history,
but
history
can
be
re-written
in
git
and
the
commits
that
are
pushed
may
not
actually
be
authored
by
the
person
who
pushes
them.
So
the
audit
log
is
important
because
it
will
be
tracking
the
information
of
who
actually
authenticated
and
the
changes
that
they
actually
made
at
that
time.
So
this
is
going
to
be
available
through
the
audit
events
system,
which
exists
at
the
project
group
and
system
level
and
is
available
in
git
lab
premium.
A
The
next
feature
I'd
like
to
draw
your
attention
to
is
a
the
file-by-file
navigation
that
we're
exploring.
So
in
a
previous
release.
We
added
file-by-file
tree
view,
so
you
could
click
between
the
different
files
and
which
you
can
see
here.
This
is
the
issue
with
the
different
files,
but
they're
still
shown
in
a
slight
list,
and
one
of
the
pieces
of
feedback
we've
frequently
heard
in
UX
research
is
that
this
can
become
quite
challenging
to
navigate
as
the
merge
request
grows
longer
with
many
files,
change
and
many
lines
changed.
A
Finding
one
spot
and
getting
lost
in
a
giant
scroll
is
difficult
and
there's
also
performance.
Challenges
associated
with
this
and
performance
is
one
of
the
most
frequently
requested
features
or
the
merge
request.
When
you
spend
so
much
time
in
a
part
of
the
application,
you
wanted
to
be
fast,
snappy
and
responsive,
and
so
in
12.3.
A
As
we
seek
to
listen
to
our
users
feedback
and
quickly
and
rapidly
improves
the
merge
request
to
handle
all
sorts
of
different
scenarios
and
finally,
we
intend
to
reenable
git
protocol
version
2.
A
new
version
of
the
git
wire
protocol
was
released
last
year
and
we
implemented
support
for
that
very
early
on.
But
there
was
a
security
issue
that
was
found
and
since
we
disabled
it,
we
have
not
yet
re-enabled
it
and
we
intend
to
do
that
with
a
feature
flag
and
commence
testing
and
rollout
of
get
protocol
v2.
A
So
those
are
the
four
highlights
from
get
lab.
12.3.
It's
going
to
be
a
great
release
and
I
look
forward
to
particularly
hearing
your
feedback
about
and
the
file
by
file,
diff
navigation
as
we
explore
that
and
share
our
results
with
you
and
share,
hopefully
a
better
version
that
you'll
be
able
to
experiment
with
and
test
in
the
coming
release.
Thanks
for
your
time,.