►
Description
Presented by Chris Patterson, Staff Product Manager @ GitHub
Since its release, GitHub Actions has seen massive adoption by open source projects, teams, and organizations looking to automate their software workflows. Improvements and new features are continuously being shipped to help better serve the needs of developers worldwide. In this session, Chris Patterson, the Staff Product Manager at GitHub, will walk you through some of the newer features of GitHub Actions that can help you better automate your workflows. He'll also share insights on how Actions is being used worldwide, and give you a peek at what’s on the roadmap for the future!
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Thank
you
so
much
davian
mohit
for
that
very
kind
introduction.
As
I
say,
my
name
is
chris
patterson.
I
am
a
staff
program
manager
here
at
github
and
today
I
am
coming
with
you
coming
to
you
from
kerry
north
carolina
in
the
united
states
and
we're
going
to
give
kind
of
a
tour
of
some
of
the
new
things
that
we
have
been
working
on
with
github
actions
over
the
past
several
months.
A
But
before
we
do
that,
I
do
want
to
give
a
big
shout
out
to
a
bunch
of
my
colleagues
in
india
who
I've
worked
with
for
almost
15
years.
I'm
incredibly
excited
that
github
is
now
in
india
and
that
I'm
able
to
work
with
the
developer
community
there.
More
than
all
we
have
here's
some
photos
of
me
during
several
of
my
trips
to
india.
Hyderabad
has
been
the
primary
location,
so
I've
got
gokanda
and
I've
even
driven
in
india.
A
A
A
We've
been
working
very
hard
on
making
actions
more
secure,
and
this
is
a
big
focus
of
mine
personally
actually,
and
if
you
think
about
things
like
the
recent
solarwinds
issues,
where
you
know,
ci
can
absolutely
be
a
potential
place.
Where
security
can
you
know
you
can
create
security
holes
in
your
software
development
infrastructure,
github
actions
being
secure
is
incredibly
important.
A
We
have
hundreds
of
thousands
of
repos
that
rely
on
actions
every
day
and
we
need
to
make
sure
we
can
scale
to
reach
to
to
provide
all
of
the
necessary
resources
so
a
little
bit
about
actions
and
how
it's
grown.
Github
actions
is
just
a
bit
over
a
year
old.
At
this
point
and
from
a
perspective
of
the
community
embracing
it,
it's
just
been
absolutely
incredible.
In
the
marketplace,
there's
about
seven
thousand
or
a
little
more
than
seven
thousand
available
different
actions.
A
You
know
the
growth
is
just
skyrocketing,
we're
now
just
in
the
github.com
cloud
this.
This
only
includes
the
runners
that
we
host
more
than
125
million
jobs
a
month
and
growing
at
an
astounding
rate,
and
all
of
that
in
the
community
has
really
brought
us
to
be
the
number
one
ci
platform
on
github
in
just
over
a
year,
and
it's
incredible
and
we're
incredibly
honored
to
have
you
guys
as
part
of
that
now
get
up.
Enterprise
server
actions
is
generally
available
on
github
enterprise
server.
Three,
you.
B
A
Up
your
enterprise
server,
you
can
configure
actions,
you
can
run
workflows.
You
can
use
actions
in
your
workflows
locally
in
your
server
as
well
as
through
github
connect.
You
can
take
advantage
of
that
incredible
actions
community
that
I
just
talked
about,
so
we've
really
enabled
github
enterprise
server
to
reach
out
and
take
advantage
of
the
cloud
now.
The
next
thing
I
want
to
talk
about
is
continuous
delivery.
A
A
That
could
be
better
that
had
some
of
the
core
capabilities
that
people
expect
things
like
you
know,
manual,
approvals
and
and
other
kinds
of
rules,
and
so,
as
part
of
the
conversation
today,
I
want
to
talk
about
sort
of
five-ish
new
capabilities.
Some
we've
talked
a
little
bit
about
at
universe.
Some
are
new
since
then
that
we're
bringing
in
the
overall
space
around
continuous
delivery,
devops
security
for
github
actions,
so
the
first
one
was
just
the
simple.
A
I
want
to
be
able
to
visualize
and
see
what's
going
on
in
my
workflows,
and
this
is
a
feature
we
did
ship
at
universe.
So
we've
enhanced
it
quite
a
bit
since
then
to
improve
the
performance
and
add
a
few
little
more
tweaks
to
it,
to
make
it
better,
but
it's
great
to
be
able
to
see
how
your
workflow
is
progressing,
particularly
if
you
have
a
complex
deployment
pipeline
or
a
large
matrix
to
help
understand.
What's
left,
what's
going
on,
it's
just
a
great
addition
to
the
overall
experience.
A
The
second
area
to
talk
about
is
the
environment
protection
rules.
Whenever
you've
got
a
continuous
delivery,
workflow,
that's
deployed
into
say,
a
production
environment.
It
can
be
important
for
a
lot
of
organizations
to
make
sure
there's
two
sets
of
eyes
who
are
approving
these
things.
So
there's
the
developer
that
approved
the
source
code,
and
then
there
is
some
other
person,
a
release,
manager,
engineer
somebody
who
says
it's:
okay:
to
deploy
to
production
with
the
environment,
protection
rules.
We've
we
started
out
with
just
two
and
we've
actually
added
one
since
then,
and
over
time.
A
We
plan
to
make
this
an
extensibility
point
to
enable
you
to
plug
in
your
own
systems,
to
allow
you
to
control
when
things
deploy
the
main
protection
rules.
Are
this
required
reviewers
rule
that
basically
says
that
somebody
within
a
team
or
an
individual
has
to
approve
a
job
before
it
goes
through,
and
then
we'll
talk
a
little
bit
more
through
the
demo
about
exactly
what
happens
at
that
point
secrets.
A
So
we
wanted
the
ability
to
scope
these
secrets
to
an
environment,
so
we
introduced
environment,
specific
secrets
and
those
work
by
making
sure
that
whenever
github
actions,
workflow
runs
and
references,
an
environment,
the
protection
rules
have
to
pass
before
that
job
starts
and
before
it
gets
access
to
the
secrets.
And
so
you
could
have
a
secret
called
deploy
key,
that
is
scoped
to
say,
the
repository
that
the
development
environment
can
use
and
then
another
secret,
that's
the
same
name.
A
It's
always
important
to
know
what
has
been
deployed
where-
and
this
is
one
of
these
capabilities
that
github
has
actually
had
for
a
long
time
if
you're
very
familiar
with
github,
you
might
know,
there's
this
thing
called
the
deployments
api
and
that
really
shows
you
a
list
of
the
activity
of
deployments
to
different
environments
and
can
tell
you
exactly
which
commit
has
been
deployed
to
a
particular
environment
and
so,
as
part
of
our
goal,
to
really
build
actions
and
build
it
deeply
integrated
into
github.
We,
instead
of
creating
something
new
to
track
your
deployments.
A
Actions
just
plugs
right
into
this,
and
this
is
also
nice,
because
it's
another
place.
That's
extensible
in
github
or
even
third
parties
and
we'll
look
at
how
actions
plugs
into
the
deployment
api
to
give
you
that
strong
element
of
history
and
finally,
security
features.
This
is
a
actually
a
preview
of
a
feature
that
hasn't
quite
shipped
yet,
but
will
be
shipping
soon.
We've
done
a
bunch
of
work
in
github
actions
to
improve
security.
We've
done
some
blog
posts.
We've
done
a
bunch
of
documentation.
A
It
could
read
and
write
source
code
read
and
write
issues,
pull
requests
etc,
and
it
works
well
in
a
lot
of
cases.
But
you
know
because
github
actions
is
such
so
much
of
an
automation
platform,
there's
lots
of
different
kinds
of
things.
People
do
like
this
example
of
a
cleanup
pr
or
I've
got
a
workflow
that
just
looks
at
issue
comments
and
does
some
processing
in
those
cases.
I
don't
need
those
broad
permissions.
I
really
want
to
have
a
very
narrow
set
of
permissions,
and
so.
C
A
Introducing
a
new
permissions
block
which
is
actually
available
at
the
workflow
level
and
the
job
level,
and
you
can
go
in
and
change
the
permissions
for
this
particular
workflow,
and
so
in
this
example,
I've
got
just
contents
read,
so
all
I
can
do
is
read
the
source.
I
can't
write
the
source
and
having
the
ability
to
control
that,
with
give
you
least,
access
we
think
is
going
to
be
very
valuable
and
just
continue
to
help
improve
the
security
of
github
actions
in
the
future.
A
So
I'm
going
to
switch
over
to
a
repo
here,
which
is
a
popular
github
repos
by
language.
It's
a
pretty
simple
application
that
basically
just
looks
at
all
the
github
repos
and
lets
you
sort
them
by
language,
and
in
this
particular
case
I've
got
a
couple
of
different
workflows,
set
up
to
do
some
different
things
for
me.
So
to
get
started,
I'm
gonna
go,
add
a
new
feature
or
a
new
language
simply
go
into
my
code.
Pull
this
up.
A
So
in
this
case
I've
got
a
couple
of
different
workflows.
I've
got
my
deploy
and
we
can
see
it's
triggered
off
a
pull
request
when
it's
targeting
main
it
is
triggered
off
or
triggered
off
a
push
for
main.
It
does
a
couple
of
different
things,
so
I've
got
a
build
job
here.
Checks
out
sets
up
node
using
our
caching
capability.
A
It
caches
the
node
modules,
which
should
speed
things
up
and
then
uses
a
couple
of
different
other
actions
which
are
really
great,
so
we
had
a
basic
script
one,
but
the
ones
I
want
to
call
attention
to
here
are
these
docker
login
and
the
docker
of
the
setup,
build
x,
docker,
login
and
then
the
docker
build
and
push
action.
These
are
built
by
docker
in
concert
with
with
github.
A
A
So
we
see
this
other
action
that
is
from
azure
another
one
of
our
partners
and
it
knows
how
to
deploy
to
azure
web
apps
and
what
it
does
is.
It
takes
the
container
in
this
case
that
I
built
deploys
to
azure
web
apps
and
outputs.
The
url
and
lets
me
bind
it
directly
in
here
and
we'll
show
how
that
pulls
together,
some
core
traceability.
A
So
we
go
back
and
take
a
look
at
our
actions.
Workflow.
We
should
see
that
it's
moving
along,
so
we
can
see
that
deployed,
review
is
started
and
as
one
of
these
nice
features
in
the
visualization,
I
can
see
the
progress
it's
made,
but
I
can
also
see
right
here
in
my
actions
view
the
url
it
goes
to
and
even
further,
if
I
happen
to
come
into
the
pull
request.
First,
I
get
this
nice
view
right
here
in
the
pull
request.
A
A
Do
is
go
in
and
merge
this
pull
request
and
confirm
the
merge
and
let
that
code
go
and
it's
going
to
start
my
next
workflow.
So
if
everything
worked
out
well,
we
see
that
our
merge,
pull
request
is
kicked
off
and
it's
going
to
start
the
next
build
job.
So
let's
go
take
a
look
and
see
how
this
workflow
is
going
to
complete
and
actually
we
can
see
in
this
case
two
different
workflows
picked
off.
I
clicked
off
this
this
cleanup
pr.
A
So
in
this
case
I've
got
a
job,
that's
going
to
delete
my
review
slot,
and
this
is
taking
advantage
of
that
new
capability.
We
talked
about
for
limiting
permissions,
so
in
this
case
my
cleanup
pr
workflow
goes
and
deletes
that
and
deletes
that
deployment
of
my
application
that
I
made
for
the
pull
request,
and
so
I'm
not
wasting
money
right
cloud
resources
cost
money.
I
want
to
make
sure
there
they
go,
but
in
this
case
I
only
need
read
of
the
source
code.
A
I
actually
don't
need
any
other
permissions,
so
I
was
able
to
lock
down
the
permissions
for
this
particular
workflow
and
make
sure
that
it
just
it.
It
only
does
exactly
what
it
needs
to
do
that
way.
If,
for
whatever
reason,
I've
done
something
not
quite
right
or
there's
some
other
issue,
I'm
protecting
myself
now
in
the
workflow
that
does
the
deployment.
A
A
Staging
it's
very
similar
to
the
other
job
and
then,
after
that
it
deploys
this
aging.
If
everything
looks
good,
it's
going
to
go
under
production,
but
of
course
I
don't
want
things
to
just
immediately
go
to
production
right.
I
want
to
have
some
sort
of
approval
or
step
in
there
to
make
sure
things
aren't
just
moving
along.
So
to
do
that
in
my
settings.
I
have
this
new
section
called
environments,
and
we
see
here
that
I've
got
review
lab
staging
and
production.
A
A
A
Another
feature
that
we're
launching
very
soon
in
concert
with
the
mobile
team
is
the
ability
to
have
these
review
notifications
on
the
mobile
app
you'll
see
more
about
that
soon.
But
again,
this
is
a
kind
of
a
quick
sneak.
Peek,
of
course,
it'll
be
there
for
ios
and
android
go
back
and
take
a
look
here.
A
A
All
right
how
many
there
let's
go
back
and
look
all
right
so
now
we're
deployed
to
production.
So
we
see
here
it's
popped
up,
it's
stopped,
so
the
workflow
is
paused.
It's
no
longer
running
on
a
runner.
It's
simply
waiting
for
somebody
to
come
along
improvement
and
says
me
chris
pack,
because
I
triggered
this
workflow
as
request
review
to
play
to
production.
I
can,
of
course,
click
review
deployments
here
and
if
company
look
at
notifications,
I
can
see
right
here
that
I
see
this
nice
notification.
A
A
Proven
deploy
and
this
job
will
pick
up
and
deploy
my
application
to
the
production
version
of
my
website
and
keep
on
going.
So
that's
a
quick
tour
of
some
of
the
new
capabilities
we
have
in
github
actions.
In
fact,
I've
got
one
more
little
thing.
I
want
to
show
you
so
there
there's
always
a
case
where
a
particular
environment.
A
Typically
production
wants
to
make
sure
that
only
one
thing
can
deploy
to
it
at
a
time
and
so
we're
introducing
a
new
capability
that
will
ship
in
a
few
weeks
that's
being
tested
right
here,
which
will
allow
me
to
serialize
those
deployments
so
keep
an
eye
out
for
that
it
should
be
really
interesting.
I've
got
some
great
content
coming
to
to
really
help.
You
again
drive
those
continuous
delivery,
workflows
and
just
use
github
actions
to
its
fullest.
A
C
A
We
chose
to
make
the
features
that
we
shipped
at
universa
beta,
because
we
wanted
to
have
some
time
to
get
some
feedback,
and
we
also
knew
that
we
weren't
quite
done
with
the
core
set
of
features
that
we
wanted
to
have
available
for
our
customers
and,
finally,
from
just
an
engineering
health
perspective,
we
wanted
to
make
sure
that
we
could
monitor
them.
We
could
support
them.
We
we
knew
what
was
happening.
A
All
of
the
things
that
you
you
know
you
have
to
do
when
you
run
a
service,
so
we
think
we're
about
a
month
away
from
calling
them
ga
a
couple
of
small
things
left
to
ship,
a
few
more
small
bugs
to
fix
and
sometime
during
the
month
of
april.
We
think
we'll
call
these
ga
and
then
make
them
and
they're
already
widely
available
at
everybody.
It's
completely
open
beta,
but
that
general
availability
also
unlocks
it.
So
we
can
ship
them
in
the
next
version
of
github
enterprise
server,
so
github
enterprise
server.
B
A
So,
as
we
heard
in
the
keynote
from
erica
github,
enterprise
server
is
just
a
very
important
part
of
the
overall
github
product
family,
and
we
have
lots
of
customers
for
a
wide
variety
of
reasons
that
need
to
use
it
and
not
having
every
single
feature.
That's
available
on
github.com
is
is
just
not
acceptable
right.
They
want
to
have
all
of
the
power
of
github
but
run
in
their
own
data.
Centers
github
actions
was
one
of
the
largest
features
that
just
wasn't
there
yet,
and
it
took
us
a
long
time.
A
It
took
almost
a
full
year
of
very
dedicated
development
from
a
good
percentage
of
the
team
in
order
to
take
github
actions
and
bring
it
to
github
enterprise
server.
There
was
a
significant
amount
of
effort
to
do
that,
and
you
now
that
it's
there
a
lot
of
customers
very
large
customers
who
have
been
asking
for
it
are
happy
and
starting
to
adopt,
and
again
it's
all
about
making
sure
that
github
enterprise
server
sells
the
full
vision
and
the
full
value
that
people
expect
from
github.com.
C
A
Sure,
as
I
mentioned
in
the
demo,
one
of
the
key
things
is
to
make
sure
that
or
one
a
key
security
tenant
is
leased,
access
right
and
all
things
you
do.
You
want
to
make
sure
that
you
give
people
the
least
access
possible
or
you
give
a
process,
especially
automation.
That's
a
that's
a
really
ripe
area
for
attack
and,
as
we
started,
github
actions
just
for
a
variety
of
reasons.
We
we
built
it
where
we
actually
did
narrow
the
permissions
from
a
standard,
github
app.
A
So
typically,
when
you
have
a
standard,
github
app,
you
give
it
a
list
of
repos.
You
say
this
has
some
set
of
permissions
to
this
set
of
repos
well
with
github
actions
we
at
least
narrowed
that
to
a
single
repo.
Now
within
that
repo,
you
still
had
fairly
broad
permissions,
because
we
wanted
people
to
be
able
to
automate
all
kinds
of
things.
You
know
they
want
to
automate
ci,
but
they
also
automate
issue
bots,
and
we
see
amazing
variety
of
different
things.
A
So
the
github
apps
token
can
read,
write
source
can
read,
write
issues,
read,
write,
prs
et
cetera.
You
can
go
look
at
the
documentation
and
see
all
of
the
capabilities
it
has,
but,
of
course
any
given
workflow
doesn't
necessarily
need
to
be
able
to
do
all
those
things,
and
we
have
had
requests
from
this
in
the
community
and
certainly
as
we
wanted
to
get
there.
A
B
A
So
private
repos
have
environments
with
actions
today,
but
they're
only
part
of
the
enterprise
sku.
So
you
have
to
have
an
enterprise
plan
to
use
environments
with
private
repos.
It's
something
that
we're
taking.
You
know.
We
certainly
have
seen
the
feedback
from
the
community
that
people
wanted
in
team.
It
is
something
that
we
are
discussing,
but
today
we
we
sort
of
because
the
environments,
protection
rules
and
things
like
that
are
very
compliance.
Oriented
et
cetera.
B
Great
great
and
this
question
was
from
the
pain
thanks
a
lot
chris
and
for
our
audience.
Let
me
share
with
you
that
chris
is
not
going
anywhere.
He
is
with
you
all
for
the
next
30
minutes
at
github
discussions.
So
post
all
your
queries
get
all
his
all
your
answers
from
him
and
he's
joining
you
at
his
midnight
so
take
as
much
as
possible
from
him
bye,
bye,
chris,
we'll
let
you
go
and
enjoy
your
time
with
our
viewers
at
get
up
discussions.