►
From YouTube: GitHub code search - Universe 2022
Description
Presented by: Colin Merkel, Sr. Engineer, Code Search
Showing off the power of the all new GitHub code search, Colin Merkel will talk about a new way to search, navigate and understand the world's code.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
You
know
our
mission
at
GitHub
is
to
build
tools
to
make
developers
happier
and
more
productive
and
I'm
a
huge
believer
in
the
capability
of
great
tools
to
make
a
difference
in
the
lives
of
Developers,
for
example,
code
spaces,
which
lets
developers
forget
about
setting
up
their
local
machine
and
jump
right
into
the
code
using
the
cloud
or
co-pilot
which
helps
developers
write
code
using
AI,
but
developers
don't
just
write
code.
They
read
it
reading
and
understanding
code
is
a
hugely
important
task
if
you're
a
developer.
A
A
Luckily,
developers
are
incredibly
good
at
finding
the
information
they
need
to
do
their
job,
whether
it's
out
there
on
the
internet
on
a
forum
or
in
documentation
developers
will
find
it,
but
a
lot
of
the
time.
The
answer
is
not
out
there
on
the
internet
a
lot
of
the
time
the
answers
developers
need
are
buried
within
the
code
and
that's
why
we've
built
the
new
GitHub
code
search
to
help
you
search,
navigate
and
understand
not
only
your
code,
but
your
team's
code,
your
company's
code
and
the
world's
open
source
code.
A
In
December
of
last
year,
we
launched
our
code
search
technology
preview
over
a
hundred
thousand
developers,
joined
the
waitlist
and
gained
access,
giving
us
tons
of
valuable
feedback
developers,
love
the
ability
to
instantly
find
relevant
code,
use
our
powerful
code
navigation
and
dig
through
large
and
complex
code
bases
and
for
many
developers,
GitHub
code
search
became
an
essential
part
of
their
workflow,
something
they
depend
on
every
day
to
find
answers.
They
need
to
do
their
job.
A
We
knew
we
had
to
bring
this
tool
to
all
Developers
and
that's
why
today
we're
bringing
three
powerful
new
capabilities
to
github.com
first
is
an
entirely
new
search
interface,
allowing
developers
to
construct
powerful
queries
with
suggestions,
completions
and
the
ability
to
slice
and
dice
the
results.
The
second
is
our
entirely
new
code
search
engine
capable
of
searching
and
even
understanding
code
to
bring
you
relevant
results
with
Incredible
speed,
and
the
third
capability
is
an
entirely
redesigned
code
view
which
tightly
integrates
search,
browsing
and
code
navigation,
allowing
developers
to
rapidly
Traverse
their
code
to
find
answers.
A
A
A
Now,
let's
imagine
that
I
forgot
the
name
of
a
script.
At
GitHub
we
use
an
RPC
Library
called
twerp
and
I
know.
One
of
my
teammates
wrote
a
script
to
send
a
request
from
the
command
line,
but
I
forgot,
the
name
and
even
which
repository
it's
in
I'll
search
across
all
of
my
team's
code
for
language,
shell
and
twerp.
A
There
it
is
I
can
jump
right
to
it.
Okay,
I'll
try
searching
now
for
a
symbol
in
my
code
base
and
now
you
can
see
the
all-new
search
results.
Interface.
We've
redesigned
the
search
interface
to
make
it
super
easy
for
developers
to
find
exactly
what
they're
looking
for
on
the
left.
I
can
filter
my
results
by
language
repository
or
even
file
path.
A
I
searched
for
the
term
query
stats,
which
is
the
name
of
a
struct
in
one
of
my
repositories
and
notice
that
the
definition
is
actually
the
first
result.
That's
no
coincidence.
Github
code
search
actually
understands
your
code
and
brings
you
the
most
relevant
results.
First,
we've
also
put
a
lot
of
work
into
making
our
query
language
super
powerful.
We
even
support
Boolean
expressions
like
and
or
and
not.
For
example,
let
me
try
to
search
for
all
of
the
code.
That's
either
in
markdown
or
ends
with
txt.
A
A
I
think
you
can
see
how
a
powerful
query
language
might
unlock
tons
of
possibilities
for
developers
to
find
exactly
what
they're
looking
for
now
a
powerful
query.
Language
is
one
thing,
but
another
thing
I'm
super
proud
of
is
how
fast
our
code
search
is
I'm,
going
to
search
across
all
of
github's
code
for
the
regular
expression,
git.star
push.
A
And
in
just
a
couple
seconds,
we
found
over
a
Million
results.
Think
about
that.
We
just
use
a
regular
expression
to
search
over
billions
of
files
of
code.
That's
only
possible
because
we've
built
the
new
code
search
from
the
ground
up
with
a
focus
on
performance,
so
developers
can
find
exactly
what
they're
looking
for
and
find
it
quickly.
A
Okay,
I've
shown
you
the
new
search
interface,
where
developers
can
construct
powerful
queries
and
our
totally
new
code
search
engine
which
finds
relevant
results
with
Incredible
speed,
but
that
alone
is
not
enough
for
developers
to
search,
navigate
and
understand
large
code
bases.
There's
one
more
missing
piece
of
the
puzzle
and
that's
the
code
view
we
knew
from
the
technology
preview
that
finding
the
right
search
result
is
just
the
beginning
of
the
journey.
A
Developers
need
to
search,
browse
and
navigate
code,
find
definitions
and
references
and
trace
the
path
of
the
code
through
their
code
base,
and
that's
why
we've
redesigned
the
code
view
from
the
ground
up
until
today.
This
is
what
the
code
view
looks
like
Pages
hardly
changed
since
GitHub
was
founded.
Here's
a
screenshot
of
the
old
code
view
from
10
years
ago,
with
the
new
code
view.
We
went
back
to
the
drawing
board
and
this
is
the
result.
We've
put
the
file
Tree
on
the
left
side
pane.
A
This
gives
developers
context
and
allows
them
to
quickly
find
related
files
in
the
same
directory
in
the
middle.
Of
course,
we
have
the
code
and
on
the
right
we
have
a
new
pane,
something
we're
calling
the
symbols
pain.
It's
designed
to
give
contextual
and
symbolic
information
about
the
code,
you're
looking
at
click
on
any
symbol,
and
you
can
see
its
definition
and
references
both
within
the
file
and
across
the
repository
and
even
across
multiple
repositories.
A
A
Now
that
prop
can
be
a
bit
dangerous
because
it
directly
writes
a
string
into
the
Dom
I'm,
going
to
search
across
all
the
code
in
GitHub
GitHub
GitHub,
which
is
the
code
behind
github.com
for
dangerously
set
inner
HTML
and
almost
instantly.
We
found
a
few
results
now.
This
first
result
is
a
component
called
safe
HTML,
where
we
verify
that
the
string
being
written
in
the
Dom
is
totally
safe,
but
this
second
result
looks
like
it
could
be
vulnerable.
A
Let's
dig
in
using
the
code,
View
I'll
click
on
the
results,
and
now
we
can
see
that
this
vulnerable
prop
is
being
used
on
line.
48
is
part
of
a
component
called
inner
issues.
Show
page
if
I
click
on
inner
issues
show
page
in
the
symbols.
Pane
I
can
see
its
definition
here
on
line
36
and
a
reference
in
this
file
on
line
31..
A
A
And
immediately
I
can
see
the
exact
URL
where
I
can
find
this
component
and
I
can
see
it's
part
of
the
react
sandbox,
which
is
just
an
internal
testing
ground.
So
we
know
it's
totally
safe.
What
we
just
did
was
use
code
search
to
find
all
the
examples
of
a
potentially
vulnerable.
Prop
then
dig
through
and
see
where
they're
being
used.
Security
teams
here
at
GitHub
use
code
search
to
find
all
the
vulnerable
instances
of
code
affected
by
log4j.
A
My
team
writes
a
lot
of
go
and
if
you're
familiar
with
go
go
routines
are
a
way
of
spawning
threads
and
if
you
don't
spawn
them
correctly
and
set
them
up
correctly,
they
might
not
clean
up
after
themselves.
Let's
search
across
all
the
code.
My
team
owns
for
where
we
spawn
go
routines,
I'll
search,
go
funk.
A
And
we
instantly
find
a
bunch
of
results
now.
I
know
that
a
particular
bug
is
happening
within
one
repository,
so
I'll
narrow,
my
search
into
that
one
and
I
also
know
that
this
bug
is
isolated
to
The
Crawling
system,
so
I'll
narrow
it
into
that
directory,
and
here
we
can
see
a
couple
of
results.
One
is
a
test,
but
the
other
is
production
code.
A
A
couple
weeks
ago,
my
team
used
this
exact
search
to
find
a
bugger
code.
Okay,
let
me
show
you
one
last
example:
at
GitHub
we
use
kubernetes.
Imagine
if
the
platform
team
sends
you
a
message
and
they
say
we're
running
out
of
memory
in
our
kubernetes
cluster.
How
much
are
your
services
using
and
can
they
cut
back?
A
Let's
try
searching
across
all
the
code.
My
team
owns
for
language
yaml,
because
that's
how
kubernetes
is
configured
and
memory
and
we
can
instantly
find
all
of
the
configurations
for
our
services
here.
I
can
see
two
gigabytes
of
RAM
are
being
requested
for
this
service
and
we
have
a
limit
of
five
here.
One
gigabyte
and
10.
A
I
can
send
this
link
right
back
to
the
platform
team,
so
we
can
find
Opportunities
to
save
memory.
I
think
you
can
see
why
so
many
developers
have
come
to
rely
on
code
search
every
single
day
to
find
information
buried
in
their
code,
we're
starting
our
public
beta
today.
If
you
have
access
to
the
code
search
technology
preview,
you'll
automatically
get
access
to
these
new
features
in
github.com.
A
If
you're,
not
part
of
the
preview
sign
up
to
be
added
to
the
wait
list,
so
you
can
get
started.
What
I've
shown
you
today
is
just
the
beginning.
We
truly
believe
that
powerful
code
search
is
an
essential
tool
for
every
developer,
join
our
beta
and
help
us
make
code
search
and
code
navigation
on
GitHub,
even
better
together.