►
From YouTube: GitLab Code Quality: Speed Run Update
Description
Update to the original speed run (https://www.youtube.com/watch?v=B32LxtJKo9M) with new features introduced since original recorded in January 2020.
A new MR was created to show the features but using the original project: https://gitlab.com/jheimbuck_gl/jh_java_example_project/-/merge_requests/26
A
Hey
I'm
james
heimbuck,
the
product
manager
for
the
testing
team
in
the
verify
stage
at
gitlab
and
on
my
screen,
I'm
sharing
the
youtube
video.
The
speed
run
that
I
uploaded
about
a
year
ago
showing
off
the
code
quality
feature.
So
I
wanted
to
provide
an
update
to
this
about
a
year
later,
almost
15
months
later
of
some
of
the
things
we've
worked
on
in
the
time
since
so
as
I
was
going
through
and
rewatching
this
today,
I
noticed
that
I
called
out
you
could
download
that
full
report.
A
Well,
not
only
can
you
download
the
full
report,
but
if
you're
a
premium
or
an
ultimate
customer,
you
also
have
access
to
the
full
report
in
the
ui.
So
on
your
pipeline
tab,
you
can
see
a
code
quality
tab
here
and
it
lists
all
of
the
things
that
were
found
as
part
of
the
pipeline
run.
So
this
is
not
just
what
has
changed
in
the
merge
request,
but
the
full
list,
everything
that
was
discovered.
A
It
includes
severity
now,
so
you
can
understand
really.
What
is
the
things
that?
What
are
the
things
that
we
should
work
on?
First,
and
in
my
example,
I
only
have
a
couple:
this
is
just
a
quick
update
to
the
hello
world
from
the
original
video,
but
if
you're
working
in
a
project
like
git
lab,
where
maybe
you
have
a
lot
of
code
quality
issues,
the
team
hasn't
dug
into
for
a
while.
Many
of
those
are
probably
a
low
severity,
but
you
might
miss
some
of
the
little
ones.
A
In
this
example,
we
see
there's
three
or
four
critical
issues
that
we
should
probably
take
a
look
at
but
they're
in
a
list
of
ten
thousand.
So
before
sorting
these
by
severity,
you
would
have
been
paging
through
400
something
pages
to
try
to
find
these,
and
that's
just
not
a
great
experience
for
anybody.
So
these
are
now
sorted
by
the
severity,
the
worst
things
are
on
top
and
you
can
always
customize
through
your
codeclimate.yaml,
adding
engines,
removing
engines
adding
plugins
to
better
tweak
what
you
see
in
those
results.
A
So
in
the
merge
request
itself,
you're
still
going
to
see
what
is
going
on
here
again.
Sorted
has
the
severity
there.
You
can
click
in
and
get
to
the
file,
and
I
wanted
to
show
off
a
new
feature
that
is
coming
in
the
mrdiff,
so
it's
not
enabled
on
this
project,
but
we
do
have
it
enabled
on
the
gitlab
project
today
and
that
is
in
the
mrdiff.
It'll
show
you,
which
of
those
files
is
called
out
where
the
code
code
quality.
A
If
there's
been
a
new
violation,
something
has
changed
in
this
file,
specifically
as
part
of
this
merge
request,
and
so
this
is
the
first
step
for
us.
This
is
our
minimum
viable
change.
Our
next
step
here
is
to
actually
get
that
annotation
in
line.
So
not
just
this
file
has
a
problem
and
going
back
and
forth
between
and
looking
at
the
widget
or
keeping
things
open
in
two
windows,
because
that's
the
experience
we
want
to
avoid,
but
actually
showing
in
line
the
annotation
of
hey
where's.
A
The
problem
here
very
similar
to
what
we've
added
with
is
there
test
coverage
for
this
or
not
you'll,
get
something
very
similar
of
what
is
the
code
quality
violation
here,
showing
the
highest
severity
thing?
First,
so
yeah
just
a
couple
of
quick
updates
things
that
I
wanted
to
show
off,
since
I
posted
that
original
video,
so
I'll
link
this
video
into
that
video
with
the
update,
so
hopefully
everyone
who's
watching
it
can
see
how
far
we've
gone
in
the
last
15
months.
Thanks.