►
A
Hey
my
name
is
Kenny
Johnson
I'm,
the
director
of
product
covering
our
obsession.
That's
the
verify
package,
release,
configure
and
monitor
stages
here
at
get
lab,
I'm
gonna
be
doing
a
walkthrough
this
morning
and
I
was
thinking
about
what
kind
of
walkthrough
I
should
do
and
I'll
give
some
verbalization
tips.
I'm
also
gonna
show
that
I'm
creating
my
walkthrough
issue
template
so
have
an
existing
project
that
let
me
show
my
screen
that
I
created
as
part
of
a
udemy
course
about
github
CI
that
I
recently
took,
and
this
is
a
static
website.
A
It
uses
the
Gatsby
content
creation
same
work,
I
have
a
existing
give
up,
see
IMO
file,
I
thought
what
I
would
try
to
do.
Is
this
is
kind
of
progressively
deploying
any
time
I
have
a
merge
to
master?
It
immediately
deploys
a
new
version
of
the
site.
I
was
thinking
about
switching
that
to
a
kind
of
more
release
bound
where
every
time
I
cut
a
tag.
A
It
deploys
a
new
version
of
the
site,
so
that
will
involve
me
changing
some
of
my
mo
file
and
then
I
thought
I'd
also
spend
some
time
setting
up
the
milestone
to
release
connections
so
that
I
could
bundle
up
a
bunch
of
issues
and
their
corresponding
merge
requests
and
then
have
those
be
kind
of
create
a
release
artifact
as
a
result
of
having
a
new
tag
natively
here
and
get
them
I'm
gonna
stop
sharing,
actually
so
yeah.
That
was
what
I
plan
to
do.
A
Sp
walkthrough
I'm,
not
creating
a
calendar,
invite
I
think
critically
lock
it
update
that
during
the
walkthrough
I'm
recording
the
video
and
I
realized
I
might
capture
notes.
So
that's
me,
section,
ops,
okay,
got
my
issue.
Recording
this
video
I've
got
my
Google
Doc
here's
my
issue
link
put
in
here:
okay,
all
right
now,
I'm
set.
So
let
me
I'm
just
gonna
share
my
whole
screen
here.
Let
me
fix
that
a
couple
windows
up
in
here:
okay,
so.
A
A
So
I
have
various
stages
of
learning
test,
build
test
review
I
have
this
deploy
template
for
deploying
review,
apps
staging
and
production
in
a
set
of
production
tests,
and
so
basically
the
deploy
staging
I
want
to
happen
on
every
merge
across,
but
the
deploy
production
I
only
want
to
happen
on
tag,
so
these
are
where
I
would
add,
only
tags
so
like
production
tests
that
wouldn't
be
master
anymore.
So
anything
in
this
yeah
see
these
deploy.
Template
is
only
running
on
master.
B
B
B
B
A
A
A
B
B
A
A
B
B
B
A
Oops
I
just
passed
yeah,
so
if
you're
not
watch
long
supposed
to
share,
but
my
problem
was
that
I
had
had
a
had
not
chosen
an
origin
because
I
have
two
origins
and
he
went
an
old
for
some
reason
on
my
on
this
Ennis
git
repository
locally
and
so
I
hadn't
chosen
one.
So
it
was
giving
me
an
arrow,
including
that
branch,
but
I
did
successfully
great
branch
and
the
merge
quest
for
adding
his
production
to
only
one
the
direction
drawn
tags.
I.
B
A
A
A
A
A
A
A
A
A
B
B
A
A
A
A
A
A
B
B
A
A
A
A
Sorry,
oh
yeah,
removing
the
production
test
from
master
and
instead
only
wanting
to
Montague,
since
that's
what
we're
doing
production
deploys
so
that
merged
and
then
we're
gonna,
look
at
this
pipeline
and
see
if
the
pipeline
actually
does
now
not
have
so
yeah.
This
is
the
merge
to
master
merged
to
master
pipeline
and
it
only
deploy
staging
does
no
longer
has
production
test,
so
that
was
successful,
no
pause
again.
A
Okay.
Well,
we
still
waiting
for
that
pipeline
to
finish,
but
while
I'm
doing
that,
I
wanted
to
show
a
UX
bug,
so
this
arrow
carrot,
I
think,
is
implying
that
there
is
other
content
over
there.
But
the
content
is
now
like
came
over
the
term
for
it,
but
it
is
reactive
to
my
page,
resize
and
and
appropriately
moving
where
it
should.
This
content
is
getting
cut
off.
It's
maybe
the
arrows
minced
to
remind
me
that
I
can
scroll
this
way,
but
I
would
have
thought
the
arrow
was
gonna.
A
The
other
thing
I
noticed
is
that
this
kind
of
always
stays
like
that.
I,
don't
know
what
like
that
carrot
is
staying
there,
but
I
had
made
a
comment
in
my
notes
earlier
that,
like
it
was
difficult
for
me
to
tell
what
kicked
off
a
pipeline
and
might
be
nice
instead
of
seeing
the
trigger
er
to
have
what
triggered
it.
I
noticed
that
we
have
these
tabs
up
at
his
hops.
That
can
give
me
like.
Let
me
show
me
the
pipeline's
from
branches
and
only
show
me
pipelines
from
tanks,
so
that
helps
me
figure
out.
A
A
A
A
Various
different
updates
in
staging
first
of
stuff,
that's
merged
master
versus
stuff.
That's
not
tagged
when
stuff
is
when
when
the
repo
is
tagged,
then
a
new
tag
will
update
the
production
site
with
any
commits
that
have
happened
since
the
last
tag,
and
those
would
be
there
will
be
points
in
time
where
production
and
staging
differ,
because
we
have
not
tagged
the
site.
B
A
A
Oh,
no,
that's
not
the
right
line.
Let's
look
at
this
pipelines
again
and
I.
There's
a
way
for
me
to
see
only
ones
running
on
tags.
That's
this
one!
Let's
go!
Oh
yeah!
That's
right!
Three
jobs!
Only
expecting
two
and
I
forgot
I
added
the
test.
Okay,
so
it's
got
build,
deploy
to
production
and
then
do
production
tests
on
time.
Those
are
the
three
jobs
I
wanted.
Hopefully,
production
deploy
will
work
now
that
I
have
the
build.
A
A
B
A
A
B
B
B
A
I'm
pointing
that
out
because
I'm
it,
because
it's
a
generic
message
about
artifact
download,
it's
telling
me
that
it's
got
to
be
like
a
get
lab
written
message,
sometimes
the
what
you're,
seeing
in
these
pipeline
most
the
time
while
you're
seeing
and
these
pipeline
logs
are
as
fine
as
far
as
are
like
the
result
of
shell
script
execution.
That
was
part
of
the
pipeline
or
part
of
the
job
definition.
But
this
downloading
artifacts
section
has
got
to
be
coming
from
get
lab
itself.
Some
okay,
that's
exceeded!
A
That
was
great,
so
we've
got
there's
no
new
content
here,
I
think
I'm
all
set
up.
Let's
go
back
so
just
reminder
what
we
did
was
we
started
with
a
a
pipeline
that
was
pushing
to
production
on
every
merge
to
master
and
we've
adjusted
that
to
no
only
push
to
production
on
merges
on
tags,
so
we
can
have
multiple
merges
to
master
that
will
automatically
deploy
to
staging
and
then,
if
we
want
to
deploy
to
master,
we
do
a
tag
and
kind
of
like
a
release.
So
the
next
thing
I
wanted
to
do
was.
A
A
So
there's
an
API
like
this
releases.
Documentation
I
still
will
to
create
a
get
tag
at
the
moment
of
a
released,
introduce
check,
plan
your
source
code
history,
but
it
must
gives
us
your
users
will
need
how
the
objects
was
released.
Our
way
to
track
deliverables
in
your
project.
There
are
a
snapshot
in
time,
use
semantic
versioning.
We
write
a
release,
description,
it
comes
with
assets
and
source
code.
You
can
get
permalinks
to
them.
I
want
to
associate
a
release
with
the
milestone.
A
A
A
If
I
want
to
do
that
post
fact,
I
want
to
release
with
no
tag
and
then
tag
a
release
at
some
later
dates.
Maybe
I
was
just
try
this.
If
I
go
to
releases,
I
have
some
releases
that
were
created
from
tags.
So
maybe
maybe
the
logic
is
every
time
you
create
a
tag.
It
creates
a
release
and
every,
but
you
can
create
a
release
without
a
tag.
So,
let's
see,
if
that's
true,
so
ok
great
release,
great
from
master.
A
A
A
A
A
A
Those
examples
were
just
a
little
bit
confusing
because
they
were
showing
examples
where
there
was
still
these
examples
where
there
as
a
tagged
release
but
like
no
burned
down.
So
you
wouldn't
expect
there
to
be
open
issues
in
a
and
no
merged
issues
in
a
milestone,
tagged
to
a
release,
because
the
release
happens
at
the
end
of
the
milestone
and
I.
Think
that's
maybe
what's
confusing
me
and
it's
like
percent
complete
I'm,
not
even
sure
why
we
would
show
that.
A
A
A
A
B
A
By
far
hey
come
in
I've
got
my
changes.
Stage-Dive
gonna
commit
that
date.
The
title
had
already
created
me.
A
branch
I'm
gonna
just
commit
to
that
branch
and
I
can
go
back
and
look
at
my
merge
request
and
again,
let's
make
sure
that's
changes
right.
It's
by
far
the
best
yeah
I
was
looking
for.
I
got
a
pipeline
I'm
going
to
resolve
the
whip
and.
A
A
Yeah
should
I
what
I
do
I
want
to
merge
them.
So
I
want
to
see
both
the
merge
request
pipeline
run,
which
would
create
a
review
app
and
then
I
want
them
that
emerged
to
master
pipeline
and
hopefully
that
deploys
to
staging
and
then
I
can
check
out
my
staging
ones
before
I
tag
my
release
and
that
will
push
up
production
to
play.
So
I'm
gonna
pause
by
wait
for
those
pipelines
to
run
just
go
over.
My
pipelines
pages
probably
wait.
A
A
Again,
it's
not
something
I'm
done,
while
I'm
waiting,
so
this
is
I,
was
on
the
milestone
page.
This
page
has
a
burn
down
chart
which
there's
only
a
dot,
because
it's
not
level
time
going
on
in
this
window
and
I
don't
have
issues
moving
through
the
process,
but
it
did
show
me
merge
requests
in
this
milestone
based
view,
and
it
tells
me
that
there
are
two
created
for
this
work
that
they're
open
and
unassigned,
and
it
says
that
there's
like
add,
there's
a
difference
between
them
being
open
and
unassigned
and
being
open
and
assignment.
A
A
A
A
This
work-in-progress
might
just
be
better
to
determine
their
use
like
is
it
listed
as
whip
and
when
it's
not
listed
in
wit,
then
it's
waiting
for
merge
whether
or
not
it's
assigned
or
not.
In
this
case,
those
M
ours
are
not
in
whip
assigned
still
open,
their
pipelines
are
running
participants.
I
didn't
see
that
so
I'm
a
participant,
probably
because
I
had
an
issue.
That's
pretty
cool.
Let's
see
who's
a
participant
in
a
milestone,
burn
down
chart
to
open
issues.
A
A
It's
all
automatic
marriage,
so
let's
just
wait
for
one
pipeline
around
and
then
I
want
to
see
that
should
close
the
attached
issue.
So
this
one
is
not
going
to
run.
That
is
the
add
family
and
friends
but
update
the
title.
Should
when
this
merges
so
there's
it's
open,
there's
a
active
might
request
for
this
issue.
It's
running
the
deploy
and
I
set
it
to
merge.
One
pipeline
succeed
so
not
using
the
deploy
app,
but
we
can
use
the
deploy
on
the
other
one.
A
B
A
A
A
A
A
A
A
A
A
B
A
A
A
A
A
B
A
A
B
A
A
A
What
I'm
going
to
be
you?
It's
just
ignore
that
for
now,
I'll
write
that
I
didn't
get
a
review
up.
Part
of
my
intent
here
was
showcase
that
I
had
issues
in
multiple
states.
I.
Look
at
my
plans
again,
so
I
wonder
of
any
running
pipelines.
I
have
some
finished
pipelines
for
I
added
the
tybone.
This
was
when
it
merged
to
master,
and
part
of
this
was
deploying
to
staging
so
I
updated.
The
title
reminder
and
I
have
a
production
website.
That
has
a
title
that
says
this
is
the
best
title
and.
B
A
A
A
A
A
A
B
A
B
A
A
A
A
A
A
We
have
fish
pipelines.
Let
me
show
you
one
that
recently
finished.
This
was
the
master
to
update
and
deployed
staging
summer,
we're
adding
family
and
friends.
Production
site
still
says
this
is
the
best
title
ever,
but
this
one
says
hi
friends
and
family
okay,
so
we've
got
our
two
changes
that
we
wanted
in
staging
they're
sitting
there
now
I
know
that
if
I
create
a
tag,
I
will
cause
a
new
deployer
production,
which
is
great.
A
A
A
Okay,
so
I
created
that
shows
up
in
my
releases,
but
releases
basically
just
created
a
tag
for
me.
I
think
it
did
much
more,
not
feel
like
my
pipelines
had
pipe
lines
up,
but
I
can
see
that
I
should
have
a
tag
pipeline
as
running
from
that
second
tag
for
1.2
it's
building,
hopefully
it
deploys
and
then
I
would
go
to
see
that
in
production
now
I
was
looking
at
how
to
associate
milestone
with
the
release
you
have
to
use
the
API.
You
need
to
call
this
update,
release
API,
endpoint
and
put
a
new
milestones.
A
A
A
A
A
A
A
B
B
A
A
A
A
B
B
A
B
B
A
A
A
A
A
If
I
look
at
my
tags,
I
can
want
a
question
whether
or
not
my
tag
is
going
to
have
everything
new
when
I
look
at
I
was
gonna.
Show
me
commits
that
word,
the
Delta
or
just
yeah,
so
that's
all
commits
not
just
the
ones
that
were
a
part
of
that
were
new
from
that.
Since
that
tag,
let
me
see
if
I
guess
I
look
at
an
older
one.
It
won't
show
me
the
most
recent
ones
that
makes
sense,
but
it's
like
a
full
tag.
Full
commit
history,
not
since
the
last
tag.
A
How
much
I
guess
can
make
sense
if
you're
not
necessarily
always
doing
sequential
tagging
and
what
else
might
release
page
I
want
to
look
at
the
main
page
shows
that
I
have
three
releases.
Three
tags
jump
straight
into
my
releases.
Okay,
so
I
will
create
I'll,
stop
the
recording,
I'll,
create
issues
and
post
this
thanks.
Everybody.