►
From YouTube: GitLab 13.7 Kickoff - Create:Code Review
Description
Kickoff for Create:Code Review
Code Review Category Direction: https://about.gitlab.com/direction/create/code_review/
Editor Extension Category Direction: https://about.gitlab.com/direction/create/editor_extension/
Code Review 13.7 Planning Issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12761
Epics:
- Reviewers for Merge Requests: https://gitlab.com/groups/gitlab-org/-/epics/1823
- Merge conflicts in diffs: https://gitlab.com/groups/gitlab-org/-/epics/4893
- Merge Request Reviews in VS Code: https://gitlab.com/groups/gitlab-org/-/epics/4607
Features:
- Merge request file order consistency: https://gitlab.com/gitlab-org/gitlab/-/issues/26552
- Custom commit message in suggested changes: https://gitlab.com/gitlab-org/gitlab/-/issues/25381
- Click and drag for multi-line comments: https://gitlab.com/gitlab-org/gitlab/-/issues/280608
- Changed files in MR (VS Code): https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/263
- Changed files diff (VS Code): https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/264
A
Hi,
my
name
is
kai
armstrong
and
I'm
the
product
manager
for
the
code
review
group
in
the
create
stage
here
at
gitlab
code
review
is
a
brand
new
group
and,
while
we're
here
today
to
talk
about
13.7
in
the
kickoff
and
what
we've
got
planned,
I
do
want
to
take
a
brief
moment
and
talk
about
code
review
and
what
this
new
group
means.
So
let
me
share
my
screen.
A
So
code
review
group
is
going
to
be
focused
on
two
main
categories.
The
first
one
is
the
code
review
group.
That's
long
been
part
of
source
code.
This
will
allow
the
code
review
team
to
go
and
build
on
top
of
those
features
and
continue
building
on
that
lovable
experience
that
we've
already
got
with
a
dedicated
focus
of
a
product
manager,
product
designer
and
engineering
team.
A
The
reason
the
code
review
group
will
be
taking
this
on
is
the
one
of
the
primary
things
that
the
editor
extension
categories
focus
on
right
now
is
completing
merge,
request,
reviews
inside
of
vs
code,
so
we'll
talk
about
that
in
the
13.7
kickoff
we've
got
some
upcoming
features
there,
but
let's
dive
in
to
the
rest
of
13
7
and
what
the
code
review
group
will
be
working
on.
So
you
can
take
a
look
and
see
I'll
link
this
planning
issue
down
below
in
the
video.
A
This
will
just
show
you
what
we've
been
talking
about,
how
we've
been
planning
and
some
of
the
other
things
we're
evaluating
and
looking
at
this
is
the
board
I'll,
also
link
this.
This
has
a
number
of
issues,
some
of
our
feature,
issues
that
we're
building
as
well
as
you
can
take
a
look
and
see
bugs
and
ux
improvements
and
other
opportunities
that
we're
looking
at
here.
A
So
the
first
thing
I
want
to
start
with
is
merge,
request
reviewer.
So
in
thirteen
five
and
thirteen
six
we
were
working
on,
merge,
request
reviewers.
This
has
a
new
field
to
merge
requests
that
allows
you
to
assign
a
reviewer
to
the
mr,
and
so
this
is
independent
of
the
assignee
and
clearly
indicates
that
this
person
will
be
reviewing
and
likely,
approving
and
doing
other
things
for
that.
Mr
so
we've
been
working
on
that
in
13,
5
and
13
6.
A
A
These
were
scheduled
for
13.6
and
we
think
they'll
ship
very
close
to
the
end
of
13.6,
but
we're
not
confident
enough
to
have
those
on,
and
so
we
think
that
this
will
delay
the
entire
reviewer
feature
until
13.7
and
give
us
a
little
bit
more
time
to
do
this
in
13
or
test
this
over
the
course
of
13
7
before
enabling
that
by
default.
So
I
just
wanted
to
bring
that
back
around.
As
I
know,
we've
talked
a
lot
about
reviewers
previously,
and
so
this
puts
this
here,
they're
also
working.
A
A
The
other
thing
that
the
code
review
group
has
consistently
been
working
on
is
using
merger
quest
using
merge
rest
for
disks,
and
so
this
changes
the
comparison
from
the
base
when
the
you
know
when
the
branch
was
originally
created
to
the
head.
So
with
the
current
state
of
the
branch
that
you're
merging
back
into
is
the
work
for
this
has
largely
been
done,
and
you
can
currently
do
this
inside
of
a
merge
request.
Now.
A
This
is
the
the
comparison
option.
What
we
need
to
work
on
in
order
to
remove
some
of
the
other
options
is
improving.
The
way
we
handle
merge
conflicts,
part
of
switching
to
comparing
against
the
head.
Is
that
you're
more
likely
to
see
merge
conflicts,
and
so
we're
going
to
be
working
on
some
of
the
cases
of
conflicts
and
how
we
detect
those
and
making
sure
that
you
can
deal
with
those
very
quickly
and
easily
inside
of
the
merge
request.
So
you
can
get
those
resolved
and
get
your
merch
request
on.
A
So
that's
what
we'll
be
working
on
in
thirteen
seven
there's
a
number
of
issues
in
this
epic.
I
will
link
this
I'll
link
everything
else,
but
I'll
link
this
epic
and
you
can
see
sort
of
the
ones
that
we're
gonna
be
targeting
for
thirteen
seven
we're
mostly
through
this.
We
expect
this
to
be
thirteen
seven
potentially
into
thirteen
8
and
then
we'll
be
able
to
clean
up
that
code
and
and
simplify
that
experience.
A
One
of
the
things
that
you
can
look
at
is
sort
of
something
like
this,
where
it's
sort
of
hard
to
understand
the
the
nesting
of
these
files
and
how
that
works.
Where
more
consistently
you
might
see
files
and
then
folders
when
you
have
that
viewing
experience
so
we'll
be
taking
a
look
at
that
in
137
and
hope
to
make
some
improvements
to
that
area,
to
make
it
easier
to
scroll
down
the
file
tree
list
and
down
the
diffs
and
get
a
consistent
experience
evaluating
those
one
of
the
other
things.
A
We're
going
to
be
working
on
in
13.
7
is
a
custom,
commit
message
when
applying
a
suggested
change,
so
suggested
changes
exist
in
merch
requests.
They
allow
you
to
propose.
You
know
a
change
to
the
lines
that
you're
that
you're
reviewing
and
and
make
that
change,
and
we
apply
a
default
commit
message.
The
problem
with
that
commit
message
is,
it
doesn't
sometimes
doesn't
follow,
commit
standards
for
the
project,
and
so,
if
that's
the
case,
then
you
can't
even
use
these
suggestions
in
your
project
because
we
wouldn't
match
your
commit
standards.
A
The
last
thing
we're
doing
is
making
an
improvement
to
multi-line
comments
inside
of
the
merch
request.
So
currently
you
can
make
a
multi-line
comment
inside
of
a
merge
request
by
toggling
a
drop
down
and
selecting
which
line
numbers.
The
comment
applies
to
we're
going
to
be
adding
the
ability
to
select
the
comment
icon
and
drag
down
in
13
7,
and
that
will
allow
you
to
make
a
comment
about
that
group
of
lines
versus
just
kind
of
one
line
at
the
end
or
trying
to
deal
with
that.
A
A
So
that's
what
we're
working
on
in
code
review
in
the
typical
spaces
that
you're
used
to
in
the
merge
request.
I
want
to
bring
you
into
the
vs
code
extension
now
and
talk
about
what
we're
doing
here
so
inside
of
vs
code.
We've
already
got
the
ability
to
see
merge,
requests
and
issues
inside
of
there.
You
can
leave
some
comments
and
do
some
other
things
in
13
6.
A
We
worked
on
a
proof
of
concept
that
allowed
you
to
explore,
emerge,
requests
and
see
the
diffs
without
having
to
check
that
out
and
do
any
of
those
things
I'll
link
this
epic
down
below.
You
can
see
some
results
here.
There
was
also
a
proof
of
concept
and
we'll
quickly
kind
of
open
this
up
and
what
you
can
see
in
the
proof
of
concept.
Is
that
sorry
about
that?
A
There
will
be
able
to
do
comments,
but
right
now
we're
sort
of
just
viewing
notes,
so
in
137
we're
going
to
continue
building
on
this
and
adjusting
the
current
file
tree
and
vs
code
to
what
you
just
saw
on
that
proof
of
concept,
and
so,
as
you
look
at
merge,
requests
in
a
project.
You'll
now
see
a
description.
You'll
see
the
file
tree
and
you'll
see
all
the
files
that
are
included
in
that
merge
request,
and
so
this
will
be
a
really
nice
way
inside
of
vs
code
to
get
a
sense
of.
A
What's
in
that
merge
request
and
what
you
need
to
be.
Looking
at
the
other
item,
we're
going
to
be
doing
is
showing
the
diffs,
and
so
once
you
get
to
this
file
tree
view
that
we
saw
back
here
if
you
click
on
one
of
these
files,
we'll
open
up
the
diff
for
you
right
there
in
the
editor
and
you'll,
see
sort
of
what's
changing,
what's
new
in
that
file.
So
these
are
the
first
steps
that
we're
taking
to
get
to
a
point
where
you
can
complete
a
merge
request
review
inside
of
vs
code.
A
A
So
that's
what
we
have
going
on
for
13.7
inside
of
the
code
review
group.
Like
I
said
it's
a
new
group,
I'm
going
to
link
stuff
down
below.
If
you
have
any
feedback
for
these
items
or
other
items,
issues
will
be
there.
Please
feel
free
to
reach
out
to
me
and
I'm
really
excited
about
13
7..
I
think
it's
going
to
be
an
awesome
release.
I'm
really
excited
about
the
new
focus.
We've
got
so
I
hope
you're
just
as
excited
as
we
are,
and
thanks
for
watching.