►
From YouTube: Searching GitLab repositories with Git file history and Git blame (for non-technical users)
Description
Learn more about searching GitLab like a pro: https://about.gitlab.com/handbook/tools-and-tips/searching/
You can search repositories in GitLab for changes using Git file History and Git blames.
https://docs.gitlab.com/ee/user/project/repository/git_history.html
https://docs.gitlab.com/ee/user/project/repository/git_blame.html
Git file History provides information about the commit history associated with a file, while a blame provides more information about every line in a file, including the last modified time, author, and commit hash.
A
Hey
all
this
is
Darrin
at
gate.
Lab,
Jacqueline
and
I
were
on
a
media
interview
today,
and
the
question
came
up:
when
did
we
switch
from
hangouts
to
zoom
and
so
immediately
I
thought?
Well,
there
has
to
be
a
handbook
change
where
we
swapped
out
the
term
hangouts
for
zoom.
That
would
give
me
a
decent
indication
of
what
had
happened.
I
was
able
to
dig
up
a
commit
from
three
years
ago.
It
took
about
a
minute
of
searching,
maybe
and
Jacqueline
said
Wow.
A
How
did
you
find
something
from
three
years
ago
so
quickly,
and
so
I
wanted
to
make
a
quick
video
to
show
people
how
I
use
get
history
and
getting
blames
to
find
anything
and
everything
that
has
ever
changed
in
the
gitlab
handbook
and
it's
it's
amazing
from
a
documentation
standpoint,
because
it
gives
you
a
timestamp
when
something
changed
which
which
then
you
can
compare
to
whatever
time
it
was
in
history.
You
can
get
context
on
what
else
was
happening
in
the
world.
What
release
we
were
on
as
I
get
lab
the
company?
A
What
other
features
we
were
working
on
at
the
time
really
great
context,
really
rich
detail,
and
this
is
corridor
wide
documentation
matters
so
much
for
us.
So
what
you're
looking
at
here
is
a
view
of
the
gate
lab
calm
repository,
which
is
where
the
gate
lab
handbook
is
found.
So
you
can
see
up
here
the
URL
to
pop
into
this,
and
so
for
my
particular
case.
What
I
was
looking
for
is
the
communications
page
in
the
handbook.
A
A
You
basically
have
to
find
the
page
you're
looking
for
first
and
then
down
to
handbook
and
it's
easy
to
find
out
what
this
tree
should
look
like,
because
if
you
just
google
the
get
lab
handbook,
communication
page
you'll
see
what
it
renders
on
the
public
web
and
then
you
can
reverse
engineer
what
those
file.
What
that
file
structure
is
so
we're
in
handbook,
and
then
communication
and
the
home
page
communication
will
be
this
index.html
D,
the
markdown
page.
A
So
now
we're
essentially
looking
at
the
gate
lab
communication
page
within
the
Hamlet,
as
it
is
current
today
now
there's
two
buttons
here
at
the
top
that
are
of
interest.
One
is
blame,
and
one
is
history,
so
we'll
dig
into
history.
First,
if
you
click
history
here,
it's
going
to
take
you
into
the
historical
look
of
this
page,
and
you
can
see
here
in
the
file
tree
exactly
where
you
are.
A
So,
if
you
wanted
to
change
this
to
a
different
page,
just
go
find
a
different
page
and
then
click
the
history
and
then
you'll
be
in
now.
This
is
a
chronological
view
of
the
commits
that
were
made
to
this
page,
so
you'll
see
one
was
made
on
June
3rd
June,
2nd
a
couple
May
30th,
so
on
and
so
forth,
and
so
this
Scrolls
all
the
way
back
and
you
can
scroll
for
a
very
long
time
and
see
all
of
the
commits
that
were
made
to
this
page
now.
A
What
I
first
did
here
is
I,
went
to
this
search
box
and
typed
in
zoom,
and
it
brought
up
some
commits
and
then
it
stopped
at
2017.
So
this
was
around
three
years
ago
and
I
thought.
Well,
maybe
that's
my
answer,
or
maybe
it's
just
not
searching
back
far
enough.
So
as
a
secondary
data
point
I
wanted
to
see
if
I
could
find
anything
further
by
going
to
the
Blane.
So
we'll
go
back
to
the
overall
index
page
here.
I
see
we're
in
commits
so
pop
back
out
to
here.
A
A
So
once
you're
back
on
this
repository
page,
you
can
click
the
other
button
beside
history,
which
is
blame.
Now
a
blame
is
a
way
to
look
at
when
the
last
time
any
given
line
of
code
in
the
repository
was
changed.
So
you'll
see
here
how,
in
the
blame
view,
every
single
line
line,
1
line,
2
line,
3
so
on
and
so
forth.
They
have
an
Associated
blame
beside
it,
so
you
can
literally
go
line
by
line
on
an
entire
page
and
figure
out
what
the
last
related
commit
was
to
that
line.
A
A
I
went
here
and
now
I'm
taken
back
in
time
and
you'll
see
a
bunch
of
commits
that
are
lined
up
here
from
3
years
ago,
so
I
clicked
on,
and
so
I
noticed
this
first
one
was
3
years
ago
and
it's
at
line
1.
So
that
gives
me
an
indication
that
the
page
was
actually
created
in
this
commit
three
years
ago.
So
I
go
to
this
commit
and
sure
enough.
You
can
see
right
here.
This
communications
index.html
click
to
expand.
It's
all
brand
new.
A
All
of
this
is
in
green,
which
means
it's
all
in
net
edition.
So
what
I
determined
here
was
this
page
was
created
in
its
current
position
by
this
commit
three
years
ago
now.
This
doesn't
necessarily
mean
that
we
switched
from
hangouts
to
zoom
three
years
ago.
It
could
have
been
that
the
referral
to
hangouts
was
in
a
different
place
in
the
handbook
three
years
ago
and
I
just
don't
know
where
to
look
as
a
third
data
point.
A
What
I'm
gonna
recommend
is
going
to
the
random
Channel
and
then
asking
if
there's
anyone
that's
been
around
and
get
loud
long
enough
to
remember
around
the
time
that
we
switched
from
hangouts
to
zoom,
and
that
would
be
a
nice
third
data
point.
But
you
can
at
least
use
this
to
get
somewhat
close
to
figuring
out
when
something
changed
and
that'll
give
you
some
contextual
history
around
that.