►
From YouTube: GitLab 13.6 Kickoff - Enablement: Global Search
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
the
first
thing
that
we
have
in
13
6
is
an
update
to
something
that's
in
our
admin.
Ui
terry's,
going
to
take
us
through
that.
B
B
Currently
we
allow
administrators
to
do
inclusion
for
projects
and
namespaces
so
that
only
those
are
the
items
that
get
enabled
for
the
elasticsearch
feature
that
kind
of
presents
a
problem.
If
someone
has
a
lot
of
projects
and
or
namespaces
and
only
wants
to
exclude
a
few
of
them,
then
they
have
to
spend
time
adding
all
of
the
other
items
to
that.
So
we've
decided
to
allow
the
administrators
to
have
the
option
to
use
inclusive
or
exclusive
for
whether
projects
or
namespaces
get
indexed.
A
Yeah
that
makes
a
lot
of
sense
too.
That's
a
really
good
addition
to
our
admin
console
we've
been
adding
to
that
over
the
last
few
iterations.
A
So
the
next
thing
that
we're
going
to
do-
and
this
is
really
more
focused
on
some
of
our
ui
initiative-
we
have
of
actually
providing
a
more
modern
ui
for
our
search
result.
Page.
A
But
we
have
some
of
these
filters
that
are
already
available
and
we're
going
to
now
put
those
in
a
left
rail
side
where,
where
the
user
is
actually
searching
on,
us
will
be
able
to
kind
of
expand
out
and
see
what
options
are
there
without
having
to
click
on
the
drop
down
to
see
what
the
options
look
like
and
understand
what
might
be
underneath
it,
and
then
the
plan
will
be
that
we
want
to
add
more
filters
to
this
and
grow
it
with
each
iteration.
A
So
the
first
thing
that
we're
going
to
be
adding
with
this
is
our
ability
to
do
confidentiality.
So,
in
the
previous
release
we
had
added
the
status,
which
is
for
merge,
requests
and
issues.
B
Okay,
so
you
do
have
to
be
within
a
project
context.
You
could
to
do
a
shaw
search.
You
can
do
a
full
shot,
search
or
a
partial
sha
search
by
adding
the
information
up
in
the
search
bar
in
the
top
right
now,
like
I
said
you
do
have
to
be
within
the
project
itself.
You
can't
do
this
from
the
group
if
the
shot
search
is
successful
and
finds
only
one
result.
That
means
it
only
found
a
commit
and
it
did
not
find
references
within
comments
or
issues
or
emerge
requests.
B
It
will
redirect
you
to
that
result.
So
it's
kind
of
an
easy
way
for
you
to
just
jump
right
to
a
commit.
You
don't
have
to
go
and
do
the
search
first
and
then
go
to
the
commit
from
there.
If
this
hits
you
in
the
commit
and
then
you
decide
actually
I
do
want
to
go
back
to
the
search
results.
B
A
Thank
you,
terry,
and
you
know
one
of
the
really
interesting
things
about
the
search
by
shaw
is
this
may
be
one
of
our
first
issues
from
global
search
that
we
really
kind
of
came
up
with
that
wasn't
necessarily
based
on
direct
user
feedback
or
requests.
This
was
actually
based
on
us,
discovering
it
by
understanding
how
users
were
using
search,
and
we
saw
there
was
a
number
of
users
that
were
actually
searching
on
shaw's.
A
It
makes
total
sense
that
you
would
want
to
just
cut
right
to
it
and
find
you
know
that
that
commit,
but
now
we've
made
this
easier.
We've
taken
some
of
the
steps
out
of
it
by
just
sending
you
directly
to
it.
If
it's
the
only
result
that
exists
in
that
project,
so
that's
I
think,
that's
going
to
be
really
helpful.
I
think
a
lot
of
people
are
going
to
really
find
this
a
real
shortcut
to
kind
of
getting
to
what
they
need
with
these
commits.