►
Description
"GitHub Actions gives teams world-class CI capabilities, helping developers merge and deploy code many times in a single day. The silent power of GitHub Actions lies in its ability to programmatically define just about any workflow to mirror your team’s processes. In this workshop, you'll learn how to:
Create and use multiple, customized workflows
Implement a unit testing framework using GitHub Actions
Use multiple jobs in a workflow and pass artifacts between jobs
Configure a repository to work in conjunction with GitHub Actions workflows and your team's workflow."
GitHub Satellite: A community connected by code
On May 6th, we threw a free virtual event featuring developers working together on the world’s software, announcements from the GitHub team, and inspiring performances by artists who code.
More information: https://githubsatellite.com
Schedule: https://githubsatellite.com/schedule/
A
Hello,
everybody
welcome
to
our
first
ever
virtual,
get
up
satellite
workshop.
I
hope
everybody's
staying
safe
and
having
a
pleasant
time
and
looking
forward
for
this
workshop
today
with
us.
We're
gonna
get
right
into
it.
Thank
you
again
for
making
time
the
topic
for
today's
workshop
is
gonna,
be
about
continuous
integration
with
get
up
actions,
and
I'm
going
to
be
your
facilitator.
My
name
is
prem,
I'm
an
implementation
engineer
with
the
professional
services
team
and
to
help
with
the
moderation.
A
We
have
these
lovely
individuals.
Folks
we
have
yadav.
Who
is
a
solution
architect.
We
have
thomas
who's.
A
senior
devops
engineer
as
well
as
john
wibach
is
also
a
senior
devops
engineer
from
the
professional
services
team.
So
these
folks
are
going
to
be
kind
enough
to
moderate
any
questions
that
you
might
have
in
the
slack
channel
and
having
said
that,
let's
jump
into
today's
agenda,
so
we're
going
to
start
off
with
a
quick
overview
where
we
set
some
expectations
and
give
a
good
context
around
the
workshop
on
the
content.
A
That's
going
to
be
covered
today,
we'll
ease
into
the
core
concept
of
get
up
actions
we'll
take
a
look
at
the
different
parts
that
make
github
action.
Stick
then
we
will
dive
right
into
the
hands-on
sessions.
That's
divided
into
three
different
sessions.
We
will
kind
of
time
box
it
for
at
least
15
to
20
minutes,
depending
on
how
we
progress
and
how
good
we
are
for
time,
all
right
with
that.
Let's
start
off.
A
What
I'm
going
to
be
doing
is
I'm
going
to
build
it
up
from
a
level
200
to
a
level
300
where
we
have
a
quick
recap
on
the
foundations
and
different
parts
of
get
up
actions
where
I'll
be
talking
about
what
is
the
difference
between
a
workflow
and
action
or
the
different
types
of
actions
that's
available
and
how
you
could
visualize
or
create
a
mental
model
between
workflows
and
actions?
All
right
in
the
hands-on
exercises,
we
will
be
using
getup
actions
instead
of
building
a
github
access
from
scratch.
A
The
hands-on
exercises
will
be
guided
by
our
learning
lab
board
and
that's
going
to
be
giving
you
all
of
the
different
steps
that
you
need
to
complete.
What
I
will
be
doing
is,
I
will
walk
through
all
of
the
different
steps
and
instructions
step
by
step
before
giving
you
some
time
to
complete
it
on
your
own.
Also,
this
particular
continuous
integration
workshop
is
a
precursor
to
the
continuous
delivery
workshop
which
vrf
will
be
presenting
later
on
today.
A
He
defines
continuous
integration
as
a
software
development
practice
where
individual
team
members
would
be,
at
least
at
a
minimum,
be
integrating
changes
frequently,
at
least
for
one
time
in
a
day
that
kind
of
results
into
a
team
having
multiple
integrations,
at
least
on
a
daily
basis,
for
the
software
that
you're
going
to
be
building
right.
So
building
on
this
principle,
we
at
github
have
been
empowering
and
helping
these
big
names
or
industry
players
who
has
invested
their
trust
in
us
to
help
them
in
their
continuous
integration
and
continuous
delivery
journeys.
A
We
were
able
to
narrow
down
these
drivers
into
these
four
common
elements,
starting
with
a
common
philosophy
where
we
at
github
have
a
philosophy
that
helps
us
in
our
day-to-day
routines.
If
you
would
like
to
know
what
is
the
zen
of
github,
I
would
recommend
you
doing
a
curl
call
to
this
particular
res
api
endpoint,
that
is
on
the
screen
that
particular
curl
call.
Curl
call
is
going
to
give
you
some
information
of
something
which
you
call
zenith
zen
of
github
and
from
that
zen
of
github.
A
We
kind
of
also
dictate
on
how
we
communicate
asynchronously.
So,
for
example,
our
philosophy
on
asynchronous
communication
is
that
in
a
team
we
are
going
to
be
communicating
across
different
time
zones.
We
are
not
going
to
expect
a
reply
in
our
time
zone.
We
are
going
to
have
the
trust
that
the
team
will
be
responding
in
a
fashion
where
it's
not
going
to
block
our
delivery
or
integration
of
the
project
that
we're
going
to
be
working
on.
Along
with
the
asynchronous
communication.
A
We
also
have
automations
through
chat
ops,
that
we
do
through
slack
channels,
which
kind
of
helps
us
in
our
continuous
delivery
and
integration
journeys
and
the
pipelines
that
we
are
going
to
build
right.
So
these
are
the
four
summarized
success
drivers,
but
when
we
speak
about
continuous
integration
and
continuous
delivery
or
even
deployment,
there
are
multiple
different
success.
A
We
don't
have
the
luxury
of
time
to
go
through
each
and
every
one
of
these
particular
drivers.
So
what
we're
going
to
do
is
we're
going
to
focus
on
continuous
integration
from
the
dimension
of
how
does
get
up
actions
fit
into
this
picture,
all
right.
So
to
start
off
with
how
get
up
actions
play
a
big
role
in
continuous
integrations
and
you
get
up
repos.
A
We
will
first
look
at
a
official
definition
of
github
actions
where
it's
defined
as
an
open
platform
that
gives
development
teams
the
flexibility
to
create
an
automated
software
development
lifecycle
or
workflow
to
meet
your
product
development
needs
right.
So
how
does
that
actually
translate
into
a
technical
implementation?
A
So
this
is
where
I'm
going
to
start
talking
about
the
call
concept
of
your
github
actions.
I
will
touch
base
from
a
configuration
point
of
view
from
a
overarching
point
of
view,
as
well
as
how
you
would
be
interacting
and
seeing
it
through
to
your
daily
work,
and
I
will
do
a
little
bit
of
diving
in
in
terms
of
the
difference
between
what
is
an
action.
What
is
the
workflow
and
how
does
the
lay
of
land
work
when
you're
going
to
actually
implement
the
entire
thing?
A
All
right,
if
you
look
at
the
diagram,
it
looks
really
very
creative
and
I
think
it
kind
of
resonates
well
with
the
concept
of
philosophy
of
get
up
actions
is
because
I
would
like
to
say
that
your
actions
is
kind
of
limited
or
is
boundless
to
the
creativity
of
your
development
team
or
individual
programmers
all
right.
If
you
could
be
really
creative
and
think
about
a
workflow
that
fits
your
software
development
cycle,
that
creativity
can
be
translated
into
a
configuration
which
is
through
workflows.
A
You
get
up
actions
that
will
help
automate
your
ci
and
cd
pipelines
all
right.
So
in
a
nutshell,
how
does
that
look
like
you
would
have
a
repository,
and
with
this
repository
you
will
need
to
consume
or
build
a
workflow
that
utilizes
actions
that
is
done
through
a
workflow
file
and
in
the
workflow
file.
You
have
various
different
jobs
and
steps
that
you
need
to
actually
configure
based
on
the
jobs.
A
When
the
execution
happens
on
a
runner,
you
will
be
able
to
keep
track
of
the
different
steps
and
the
logs
and
the
status
of
the
workflows
and
the
information
that
you
might
have
been
configuring
in.
In
there
all
right,
so
this
is
how
or
what
you
will
be
doing
on
a
daily
basis.
But
if
I
were
to
clarify
a
common
misconception
that
we
have
seen
cropping
up
in
our
engagements,
people
try
to,
let's
say
confused,
but
I
mean
people
usually
get
confused
between.
Like
you
know
what
is
a
workflow?
What
is
an
action?
A
So
first
up,
let's
clear
the
doubt,
I'm
going
to
say
that
you
know
use
this
particular
example,
which
is
a
light,
bulb
that's
going
to
represent
an
action,
whereas
the
lamp
over
here
is
a
workflow.
So
actions
to
a
workflow
is
a
light
bulb
to
a
particular
lamp.
So
it's
going
to
be
a
part
of
a
workflow
that
you
are
going
to
be
creatively,
configuring
right
and
that
configuration
is
going
to
end
up
as
steps
or
jobs
in
an
infrastructure
file
that
you
might
have
same
goes
to
you
know
from
a
light
bulb.
A
A
You
may
say
that
these
ideas
are
great,
but
you
know
how
does
it
really
translate
from
it
into
a
technical
standpoint
from
a
technical
standpoint,
if
I
were
to
look
at
the
lay
of
the
land,
it's
going
to
be
where
you
have
to
define
an
action
right
and
this
getup
action
is
basically
a
repository
and
the
action
could
be
either
a
docker
container,
a
containerized
action.
It
could
be
an
action
that
you
could
build
using
javascript,
or
it
could
also
be
an
action
that
is
just
using
scripts
by
using
scripts.
A
What
I
mean
here
is
that
you
will
have
a
run
command
in
your
workflow
file,
which
is
a
yaml
syntax
which
allows
you
to
run
a
cron
tab,
or
maybe
any
scripts
that
you
might
have
all
right.
So
this
is
how
you
would
build
or
define
an
action.
You
have
a
various
different
types
of
action
for
that
when
you
would
like
to
piece
the
puzzles
together
when
you
want
to
use
a
few
of
the
actions
together
in
a
workflow
that
you
would
like
to
define.
A
The
moment
you
trigger
the
workflows,
it
is
actually
going
to
run
in
a
virtual
environment.
Now
this
virtual
environment
could
be
either
a
github
hosted
virtual
environment
or
a
self-hosted
virtual
environment.
In
short,
we
will
call
this
virtual
environment
as
runners
all
right,
so
to
be
able
to
use
an
action,
you
will
need
to
reference
it
as
part
of
a
workflow
and
when
the
workflow
is
triggered,
it's
going
to
be
loaded
and
run
into
from
a
virtual
platform
which
could
be
either
a
self-hosted
runner
or
a
github
hosted
runner
all
right.
A
A
You
need
to
consume
the
action
in
your
specific
repositories
when
an
event
is
triggered
to
run
the
action
it's
going
to
be
executed,
either
in
a
self-hosted
runner
or
a
get
up
hosted
runner
all
right.
So
that's
the
layout
of
the
land
and
from
there.
What
we're
going
to
do
is
dive
a
little
bit
deeper
into
like
you
know.
A
The
suite
that
it's
going
to
belong
to
the
various
different
jobs
that
you
might
have
configured
in
the
workflow
you
get
to
see
when
it
was
last
run
as
well
as
you
are
able
to
download
the
logs.
You
get
the
duration
of
each
different
steps,
as
well
as
the
multiple
steps
that
you
might
have
defined
all
right.
All
of
these
can
be
accessed
through
your
action
step,
which
we
will
be
going
through
shortly.
A
With
that,
I'm
going
to
stop
talking
very
much
and
I'm
going
to
directly
get
into
your
first
hands-on
session,
which
is
the
setting
up
the
prerequisites
and
installing
our
learning
lab.
I'm
going
to
walk
you
folks
through
on
how
to
do
it
as
well
as
walk
you
through
the
first
six
steps
to
show
you
what
you
need
to
be
looking
out
for
right.
So
there
is
some
prerequisites.
A
If
you
had
not
gone
to
the
github
satellite
workshop
repository,
there
is
a
shortcut
link
and
if
you
would
like
to
follow
along
the
slide
decks,
the
keynote
is
also
exported
as
a
pdf
file
in
the
same
document.
So
I'm
just
going
to
copy
this
link
and
update
it
in
the
slack
channel.
So
you
folks
would
have
access
to
it
and
from
here
what
I'm
going
to
do
is
I'm
going
to
go
back
in
here.
We
need
to
install
learning
lab,
so
you
have
two
ways
you
could
go
into.
A
A
A
Bringing
you
to
the
cost
that
you
need
to
be
enrolling
to
complete
the
hands-on
practice
all
right
from
there.
We
will
move
on
to
the
first
section,
which
is
completing
at
least
six
steps
of
the
get
up
actions
workshop
right,
so
I'm
gonna
do
all
of
that.
If
you're
gonna
follow
along
great
would
be
nice.
If
you
would
like
to
see
what
I'm
doing.
First
then
continue
with
the
steps
we
will
time
box
it
for
about
15
to
20
minutes,
so
that
everyone
has
the
enough
time
to
complete
the
instructions
right.
A
A
B
A
I
hope
you
folks
are
following
along.
If
there's
any
questions,
if
you're
stuck
anywhere
feel
free
to
pop
in
the
chat,
our
awesome
moderators
will
help
you
out
in
there
all
right,
so
right
now
upon
installation.
I
am
already
in
the
learning
lab,
and
you
can
see
that
I
have
my
account
assigned
in
in
here.
A
B
B
A
All
right,
so,
you
should
be
presented
with
this
screen
where
you
get
to
choose
whether
you
want
to
create
the
course
as
a
public
or
a
private
repository,
it
doesn't
really
matter,
I'm
going
to
make
it
as
a
public
so
that
everyone
gets
to
see
it.
I'm
going
to
say
begin,
get
up
actions,
continuous
integration,
and
you
can
see
that
the
bot
is
going
to
start
cloning.
A
That
repository
into
my
account,
then
it's
going
to
publish
the
cost
materials
and
then
it's
doing
its
final
touches
as
soon
as
it's
done
with
that
steps,
I'm
going
to
be
presented
with
this
screen
with
all
the
different
steps
that
you
need
to
complete.
So
if
you
have
been
following
along
great,
if,
if
you
have
not,
I'm
gonna
give
you
folks,
maybe
five
minutes
five
to
ten
minutes
to
get
this
set
up,
and
then
I'm
going
to
continue
with
the
instructions
from
step,
one
right
up
to
step
six
right.
B
A
B
C
A
Okay,
guys,
we
have
not
yet
started
the
steps
once
you
have
installed
learning
lab.
What's
going
to
happen,
is
you
will
be
presented
with
this
screen
here
with
the
different
steps
that
you
could
start
with
if
you're
already
at
this
step,
or
this
page,
I
would
say
just
hang
in
there
for
a
while,
then
I'll
continue
with
the
steps
one
right
up
to
six.
C
C
C
A
What
I'm
going
to
do
is,
I
think
we
will
continue
with
the
next
step,
so
I'm
going
to
just
clear
the
timer
right
now
and
then
get
back
into
the
steps
so
for
our
first
work
session.
What
we're
going
to
do
is
complete
at
least
the
first
six
steps
where
we're
going
to
use
a
templated
workflow,
we're
going
to
run
the
workflow
fix
a
little
bit
of
the
box
and
then
merge
that
particular
changes
into
the
repository
that
was
already
cloned
in
your
account
right.
A
So
the
first
step
is
making
sure
that
we
click
on
the
start
button.
So
I'm
going
to
do
that.
I'm
clicking
on
the
start
button
and
what
we
will
be
presented
is
you
will
have
a
repository
called
github
dash
actions
dash
4-ci
in
your
own
account
and
in
there
there
will
be
a
issue
that
the
bot,
the
learning
lab
bot
will
create
for
you.
You
could
go
through
the
car,
the
the
contacts
it's
going
to
explain
to
you.
What
is
ci,
how?
A
How
is
it
actually
linked
to
learning
lab
and,
what's
really
important,
is
you
need
to
pay
attention
to
step
number
one
and
beyond
all
right,
so
this
is
going
to
give
you
a
list
of
activity
that
you
need
to
complete
accordingly
for
the
next
step
to
be
posted
by
the
bot.
So
I'm
going
to
give
you
an
example
of
how
you
could
go
about
completing
the
steps
over
here.
A
A
A
The
moment
I
create
the
pull
request:
what's
going
to
happen,
is
the
bot
will
be
responding
in
my
pull
request
itself,
all
right,
so
it's
going
to
respond
with
the
second
step
that
I
need
to
complete
all
right
so
over
here.
It
says
that
it's
going
to
respond
when
the
workflow
finishes
running
you
can
follow
along
the
actions
tab.
A
I
could
expand
and
take
a
look
at
all
of
the
different
locks
that
is
being
output
from
each
and
every
one
of
those
steps
all
right.
What
I'm
interested
at
this
point
is
to
go
back
into
the
pull
request,
I'm
going
to
go
into
the
ci
for
node,
so
this
is
the
pull
request
that
I
created
earlier
and
over
here.
A
A
So
it's
going
to
ask
me
to
navigate
to
the
open,
pull
request,
title
add
jest
test
and
then
merge
that
pull
request
into
this
current
branch.
So
what
I
can
very
quickly
do
is
either
click
on
the
link
here
or
I
could
just
go
into
the
pull
request.
Tab
and
click
on
add
just
test
all
right
and
what's
going
to
happen
is
I
just
need
to
merge
this
pull
request,
so
I'm
going
to
merge
the
pull
request
confirm
the
merge.
A
A
It
brings
me
back
into
the
existing
workflow
that
I've
created
right,
so
this
is
step
three
that
I
just
completed
and
then
next
I
have
step
number
four,
which
is
asking
me
to
read
the
actions
log
and
comment
the
name
of
the
test
which
is
failing.
So
how
am
I
going
to
grab
the
information?
I
first
need
to
actually
navigate
to
the
actions
tab.
So
I'm
going
to
scroll
up
to
the
actions
tab,
I'm
going
to
click
on
the
actions
tab.
A
A
B
A
Me
go
back,
oh
so
I
should
have
chosen
the
second
ci
for
node,
because
this
branch
contains
the
unit
test
that
we
have
just
added
from
the
earlier
pull
request
that
I've
merged
right.
So
I'm
going
to
click
on
the
ci
go
back
to
the
bill
here
and
then
I
have
the
failing
test
and
in
this
failing
test
I
get
to
choose
the
name
of
the
test
that
is
required.
So
I
get
to
see
that
there's
a
game,
dot,
test.js
and
then
the
function.
That's
failing
is.
A
A
As
soon
as
I
comment,
you
can
see
that
the
bot
replies
right
once
the
bot
replies.
It
tells
you
that
this
is
the
test
that
is
failing.
The
bot
is
also
kind
enough
to
propose
some
changes
to
actually
make
those
tests
from
failing
to
be
showing
up
as
a
green
tick
right.
So
what
I
would
do
is,
I
would
recommend
you
folks,
to
use
the
commit
suggestions
so
that
you
need
don't
need
to
be
like
typing
and
create
some
accidental
typos.
A
A
Fixing
and
then
completing
step
number
six,
all
right.
So
what
I've
essentially
done
is
explained
to
you,
folks,
with
some
examples
on
how
you
would
be
here.
The
bots
already
explained
replied
me,
so
it
says
that
hey
great
job,
it's
going
to
respond
and
I
could
go
ahead
and
merge
the
change.
So
I
have
everything
is
passing.
I'm
just
going
to
merge.
The
pull
request
commit
the
merge
as
a
good
housekeeping
practice.
A
I
delete
the
branch
all
right
so
as
soon
as
I've
done
that
it's
going
to
tell
me
let's
go
to
the
next
step,
but
the
next
step
is
actually
going
to
be
our
second
hands-on
practice.
What
I
would
like
to
do
is
time
box
for
15
minutes
or
10
minutes,
we'll
go
with
10
minutes
first
and
then
we'll
extend
if
you
need
more
additional
time
and
then
I
will
do
a
bit
of
a
recap:
what
actually
happened
and
from
there
we'll
move
on
to
the
second
hands-on
activity
right.
C
C
C
C
C
A
B
C
C
C
C
C
C
C
A
All
right,
so
I
I've
been
following
the
cat
threat
and
I
think
there
are
some
folks
who
are
stuck
in
the
different
steps.
So
what
I
would
recommend
is,
if
you
are
stuck
and
you're,
not
sure
which
step
you
are
currently
in
I'm
going
to
drop
a
link.
This
link
is
again
going
back
into
the
overview
of
the
steps
page
for
the
get
up
in
inter
get
up
actions,
continuous
integration
course.
B
B
B
C
C
A
C
C
B
A
A
So
these
events
were
your
push
events
or
you
opening
up
a
pr
or
whether
you're
commenting
on
an
issue
or
so
right
and
those
events
triggered
a
workflow.
And
this
is
the
template
workflow
that
we
created
from
the
community
page
right,
which
was
just
the
node.js
starter,
template
right
and
from
this
workflow
or
in
this
workflow.
A
We
are
actually
depending
on
a
action
all
right,
and
this
action
is
basically
running
some
scripts,
which
is
your
npm
bill
as
well
as
npm
test
scripts
and
those
scripts
are
actually
executed
or
run
in
a
runner
which
is
hosted
on
the
github
platform.
All
right,
so
you
could
see
that
first
and
workflow
or
action
to
to
be
triggered.
You
need
to
have
some
kind
of
event
happening
on
the
github
site,
all
right
so
from
the
event
a
workflow
will
be
triggered.
A
A
That
is
your
repository
and
in
that
repository
right
up
to
now,
we
had
only
created
one
workflow
file
right
and
this
workflow
file
is
going
to
contain
one
job
as
well
as
several
steps
in
there,
and
these
steps
are
actually
utilizing
one
or
more
actions
all
right.
So
if
you
were
to
look
at
the
workflow
file
right
now,
you
would
have
seen
that
there
is
probably
two
actions
that's
being
used.
One
is
the
check
out
action.
That's
version
two
which
we
need
to
upgrade
the
cost
to
right
and
that
particular
action.
A
I
would
like
to
zoom
in
a
little
bit
on
jobs
right
now.
Each
of
these
jobs
is
actually
going
to
be
run
in
a
virtual
environment
and
in
so
far
what
we
have
is
just
one
job
that
is
being
run
in
one
virtual
environment
and
if
you
look
at
complex,
workflows
or
actions
that
that's
out
there
in
the
community,
you
will
see
that
the
different
jobs
need
to
actually
share
artifacts
or
packages
between
the
runs
or
between
the
steps,
all
right.
A
So
in
our
next
example,
what
we
are
going
to
be
doing
is
we
are
going
to
create
two
jobs.
The
first
job
is
going
to
utilize.
An
action
call
upload
artifact.
What
it's
going
to
do
is
it's
actually
going
to
build
the
npm
package,
the
repository
the
the
tic-tac-toe
game,
it's
going
to
build
the
artifact
and
then
it's
going
to
use
an
action
to
upload
it
as
a
package
and
then
in
the
tests
job.
A
What
we're
going
to
do
is
we're
going
to
use
another
action
called
download
artifact,
and
it's
going
to
download
that
same
specific
artifact
into
the
second
job.
For
you
to
be
able
to
continue
with
the
workflow
that
you're
going
to
be
creating,
so
that
gives
us
a
good
segue
into
our
second
hands-on
section
right
in
this
section.
What
we
will
be
doing
is,
we
are
basically
going
to
add
two
different
jobs
and
include
actions
to
actually
upload
and.
A
But
I
could
add
not
only
different
packages,
but
I
could
also
specifically
get
it
to
target
a
windows
or
a
mac
or
a
linux
environment.
So
I
could
include
the
different
os
versions
where
I
would
want
to
run
the
tests
all
right
and
over
here.
What
I'm
going
to
do
is
I'm
just
going
to
click
on
commit
suggestion,
because
it
already
proposes
with
the
changes
that
I
need
to
include
so
I
say,
commit
changes.
A
Right
so
as
soon
as
I
commit
the
change
what's
going
to
be
responding,
and
this
time
you
will
see
that
there
is
going
to
be
additional
bills
being
run
over
here
all
right,
so
you
could
see
that
I
have
one
for
ubuntu
on
8x
and
another
one
for
ubuntu
as
well
on
10x
and
another
job
or
matrix
for
windows.
2016,
note
version
8
and
note
version
10..
A
So
this
this
really
opens
up
the
possibilities
of
you
know
having
parallel
execution
of
different
jobs
for
any
test
that
you
would
want
to
do
where
you
could
deploy
to
a
staging
environment
so
right
the
job's
still
running,
and
this
time
you
would
see
that
I
have
one
failing
job.
Where
else
the
other
ones
are
passing
all
right.
So
let's
see
what
the
bot
has
to
say
about
it.
A
And
the
bot's
going
to
tell
me
that
hey
you
know
we
could
actually
use
multiple
jobs,
but
in
the
first
place,
why
it
was
failing
is
because
I'm
building
it
in
one
section
and
then
I'm
not
sharing
the
artifact
with
the
different
jobs
that
I've
created
so
to
be
able
to
successfully
use
those
artifacts
between
the
jobs.
I
will
need
to
actually
create
two
different
jobs.
One
is
called.
A
A
B
A
D
B
A
B
B
A
A
B
C
C
C
C
C
C
C
A
A
All
right,
so
that's
that's
the
cue
for
the
10
minutes.
I
do
know
everybody
is,
is
really
busy
catching
up
to
speed
what
I
would
like
to
do,
because
we
have
a
bit
of
a
30
minutes
of
buffer.
I
would
like
to
run
through
the
different
steps
and
then
different
sections
of
the
workflow,
as
well
as
the
actions,
and
then
we
could
circle
back
into
the
last
hands-on
section,
which
is
adding
an
extra
workflow
file
right.
A
So
in
this
section
in
the
second
session,
what
we
have
done
is
completing
step
7
right
up
to
13
we
added,
or
we
kind
of
extracted
out
a
build
job,
as
well
as
a
test
job
right
and
then
to
be
able
to
access
artifacts
between
these
two
jobs.
We
were
using
the
upload
artifact,
the
upload
artifact
actions,
as
well
as
the
download
artifacts
action,
and
we
also
added
a
build
matrix
for
different
operating
systems
and
the
different
node
versions
that
you
wanted
to
test
on
those
operating
platforms
right.
A
A
So
right
up
to
this
point,
we
have
the
work
session
one
and
two,
which
is
focusing
only
on
the
ci
workflow
and
then
in
the
next
hands-on
section.
We
will
be
adding
an
approval
workflow.
This
is
going
to
automate
the
steps
of
you
folks,
adding
an
automatic
label
for
a
pull
request
that
approves
a
pull
request
or
merges
a
pull
request.
That's
ready
for
some
reviews
and
actions
right
later
on.
A
In
the
day,
if
you're
following
the
cd
workshop,
you
would
have
the
deployment
workflow,
which
yadav
is
going
to
be
walking
you
folks
through
right
with
that.
What
I
would
like
to
do
is
to
be
mindful
of
the
time
I'm
going
to
skip
this
particular
section.
First
explain
a
little
bit
on
the
concepts
that
we
have
and
then
come
back
to
the
workflow
session.
A
All
right,
so
we've
worked
for
work
session,
number
three
we're
just
going
to
add
another
workflow
file
and
that
workflow
file
is
going
to
include
some
logics
that
you
need
to
copy
and
paste.
The
bot
is
going
to
walk
you
through
that
instruction.
Once
you
have
completed
that
particular
instructions,
you
would
have.
A
In
your
dot,
github,
workflows,
folder,
you
should
end
up
having
two
workflow
files:
two
yaml
files
and
in
the
approval
dash
workflow
yaml
file.
You
would
have
a
content
similar
to
this,
which
is
going
to
have
its
own
name.
It's
going
to
have
one
job
and
different
steps
that
uses
a
pool
reminders,
action
that
was
defined
in
the
pool
reminders,
repo
all
right
public
actions,
repo
going
through
all
of
these
actions,
I
think,
like
you,
could
build
a
workflow.
A
You
could
include
multiple
different
actions
and
stuff,
but
the
real
power
or
the
real
value-add
that
I
would
like
you
folks
to
take
away
from
this
workshop
is
pretty
much.
How
can
you
migrate
your
existing
azure,
devops
or
circle
ci,
or
even
your
jenkins
pipeline,
all
right?
So
for
that?
What
I'm
going
to
do
is
open
up.
Another
screen
share.
A
Right
in
this
screenshot,
you
will
be
able
to
see
that
there
is
a
side
by
side
comparison
where
over.
Here
I
have
a
jenkins
pipeline,
and
then
I
also
have
over
here
a
get
actions
workflow
file
that
you
could
migrate
into
so
over
here
in
this
jenkins
pipeline.
You
could
see
that
I'm
defining
stages
and
these
stages
are
going
to
be
actually
running
a
test
and
that
kind
of
translates
directly
into
a
job
which
is
called
as
a
test
job
all
right
and
in
this
test.
A
I
can
represent
this
two
jobs
into
one
over
here
and
then
this
particular
matrix
is
actually
going
to
go
back
into
the
os
matrix
that
I
have
right
and
then
the
various
different
steps
are
just
going
to
actually
say
use,
which
particular
action,
which
is
checkout
to
be
able
to
use
the
code
base
of
the
repo
and
then
I'm
going
to
set
up
node,
which
particular
version
I'm
just
running
the
scripts
over
here.
All
right
and
we
have
detailed
instructions
on
how
you
could
actually
do
the
matrix.
A
A
In
the
help
documentation
that
we
have
provided,
we
have
a
section
that
talks
about
my
grading
to
get
up
actions
and
if
you
were
to
click
on
that
particular
section,
it
talks
to
you
on
how
you
could
migrate
from
circle
ci
to
get
up
actions
from
azure
pipelines
as
well
as
from
jenkins.
So
if
I
were
to
click
on
the
jenkins,
it's
going
to
give
me
a
side
by
side.
A
Comparison
of
you
know
what
does
agents
mean
in
get
up
action,
they're,
basically
runners,
they
could
be
either
self-hosted
or
they
could
be
from
github
itself.
You
have
like
agents,
posts
and
stages.
They
directly
translate
into
different
jobs
that
you
could
run
on
either
container
or
include
different
steps.
A
A
A
What
are
the
events
that
actually
trigger
a
workflow,
different,
contextual
expression,
syntax,
as
well
as
virtual
environments?
And
if
you
would
like
to
know
what
are
the
different
softwares
that
are
installed
on
those
scada
posted
virtual
runners,
you
could
come
into
the
link
and
you
can
see
that
all
of
the
different
softwares
that
comes
predefined
in
here
right.
So
you
get
all
of
the
information
that
you
need
to
start
up
and
with
that.
A
B
B
B
A
B
A
A
A
A
A
So,
let's
wait
for
the
jobs
to
run
and
the
bots
should
be
responding
in
the
meantime.
What
I
would
propose
is
for
us
to
use
the
last
15
minutes
to
complete
as
many
steps
as
possible,
and
I
will
be
paying
attention
to
the
chat
window
and
slack
to
see
if
there's
any
questions
that
I've
missed.
That
could
use
my
attention.
E
C
C
C
C
A
All
right
so
as
we
are
getting
closer
to
the
end
of
the
workshop,
what
I'm
going
to
do
is
very
quickly
recap
some
of
the
questions,
so
you
could
continue
just
working
on
the
background.
While
I
post
and
answer
some
of
the
questions,
starting
with
the
first
question,
are
the
slides
going
to
be
provided
after
yes,
the
site
slides
are
going
to
be
in
the
this
particular
ci
with
actions
workshop
repo,
in
fact,
they
are
already
there
as
a
pdf
document
right
so
yeah
there,
the
next
one.
A
A
Next
question:
will
the
recording
of
the
talk
be
available
after
the
course?
Yes,
all
attendees
will
receive
a
copy
of
the
recording
after
the
workshop
next
question.
Our
workflow
is
conceptually
similar
to
jenkins
pipeline.
Yes,
they
are
conceptually
similar.
In
fact,
we
have
a
path
where
you
could
migrate
from
the
jenkins
pipeline
into
workflows
in
texas
and
the
links
are
actually
already
dropped
in
the
resources
section
of
the
pdf
document,
which
is
shared
next
question.
I,
like
the
bot,
especially
suggestions
for
fixes,
would
be
nice
to
integrate
it
at
work.
A
A
Ghe,
so
I'm
going
to
drop
the
link
in
the
channel
shortly,
you
will
be
able
to
go
to
the
documentations
and
learn
quite
a
bit
of
the
app
all
right
next
question:
how
can
I
retake
this
learning
lab
course?
If
I
wanted
to
it's
going
to
be
as
simple
as
let's
say,
I've
completed
the
steps
you
could
just
go
in
here:
leave
the
cost.
So
when
you
say
leave
the
cost,
it's
going
to
ask
you
whether
do
you
want
to
delete
the
cost
repository
yes
or
no,
and
then
you
would
be
able
to
unregister.
A
C
B
A
What
are
possible
os
targets?
Is
it
possible
to
use
a
custom
os?
Yes,
you
could
do
a
custom
os,
but
that's
going
to
be
a
self-hosted
runner
and
there
is
documentation
on
how
you
could
host
your
own
runners
and
what
are
the
basic
prerequisites
that
you
need
to
meet
right.
Currently
we
do
support
windows,
server,
2019,
ubuntu,
18.04,
16.04
and
mac
os
catalina
10.15.,
just
bitara.
A
Is
it
going
to
be
supported
anytime
soon,
so
we
have
internally
started
working
on
preparing
those
image,
but
we
don't
have
an
actual
eta
to
to
share
for
you
folks
today
on
that.
So
this
is
the
next
interesting.
It's
a
very
good
question
where
you
say
if
we
do
not
mention
node.js
matrix
in
the
build
which
version
of
node
will
be
used
by
default.
A
You
will
be
specifying
the
node
version
that
is
going
to
be
the
default
version
that
you
are
required
to
run
the
action
right
and
that's
covered
in
the
section
where
on
how
to
build
a
get
up
action
right.
Are
there
any
additional
trainings
besides
learning
lab
and
get
up
actions,
because
they
have
a
steep
learning
curve?
A
A
Last
but
not
least,
all
of
these
questions
and
answers
that
we
have
just
explained
will
be
converted
into
a
faq
markdown
document
that
will
live
in
the
same
repository
of
the
ci
with
actions
repo
in
the
github
satellite
workshop.
So
you
don't
need
to
memorize
the
answers
it's
going
to
be
available
for
you
in
the
form
of
a
faq
document.
Right
with
that,
I
think
some
parting
thoughts.
A
All
you
need
to
do
is
just
point
a
reference
to
that
actions
in
your
workflow
files
that
you're
going
to
define,
and
it's
going
to
be
as
easy
as
one
two
three
to
point:
the
dependencies
use
it
into
your
workflow
with
all
the
transparencies
and
the
log
information
that
you
would
get
at
your
hand.
It's
gonna
it's
following
an
open
and
component
based
design
for
for
continuous
integration.
A
It's
all
going
to
be
in
one
single
platform,
so
you
save
a
lot
of
time
in
contact
switching,
it's
also
os
agnostic
and
it
uses
the
github's
open
api
to
drive
at
the
car
or
the
heart
of
the
actions
right,
and
we
do
have
some
resources
for
you.
Folks.
The
help
documentation
is
pretty
legit.
It's
kind
of
tight:
it
has
every
single
information
that
you
need
to
be
up
and
running
with
github
actions
beyond
that.
A
A
I
think
there
is
also
a
javascript
action,
and
the
neat
thing
about
this
actions
here
is
that
you
could
use
them
as
a
template
to
kick
start
your
own
version
of
actions
that
you
would
like
to
build
right,
so
you
would
have
a
scaffolding
or
a
template
created
automatically
for
you
right
with
that.
I
think.