►
From YouTube: UX Showcase: Summarize my merge request with AI
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
Designer
for
the
code
review
team
and
today
I'm
going
to
talk
about
how
we
are
using
AI
to
summarize
a
merge
request,
we
are
probably
all
familiar
with
the
merge
request
review
process
so
before
I'm,
going
into
how
we
are
using
AI.
To
summarize
a
merge
request,
I'm
going
to
give
a
very
brief
context
on
what
submerged
request
is
and
what's
the
problem
we
want
to
solve.
So,
let's
dive
into
it.
A
This
was
the
longest
merge
request.
I
ever
found
check
out
that
description.
It's
very
very
long,
and
there
is
lots
of
change
and
lots
of
comets.
So
overall
I
mean
isn't
it
what
we
want?
What
we,
what
if
we
use
AI
to
summarize
that
description
and
the
commit
change
into
a
brief
and
well
articulated
short
sentence?
A
So
we
decide
to
quickly
prototype
an
MVC
that
will
allow
us
to
test
how
useful
the
content
generated
by
AI
could
be
to
our
users.
We
used
AI
to
summarize
the
merge,
request
description
and
can
be
changed
directly
within
the
merge
request,
and
we
develop
a
quick
action
to
post
a
summary
of
changes
into
a
comment.
A
A
A
A
A
We
are
open
side
drawer
and
what
you
can
see
here
on
the
top.
We
have
a
nice
header
with
a
title
and
the
experimental
label
and
they
copied
summarize,
are
written
by
AI,
which
communicate
clearly
that
you
are
interacting
with
AI
now
moving
down.
We
have
a
summary
list
which
is
organized
in
chronological
order.
So
this
means
is
that
two
days
ago,
the
author
of
this
merge
request
committed
change
and
the
summary
was
generated
automatically
after
the
commit,
and
you
can
also
see
here
the
gray
box
that
Peterborough
reviewed
the
change.
B
A
We
are
going
to
release
this
new
experience
as
experiments
collecting
more
feedback.
Then
we're
going
to
release
this
feature
as
a
maturity
to
Beta
and
we're
going
to
do
a
solution,
validation
and
then
we're
going
to
move
this
to
GA.
If
everything
works
well-
and
this
is
this
is
what
we
we
done
with
the
AI
feature
and
I
hope
you
try
it
yeah.
Let
me
know
if
you
have
any
questions
thanks
and
I'm,
going
to
stop
sharing.
B
All
right,
thanks
Alex
for
that
I
see
that
where
the
feature
is
at
right
now
in
experiment
and
you
have
mechanisms
to
capture
feedback
and
data,
just
out
of
curiosity,
like
one
of
the
goals
of
this
feature,
was
to
save
time
in
revealing
a
merge
requests.
How
are
you
capturing
that
kind
of
sentiment,
or
are
you
capturing
that,
through
data
that
people
save
time
in
revealing
a
merge
requests?
Yeah.
A
B
B
Okay
and
the
next
question
I
have
is
about
the
the
summary:
that's
in
the
drawer
itself.
You
were
saying,
like
Peter
broth
gets
a
notification
as
well
for
the
summaries.
At
the
moment
we
get
a
lot
of
emails.
If
you
make
a
change
to
Mr,
you
kind
of
get
like
these
are
your
commits
and
then,
if
you
left
a
comment,
you
know
you're
going
to
email
on.
B
A
C
Yeah
I
just
want
to
make
sure
that
I
understand
it.
So
this
kind
of
drawer
that
you
showed
it's
like
a
little
like
mini
higher
cycle
of
the
Mr,
because
it's
like
the
Mr
was
created.
This
person
reviewed
it
now
the
Mr
is
doing
this.
This
is
kind
of
like
it's,
like
the
same
as
if
you
read
the
entire
description
and
read
every
single
comment,
and-
and
it's
just
like
is
that-
is
that
what
it's
doing.
C
A
C
Right
so
the
problem
that
you're
solving
is
the
Mr
is
created.
It
has
a
certain
description,
that's
written,
and
maybe
it
evolves
over
time.
The
description
may
not
be
accurate,
because
people
are
not
good
at
updating
description
so
coming
into
this
Mr
with
not
a
lot
of
context.
I
can
trigger
this
and
see
what
the
current
state
of
the
dish
is
in
in
kind
of
natural
language,
yeah.
A
C
C
A
B
A
You
get
a
little
bit
lost
of
who
created
and
you
know
like
what
is
the
latest,
because
it
is,
it
is
using
chronological
order,
but
it
is
a
bit
in
out
of
context
and
also
the
other
type
of
insights
we
start
to
get.
Is
that
once
people
land
into
the
merge
request,
they
read
all
the
description
and
once
they
are
already
like
funnel
families
with
it,
then
they
have
the
quick
actions
below
the
page.
A
A
Yeah
the
most
benefit
that
we
want
with
that
is
to
have
that
history
of
changes
right
like
it's,
not
that
probably
people
will
not
care
about
it.
But
maybe,
if
someone
have
like
a
question
or
or
a
different
type
of
recommendation,
they
could
quickly
see
how
that's
evolved
over
time.
So
that's
why
we
decide
to
to
have
that
history
in
place.
C
Mm-Hmm
yeah
I'm
wondering
if
this
is
all
my
assumption
a
but
like
if
the
most
current
diff
is
the
most
important,
and
you
were
talking
about
in
that
feedback
issue,
that
you
got
feedback,
that
it
could
be
a
little
bit
confusing
if
there
were
a
lot
of
summaries.
I,
wonder
if
there's
a
way
in
the
UI
to
have
like
the
hierarchy,
put
a
lot
of
emphasis
on
the
current
div.
But
then,
if
you
want,
you
can
maybe
view
the
historical
ones
as
like
with
like
Progressive
disclosure,
or
something
like
that.