►
From YouTube: How to use "view source" to find out when content on about.gitlab.com/free-trial/ was updated
Description
In this video Lauren Barker demonstrates how to use the "view source" link in the footer of the about.gitlab.com to access the content file of that page, find out when it changed, and located the merge request associated with the change.
A
So
I'm
here
on
our
free
trial,
page
on
about
gitlab.com,
it's
a
beautiful
page.
We've
got
some
tabs,
we
got
a
form,
we've
got
so
much
content
down
here
and
it's
been
internationalized.
So
now
we
have
four
versions
of
this
page
and
we
want
to
know.
When
was
the
last
time
the
Japanese
version
of
this
page
was
updated.
So
we
use
our
language
selector
down
here,
switch
over
to
the
Japanese
version
and,
let's
say
hey
I,
want
to
know
when
the
content
changed.
A
This
link
down
here
it
reads
view
page
Source,
but
I,
don't
read
Japanese,
so
I
can't
do
that
so
I'm
going
to
use
Google's
switcher
here
so
that
just
translated
all
back
to
English,
and
we
can
see
that
this
is
view
page
source
switch
that
back
to
Japanese
that's
kind
of
a
cool
cool
feature.
There
click
on
that
sucker,
it's
gonna,
pull
us
right
into
git,
lab
the
product
and
drop
us
in
to
the
content
file
for
that
page.
A
So
this
is
in
our
buyer
experience
repository
in
the
content
directory,
it's
in
the
jajp
directory
free
trial,
index.yaml,
and
this
is
the
content
file
for
that
page.
It
holds
all
of
the
content.
For
that
page,
you
can
edit
the
content
from
here.
You
can't
like
by
opening
this
and
going
to
web
it
web
IDE.
That's
one
of
my
favorite
features
or
you
can
go
up
here
and
click
on
this
history
button
and
go
see
the
entire
git
history
of
this
page.
So
we
could
see
on
April,
21st,
2023
Miracle
created
the
page.
A
It
didn't
exist
before
that.
That
was
the
Inception
of
this
page
and
we
can
click
into
that
and
it'll.
Take
you
to
the
the
commit
and
show
you
everything
that
changed
to
make
that
page
page
happen.
We've
had
couple
more
changes
since
then
we
can
see
the
most
recent
was
on
July
25th
and
TMA
fixed
up
some
GA
attributes.
We
can
see
on
July
20th.
A
She
applied
the
lqa2
marketing
site
for
Japanese
and
if
we
take
a
look
in
here
and
click
on
that,
it's
going
to
take
you
to
the
commit
and
show
you
all
of
the
changes
that
were
associated
with
that
commit
now
there's
kind
of
a
lot.
You
know
here
we're
on
the
Enterprise
page,
go
and
close
that
here
we
go
we're
on
the
content,
Japanese
free,
trial,
red,
that's
what
it
used
to
be
green
is
what
was
introduced
with
this
commit.
So
you
can
see
line
by
line.
A
It
was
a
lot
lots
of
detail
there
and
that
will
go
down
for
all
11
files
that
were
changed.
Another
cool
feature
is
you
come
up
here
to
the
top
it'll
say
one
merge
request,
give
you
a
number
and
then
it's
the
name
of
the
merge
request.
If
you
click
on
this
number
right
here,
it
takes
you
right
to
the
merge
request
and
that
it's
just
a
beautiful
interface,
where
you
can
look
at
all
the
commits
that
were
involved
with
creating
that
all
the
pipelines.
A
33,
that's
a
lot
and
there
were
11
changes
and
we
have
our
Engineers
always
explain
what
the
goal
is
all
the
pages
that
were
involved
in
this.
So
there
were
11
and
there
are
some
ga
bugs
fixed.
We
also
link
it
back
to
the
issue
and
issues
are
how
we
triage
and
work
in
an
agile
process
with
our
teams,
and
this
is
where
we
explain:
okay,
the
goal
is,
we
want
to
publish
all
the
animal
content
files
delivered
by
the
translated
team
during
lqa2
and
let's
also
address
these
functional
bugs
in
the
spreadsheet.
A
We
list
all
the
pages
that
were
involved
with
that
and
where
we
could
go
and
get
those
content
files
and
there's
some
conversation
in
there.
So
pretty
cool
stuff
and
we'll
just
end
it.
By
going
back
to
here,
we
are
on
that
Japanese
free
trial,
page
there's
that
view
page
source
and
because
these
are
all
different
versions.