►
From YouTube: Enablement:Global Search - GitLab 14.3 Kickoff
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
So
in
143,
going
through
the
design
pipeline
right
now
and
and
soon
to
be
a
feature
that
will
be
released,
but
not
in
143,
but
the
design
work
is,
is
the
ability
to
reference
blame
inside
of
code
search?
A
Get
blame
is
so
important
to
the
use
case
of
why
code
search
really
does
add
value,
and
even
though
this
this
link
is
just
going
to
take
you
out
to
the
blame
page,
it
does
add
a
lot
of
extra
reference
and
starts
to
set
the
stage
to
understand
how
commonly
a
feature
like
this
is
going
to
get
used
or
or
be
the
intent
of
a
particular
search,
doing
code
search.
A
We
we
hope
to
do
a
lot
more
with
the
type
of
information
that
comes
back
and
is
available
from
both
history
and
blame,
but
at
this
point
we're
going
to
try
to
just
provide
the
link
and
see
how
much
it
gets
interacted
with
the
next
piece
that
we
are
also
designing.
This
is
going
to
be
really
important
for
a
lot
of
people
that
are
using
search
and
are
used
to
doing
issue
searches
using
the
issue
list.
A
We
are
adding
labels
into
the
ability
to
facet
in
global
search,
so
this
is
not
going
to
be
in
143,
but
we
are
doing
the
design
work
for
this
in
preparation
for
this
coming
up
in
a
future
release.
This
is
just
one
of
the
interpretations
that
we're
looking
at
and
kind
of
testing
through
to
see
how
this
would
function
and
and
look
at
different
things.
We
would
need
to
solve
with
it
the
the
kind
of
interesting
piece
anytime.
A
You
add,
a
facet,
we're
also
going
to
change
the
layout
of
search
results
so
that
we
can
add
in
this
case
and
the
bubble
for
the
label.
So
you,
you
have
context
to
the
results
that
are
there
with
the
information.
That's
coming
back
from
the
facet
and
that's
not
the
only
time
we've
made
these
changes
again.
This
is
just
for
design
work,
but
we
are
now
delivering
not
just
indesign
the
ability
to
sort
by
popularity.
A
It
is
not
necessarily
easy
to
browse
through
right
now
and
in
global
search,
we're
going
to
be
providing
something:
that's
more
algorithmically
driven
for
a
score
so
that
this
hopefully
adds
a
lot
more
value.
When
you,
when
you're,
actually
seeing
the
results
and
projects
that
come
back,
they
are
oftentimes.
We
notice
that
projects
get
named
very
similar.
A
That
means
that
trying
to
even
notice
the
difference
among
them
in
a
list
can
be
difficult,
but
hopefully
the
adding
some
details
in
for
the
algorithmic
scoring
is
going
to
help
out
a
lot
in
this
issue.
You
can
even
see
some
of
the
details
on
where
we're
currently
at
with
the
logic
that
we
want
to
provide.
A
So
moving
into
reliability
and
performance,
this
is
a
big
topic
for
us.
We're
really
focused
on
trying
to
improve
overall
performance
across
kit
lab,
specifically,
my
focus
in
global
search
is
areas
that
we
have
noticed
are
hot
spots.
Most
of
this
comes
from
our
understanding.
This
happens
in
sas,
but
it
would
not
be
necessarily
limited
to
the
values
that
these
things
can
create
for
all
all
of
our
customers.
A
This
particular
issue
that
we
had
found
has
to
do
with
when
you're
doing,
project
searches
and
the
fact
that
post
escrio
counts
when
requested,
actually
create
a
it,
can
create
a
large
amount
of
of
hit
to
to
postgres
and
we're
gonna
change.
The
way
that
we
actually
do
these
counts
so
that
they
are
easier
to
you
know
not
not
take
as
many
resources
to
actually
use.
A
Also,
with
counts
counts
are
difficult,
sometimes,
so
we
we
have
in
our
controller
for
the
search
count
controller
for
count.
It's
been
called
out
that
we
do
see
some
poor
performance
from
time
to
time
with
it.
We
think
we
have
a
pretty
solid
solution
that
should
improve
this
quite
drastically,
and
this
should
also
be
complete
and
available
in
14.3
nothing's
going
to
be
needed
from
you
know
the
implementation
side.
These
are
just
going
to
be
performance
improvements
that
you'll
just
see
after
the
upgrade.