►
From YouTube: 2020 11 02 GSoD Office Hours
Description
Google Season of Docs office hours Nov 2, 2020.
A
B
B
B
A
A
A
C
So
what
I,
what
I
would
like
xenop,
if
it's
possible
once
this
pr,
is
ready
to
go
like
everybody
has
said
that
they
approve
it
and
everything
I
would
like
if
you
could
squash,
commit
to
bring
all
of
these
commits
down
into
one,
and
that
can
sometimes
be
a
a
little
difficult.
But
if
you
need
help,
please
let
me
know
I
will
be
more
than
happy
to
help
you
do
that
essentially
go
ahead.
A
There
is
a
the
label
squash
merge
me
has
been
applied,
and
so
the
person
who
merges
it
can
just
do
that
squash
directly
beautiful,
so
the
z
knob
doesn't
have
to
xena,
but
I
assume
you're.
Okay,
if
we
squash
merge
it
that
will
whether
we'll
do
is
collapse,
all
the
commits
into
a
single,
commit
and,
and
then
okay.
A
A
So,
probably
not
if
it's
not
immediately
apparent
to
you,
probably
not
so
just
just.
We
just
have
to
remember
that
the
label
has
been
applied
now
we
need
to
honor
the
label
and
actually
do
the
squash
merge
that
avoids
you
having
to
do
it
and
it
lets
you
still
xenop
continue
this
pattern
of
small
commits
to
jews.
I
like
that
pattern.
It's
very
healthy.
A
E
A
A
C
B
B
C
B
So
you
know
in
in
this
snippet
here
I
was
using
the
file
from
the
official
repository,
but
I
like
mentioned
that
it
might
be
a
problem
if
the
master
branch
of
your
official
repository
is
renamed,
so
I
suggested
probably
replicating
the
file
and
putting
it
on
jenkins
dot
io.
So
we
can
have
control
over
more
control
over
that.
C
Thank
you
for
clarifying
that.
That's
a
lot
more
clear
to
me.
I
could
I
agree
with
that.
However,
I
would
wonder
if
it
would
be
possible
to
put
a
comment
on
the
official
repository
that
there
is
some
linkage
to
this
document
and,
if
there's
any
changes
made
there,
they
would
need
to
also
be
reflected
in
here
that
way,
the
person
that
were
making
the
changes
would
know
that
that's
just
a
possible
thinking
out
loud
suggestion.
F
E
A
B
B
C
Yes,
yes,
that
will
resolve
it.
There's
like
there's
a
hidden
link
in
github
that
you're
able
to
use
the
get
buster
hidden
links
where
you
can
pull
down
the
raw
content
of
that
okay,
but
my
concern
now
it
now.
I
understand
what
oleg
and
tim
are
saying
and
because
of
this
repo
in
particular,
I
would
be
yeah.
This
is
sort
of
a
touchy
catchy
one
right
here.
D
C
I
think
that
I
think
tim's
concern
is
specifically
to
the
operator
and
whom
control
I
don't
want
to
use.
The
word
controls
the
operator
code
base.
There's
like
a
big
there's,
a
big
thing,
sort
of
happening
with
people
getting
in
and
being
able
to
become
maintainers
of
this.
What
I
would
suggest-
and
this
is
a
more
official
suggestion-
is
xenop.
I
would
leave
line
593
as
is,
but
I
would
add,
a
comment
in
there
that
this
is
subject
to
change
and
it's
best
to
verify
like
the
repo
to
be
safe.
A
That
that
sounds
okay
to
me,
I'm
actually
a
little
concerned
that
I
think
that
this
link
right
now
is
actually
broken,
and
so
I
think
it's
going
to
be
need
to
be
revised
anyway,
and
I
don't
know
when
the
change
was
applied
that
caused
it
to
become
broken,
because
it's
not
that
these
files
have
changed
recently.
Yes,
but
at
least
I
was
expecting
that
when
I
opened
this
url
in
a
web
browser
page
that
it
would.
C
Not
404
yeah,
you
would
actually
get
the
raw,
so
that
link
is
broken,
so
z,
knob
that
has
to
be
corrected
and,
while
you're
correcting
that
I
would,
I
would
add,
a
comment
in
there
for
in
that
593.
I
would
add
a
comment.
That's
basically
says
this
repo
is
subject
to
change,
or
this
link
is
subject
to
change
and
it
would
be
best
to
verify
that
would
be
my
recommendation.
C
C
A
So
the
so
tim's
tim's
phrasing
here
apply
these
official
deploy
instructions
in
the
official
repo
yeah.
So
so
I
think
tim's
actually
objecting
to
the
idea
of
putting
examples
in
this
repo,
if
they're
conceptually
too
close
to
the
production
ex
to
the
real
examples
in
the
or
the
the
data
in
the
repository
so
he's,
I
think,
he's
buying
us
towards
not
doing
placing
examples
in
the
repo
unless
they
are
somehow
trivial
or
completely
dis.
C
Am
I
misreading
his
comment?
I
think
this
has
so
just
for
the
record
of
why
this
may
be
a
bit
of
a.
I
think
what
I
think
tim
is
bringing
up,
and
also
oleg,
is
the
maintainers
of
this
repo
in
particular.
There's
been
some
there's
been
people
have
raised
not
being
able
to
become
maintainers
of
this
specifically
red
hat,
and
my
I
think
what
the
fear
is
is
that
something
will
change
in
this.
C
We
will
not
know
or
have
any
way
to
affect
correcting
something
and
we're
kind
of
at
the
mercy
of
the
maintainers
of
this
operator,
and
I
think
that's
what
tim
is
trying
to
avoid
as
well
as
oleg.
I
could
be
completely
wrong,
so
I'm
not
speaking
that
they've
actually
told
me
that
I'm
speaking
just
sort
of
guessing,
but
knowing
some
of
the
history
with
this
particular
repository.
A
A
Okay,
because
I
think
that
would
address
tim's
concern,
it
doesn't
really
address
the
concern
that
started
us
down
this
path
from
kristin
and
I
think
from
oleg
that
hey,
we
need
a
place
to
put
examples
that
are
bigger
than
will
comfortably
fit
in
line
in
the
documentation,
yeah
cutting
and
pasting.
I
like
kristen's
example
from
a
week
ago,
cutting
and
pasting
more
than
a
page
of
text
is
problematic
and
error-prone.
C
D
F
A
B
A
D
A
A
A
D
A
Next
topic,
then,
was
the
blog
post
and
oh,
that's,
the
we've
got
the
pr
for
the
blog
post
as
well
right,
and
it
is
here
and
zenob.
I
assume
that
you're
okay,
if
we
post
this
anytime
right
so
you're,
okay,
if
I
adjust
the
date
on
this
and
if
we
were
to
post
it
today
or
tomorrow,
you'd
be
all
right
with
that.
B
A
A
A
F
F
A
B
A
A
A
Manager,
that's
excellent,
zeno.
Anything
else
that
you'd
like
to
share,
though
those
already
feel
like
large
undertakings
and
interesting
challenges
now
will
administering,
for
instance,
include
how
to
deal
with
configuration
as
code
in
a
kubernetes
environment.
What
what
sorts
of
things
are
you
envisioning
there.