►
Description
Presented by Chris Patterson, GitHub
In this demo-packed session, you'll learn how to deploy to any cloud and on-premises with GitHub Actions, a powerful community-powered automation and CI/CD system built directly into GitHub.
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/
B
Next
is
Chris
Patterson
with
ship;
it
would
get
up
actions
and
get
up
packages.
Chris
is
a
product
manager
here
at
github
and
is
had
an
interesting
career
in
tech
has
started
off
with
classic
ASP
then
went
on
to
Visual
Basic
to
Java.
And.Net
now
is
even
dabbling
in
JavaScript.
So
now
over
to
you,
Chris.
C
C
First
off
I
want
to
thank
everybody
for
joining
us.
This
virtual
conference
has
been
a
lot
of
fun.
I,
certainly
learned
a
lot
today
and
seen
a
lot
of
really
cool
things.
It's
great
to
be
able
to
share
this
time
with
you
and
interact
with
the
community,
even
though
we
can't
be
together
so
today,
I'm
going
to
go
through
a
little
bit
more
about
github
actions,
as
Matt
mentioned
in
the
keynote.
C
This
morning
we
launched
it
last
November
made
it
generally
or
last
August
actually
made
it
generally
available
in
November
for
all
your
repos
and
I
could
not
be
more
impressed
with
what
I've
seen
so
far.
The
uptake
from
the
community
and
the
interaction
has
been
amazing,
and
it's
really
really
great
to
see
what
you
guys
are
doing
with
actions.
So
today
we're
going
to
walk
through
a
couple
of
different
things.
While
actions
has
been
out
for
a
few
months,
you
know
not.
C
We'll
talk
a
little
bit
about
the
details
about
action,
some
of
the
things
that
to
help
you
orient
yourself,
then
we're
going
to
do
a
really
quick,
getting
started
basic
CI
demo
of
how
I
can
just
do
a
simple
website
and
then
I'm
going
to
take
all
of
the
things
that
we've
talked
about
and
just
put
some
interesting
spins
on
it
and
talk
a
little
bit
more
about
some
of
the
great
things
that
I've
seen
from
the
community
so
getting
started,
get
up
actions.
Obviously,
at
its
core,
is
a
great
automation
system.
C
That's
really
what
we
want
to
build.
We
want
to
make
sure
that
we
have
a
very,
very
powerful
and
flexible
CI
and
eventually
CD
system,
to
allow
you
to
automate
those
workflows
to
automate
that
continuous
testing
to
automate
that
continuous
integration
and
continuous
delivery.
But
at
the
same
time
our
vision
for
actions
goes
beyond
them.
C
We
want
to
enable
our
community
to
take
advantage
of
these
automation,
workflows
and
reusable
bits
in
the
same
way
that
we
do
in
our
in
our
applications
by
taking
advantage
of
open
source
libraries
that
have
been
created
by
other
members
of
the
community
so
getting
started
in
order
to
get
started
with
github
actions.
All
you
have
to
do
is
go
up
to
a
repo
that
you
own
click
on
the
actions.
Tab
and
you'll
be
presented
with
a
screen
with
a
wide
variety
of
different
templates.
C
We'll
walk
through
this
in
more
detail
later,
but
these
templates
come
from.
Today
they
come
from
a
repository.
That's
actually
open
source.
It's
in
the
actions
org
on
github,
it's
called
started,
workflows,
a
variety
of
ones.
We
have
created
ourselves
as
part
of
the
product
team,
but
we've
also
incorporated
ones
from
partners
such
as
Amazon
or
Google
hashey
Corp,
Tencent
asher,
as
well
as
from
the
community.
For
example.
Most
recently
we
switched
over
the
Ruby
workflow
to
be
one
that
is
actually
maintained
by
the
Ruby
community
over
time.
C
We
have
a
vision
to
expand
this,
to
allow
anybody
to
potentially
show
up
on
this
page
by
creating
a
starter,
workflow
and
publishing
it
to
a
marketplace.
Just
like
you
can
an
action
or
an
app
simply
get
started.
You
click
the
new
workflow
you'll
be
presented
with
the
editor.
You
can
commit
it
and
off
you
go
so
as
I've
gone
through,
I've
used
a
couple
of
different
terms
and
I
want
to
make
sure
we're
all.
On
the
same
page,
the
terminology
we
get
hub
actions
the
product.
C
We
have
two
major
things
that
we
think
about
with
respect
to
road
ology
is
a
workflow
which
is
the
file
you
use
to
orchestrate
what
you
want
to
do.
It's
where
you
declare
the
event
that
you
want
to
listen
on.
You
declare
your
jobs.
The
job
is
just
a
set
of
steps
that
runs
on
a
particular
computer,
Mac,
Windows
or
Linux,
and
then
a
series
of
steps
which
are
the
individual
actions.
C
These
actions
are
simply
stored
in
repos
and
they're
referenced
across
the
github
graph,
there's
over
3,000
actions
in
the
github
marketplace
today,
and
as
we
walk
through
the
demos
for
this
presentation,
we'll
definitely
take
advantage
of
them
and,
of
course,
community
powers,
github
actions,
as
I
mentioned,
we
have
actions
from
various
partners.
We
have
actions
that
we
create
and,
of
course,
actions
from
the
community
all
right
so
enough
with
the
kind
of
overview.
Let's
get
started
and
take
a
quick
look
at
a
basic
CI
scenario.
C
So
I
have
this
application
that
I
wrote
and
what
it
does
is.
It
shows
sort
of
the
most
popular
repos
by
language
on
github,
and
it
just
gives
me
a
nice
presentation
and
layout
of
those,
but
what
I
want
to
do
is
today.
I
want
to
actually
deploy
this
out
to
a
cloud.
So
if
I
go
over
to
the
actions,
tab
I
can
go
through
and
the
first
thing
you'll
notice
is
this
action
happens.
C
This
application
happens
to
be
written
in
JavaScript,
so
we've
recognized
that
by
looking
at
the
language
that
github
knows
is
primary
to
that
particular
repo
and
we've
offered
you
a
couple
of
different
options
for
what
you
can
do,
so
you
can
do
a
very,
very
basic,
node
workflow.
So
if
we
click
on
that,
we'll
see
that
out
of
the
box,
this
is
going
to
set
you
up
to
test,
to
run
your
test
across
a
couple
of
different
versions
of
node,
using
a
matrix
and
across
in
for
push
and
pull
requests.
C
What
I
really
want
to
do
is
this
is
a
web
app,
so
I
want
to
deploy
it
out,
and
we
can
see
a
couple
of
different
options
here
so
today
I
happen
to
be
most
familiar
with
Azure.
So
I'm
going
to
use
this
template
provided
by
them
to
deploy
a
node.js
web
site
to
an
azure
web
app.
So
when
I
click
on
this
I
get
presented
with
a
template
to
do
a
couple
of
different
things,
I
get
some
instructions
about
what
I
need
to
do
to
set
up
these
things.
C
C
And
if
I
look
down
here,
I've
got
a
couple
of
basic
things
happening:
I'm,
going
to
set
up
a
projector
repo,
it's
going
to
set
up
a
version
of
node
to
use
I'm
gonna,
run
kind
of
a
basic
set
of
dependencies
and
then
publish
so
let's
go
ahead
and
commit
this
guy,
and
in
this
case
I'm
gonna
be
a
little
bit
naughty
and
dangerous
and
just
commit
directly
to
the
master
branch
if
I
go
and
click
on
the
actions
tab.
Oh.
C
Sorry,
you
know
what
I
think
that
I
forgot
to
change.
One
thing
in
this
particular
template
up
here
at
the
top
we
can
see
this
template
runs
on
release
created
I
actually
want
to
run
this
guy
on
push,
and
we
look
here
in
the
editor
right
away.
I
get
some
help
to
tell
me
what's
going
on
so
I
want
to
run
on
push.
C
In
fact,
I
want
to
only
one
on
run
on
pushes
to
the
master
branch,
and
while
the
editor
helps
you
with
that
syntax,
if
I
forget,
we've
got
documentation
right
here
to
help
you
along.
So
let's
commit
that
back
and
maybe
this
time
we
should
yep.
So
we
see
we,
we
recognize,
there's
a
new
workflow
file
committed
and
we're
gonna
start
running
it.
C
So
in
this
case
we're
gonna
run
this
particular
workflow
on
runners
that
are
hosted
by
github,
and
we
have
runners
available
that
are
on
all
of
the
major
operating
systems,
so
Windows,
Mac
and
Linux,
as
well
as
the
ability
to
host
your
own
runners,
which
I
think
is
another
great
feature
of
actions.
In
fact,
recently
we
ship
the
ability
to
host
runners
not
only
for
an
individual
repo
but
also
for
the
entire
organization.
C
C
So
we
see
here's
my
application
running
I
deployed
it
earlier.
It
looks
pretty
nice,
but
there's
a
couple
of
things
about
that
process.
That
just
aren't
great
for
me.
So
first
off
I
think
that
we're
missing
a
pretty
important
language
here
so
I
see
no
Ruby
projects
mentioned
so
I
think
we
need
to
fix
that.
And
secondly,
you
know
I,
don't
like
the
fact
that
we,
just
you
know,
pointed
right
at
production.
You
know
we
just
said
you
know
we're
just
going
to
push
and
push
to
production.
C
So
what
I've
done
is
I
have
another
version
of
my
application
that
I've
done
a
few
different
things
to
first
off
I've
got
a
docker
file,
so
I
decided
that,
instead
of
just
kind
of
using
whatever
node
runtime
I
get
I
want
to
control
those
things
so
I've
docker
eyes
this
application
and,
in
addition,
I've
added
a
bunch
of
different
workflows
and
you
can
see
I've
got
one
that
does
a
build.
I
got
this
thing
called
chat
ups
here,
clean
up,
PR,
etc.
C
So
we're
gonna
walk
through
this
more
richer,
continuous
delivery
syrup
scenario
that
I've
built.
So
as
I
mentioned,
my
application
is
missing
that
core
important
language
Ruby.
So
what
I'm
going
to
do
is
I'm
going
to
go
in
and
make
a
quick
change
now.
I
could
open
this
up
in
a
code
space
that
would've
been
a
really
cool
thing
to
do.
I
think
I'll
try
that
later,
but
for
now,
since
it's
just
a
simple
job,
simple
change
to
JavaScript,
I'm
gonna
edit
right
in
the
browser,
so
I'm
gonna
go
over
here
and
put
Ruby.
C
That's
the
first
language
after
all,
I
think
that
looks
good
alright.
So
we
go
down
here,
gonna,
commit
changes
and
in
this
case
I
can't
commit
directly
to
master
branch
because
I've
got
branch,
protection,
setup,
so
I'm
going
to
say
an
ADD
Ruby,
a
ruby
and
we'll
put
a
nice
comment
say
Mona
was
sad.
C
Ahead
and
proposes
file
change
immediately,
will
get
dropped
into
the
PR
experience.
You
guys
are
all
probably
very
familiar
with
go
and
create
this
full
request
and
then
right
away.
Couple
of
things
happen
so
as
before
we
just
kind
of
pushed,
and
it
kicked
off
immediately
now
we're
in
a
pull
request,
and
we
have
a
couple
of
required
checks
coming
up
and
we
can
see
them
starting
to
run
and
click
here
go
start
to
look
at
the
details
of
running
and
we'll
see
we're
doing
a
bunch
more
interesting
things
here.
C
In
fact,
we've
added
a
whole
bunch
of
features
to
our
build
as
compared
to
what
was
in
the
default
template.
Let's
go
take
a
look
at
that.
So
this
is
the
deploy
PR
workflow
that
goes
off.
You
can
see.
I've
called
this
deploy
to
Azure
for
review.
So
what's
happening
here
is
first
thing:
I'm
doing
is
I've
got
pull
requests
targeting
the
master
branch,
so
this
is
gonna
run
anytime.
Somebody
raises
a
pull
request
to
targets.
C
But
I
can
also
use
a
conditional,
which
is
another,
very
powerful
feature
of
action
to
say.
Well,
if
I
don't
find
the
exact
version
I
want,
I
can
go
ahead
and
run
that
NPM
install
if
I
want
to,
of
course,
we're
going
to
build,
and
then
we
hit
our
first
action
from
a
partner.
In
this
case,
docker
has
created
a
great
set
of
actions
for
building
and
pushing
docker
containers.
As
you
can
see,
this
is
a
really
nice
action.
C
It
made
it
super
easy
for
me
just
to
supply
some
credentials
and
it
kind
of
takes
care
of
the
rest
includes
nice
features
like
being
able
to
say
which,
which
docker
image
I
want
to
try
to
use
as
a
cache
for
building
this
docker
image,
to
make
it
faster
all
right.
So,
let's
go
back
and
see
how
we're
doing
here.
C
All
right,
so
it
looks
like
if
I
look
at
my
deployed
to
review
here
and
ruby
has
finished.
That's
great.
So
if
I
go
back
and
look
at
the
pull
request,
I
should
now
have
an
environment.
So
the
first
thing
that's
happened
is
that
workflow
automatically
created
a
new
environment.
So
a
new
version
of
my
app
for
me
and
if
I
go
click
right
clicking
on
that
we
can
see
yep,
we
have
our
nice
new
version.
C
It's
got
its
own
URL,
so
it's
taking
advantage
of
a
nice
feature
of
this
particular
cloud
service
that
I'm
using
we
got
Ruby
sweet
I,
can
see
rails
being
that
number
one
starred
Ruby
application,
Ruby
repository
on
github,
fantastic,
so
I've
gone
through
and
I
said.
You
know.
I
think
this
looks
good,
it's
reviewed,
but
you
know
what
I'm
not
admin
right,
so
I'm,
just
a
developer.
I
can
write
code
perhaps
but
I
can't
necessarily
deploy
it
up
to
production.
C
So
what
I
want
to
do
is
I
could
have
somebody
else
come
in
and
I
want
to
go
ahead
and
deploy
this
guy.
The
staging
and
comment
on
that
and
right
away
I'm.
So
this
is
kind
of
interesting,
so
I've
added
this
command
here
I
said:
okay
deploy
to
staging.
What
does
that
do
so
I've
got.
You
can
see
a
couple
reactions
we
can
see.
Github
actions
has
seen
this
and
it's
dispatched
it.
So
let's
go
take
a
look
and
see
what's
happening
here,
so
we
go
back
and
we
look
at
our
workflows
again.
C
C
If
you
want
to
it's
only
going
to
run
for
pull,
request,
issue
types
and
then
it's
going
to
give
some
reactions
and
what
this
does
is.
This
rate
raises
a
repo
dispatch
of
it,
and
the
repo
dispatch
event
is
something
that
we
have
that
lets
you
kind
of
create
your
own
custom
events
and
github
actions
and
really
expand
on
what
they
can
do.
C
So
in
this
case,
we
see
I've
got
this
deployed
a
staging
workflow
and
what
it
does
is
it
takes
this
reap
repository
dispatch
for
the
deployed
command
and
then
does
a
bunch
of
really
cool
stuff
with
it.
So
it's
going
to
take
and
look
at
it's
going
to
log
me
into
a
shirks
I
happen
to
be
using
edge,
should
I
get
this
secret
and
then
the
first
thing
it
does
is
use
yet
another
community
action
that
sets
up
these
deployment
events.
C
So
you
saw
the
fact
that
I
had
that
nice,
environment
and
deployment
for
my
pull
request
that
included
a
link
out
to
everything.
Now
this
this
is
the
action
that
takes
care
of
it.
Does
it
for
me
and
with
this
dispatch
event,
you
can
see
I've
got
this
custom
client
payload,
so
here
I'm
able
to
use
the
fact
that
github
actions
contains
a
lot
of
detailed
information
about
what
triggered
them.
C
In
the
case
of
the
repository
dispatch
event,
it
can
have
a
custom
payload
in
that
great
action
written
by
Peter
Evans,
actually
attach
the
pull
request.
Information
so
I'm
able
to,
even
though
this
workflow
is
running
out
of
the
default
branch,
go
ahead
and
grab
the
pull
request.
Shah
from
it
so
I
know
I'm
deploying
the
right
thing
and
then
it's
going
to
go
ahead
and
deploy
my
deployment
to
staging.
So
if
we
go
back
and
look
at
our
pull
request,
we
can
see
yep
done
a
bunch
of
things.
So
hey
it's.
C
The
successfully
deployed
PR
13
to
staging,
which
is
really
cool.
If
I
click
here
I
want
to
see.
Well
what
happened
it
takes
me
right
to
the
run
that
did
it.
I
can
see
the
comment
happening.
I
can
see
the
deployment
to
Azure
and
if
we
go
back,
I
can
certainly
click
on
this
or
go
here
and
look
at
the
environment
and
say
yep
staged
he's
been
deployed.
Let's
go
up
and
see
that
I've
got
a
new
URL
here,
complete
with
that
ruby
language,
that's
fantastic
and
then
the
last
thing
I
want
to
do.
C
So
it's
going
to
take
my
staging
slot
and
it's
simply
going
to
swap
it
over
to
production,
make
sure
it's
warmed
up,
make
sure
it's
ready
to
go
and
do
some
additional
checks
for
me
and
then,
when
it's
all
done,
I'll
get
one
more
entry
here
into
this
environment,
so
I
can
see
what's
going
on
so
while
we're
waiting
for
takes
a
couple
of
seconds
to
do
this,
let's
go
ahead
and
check
on
the
progress
here.
So
we've
got
my
nice.
Deploy
to
production.
I
can
see
it's
running
swap
command
there.
C
Let's
go
check
on
our
job
alright,
so
this
is
at
a
swap
with
production.
Can
take
a
minute,
or
so
in
this
particular
case
I
actually
do
have
this
running
on
one
of
those
self-hosted
runners
that
I
mentioned
I'm
gonna
go
take
a
look
at
the
workflow
as
we
can
see,
it
looks
awfully
similar
to
the
one
that
we
did
for
for
staging,
but
we
can
also
see
that
we're
not
rebuilding
anything
so
we're
taking
advantage
of
some
good
practices.
C
We
built
that
container
once
we
tagged
it
with
a
particular
shot,
and
so
we
know
that
every
time
we
deploy
it,
you
know
whether
to
any
environment,
we're
not
rebuilding
we're,
not
getting
a
new
dependency.
We're
deploying
exactly
what
we're
testing
exactly
what
we're
validating
in
every
single
case.
C
It's
still
working
so
we'll
move
on
and
take
a
look
at
that
one
more
workflow
that
we
have
so
when
this
is
all
done.
I'm
gonna
check
this
deployed
production
I'm
going
to
merge
this
pull
request,
but
I
want
to
make
sure
that
I
don't
leave
any
cloud
resources
out
out
there
to
be
spending
money.
So
I
have
one
more
workflow
that
I'm
running
on
pull
request
closed
again
back
to
that
power
of
be
able
to
run
different
workflows
for
different
scenarios
for
different
events
every
time.
A
pull
request
is
closed.
C
That
is
targeting
master
I'm,
going
to
go
and
I'm
going
to
delete
the
review
app
that
I
had
created
for
that.
So
now,
I
can
make
sure
that
my
application
I
get
that
great
review
cycle.
I
get
that
each
instance.
My
pull
request
is
built.
I
can
push
them
through
to
different
environments,
using
chat
ups,
all
driven
through
actions
and
even
make
sure
I
clean
up,
and
you
know
keep
that
cloud
spin
down
with
actions,
so
I
was
sort
of
going
beyond
the
icd.
C
So
I
want
to
thank
everybody
for
coming
today
and
and
really
think
about
in
this
section
section.
What
we
covered
is
you
know,
sort
of
the
overall
power
of
actions,
what
we
can
do
with
it,
how
you
can
use
it
for
cin
CD,
how
you
can
use
github
actions
to
automate
things
to
Azure.
You
can
do
the
same
thing
to
Amazon
AWS
to
Google
gke.
C
You
know
using
there
are
some
actions
out
there
for
terraform
and
other
clouds,
and
finally,
how
community
is
really
part
of
our
vision
and
and
how
we
want
to
take
actions
forward,
and
you
know
that
demo
that
I
did
all
of
those
cool
things.
I
did
would
have
taken
me
a
very
long
time,
without
definitely
all
of
the
community
contributing
to
make
that
easy.
B
Thank
you
so
much
Chris.
Thank
you
so
much
Chris
for
that
amazing
presentation
on
get
up
actions
the
ability
to
turn
infrastructure
into
code,
not
only
that
what
I
find
the
most
fascinating
about
actions
is
the
community
add
into
actions
whether
it's
an
individual
developer
or
it's
a
partner,
putting
the
actions
in
the
marketplace
and
coming
to
market
place
and
seeing
it
grow
day
by
day.
B
So
remember
after
every
single
session
we
can,
you
can
ask
questions
and
discussions,
and
we
can
ask
those
questions
live
right
now,
so
moving
right
along
I
have
a
few
questions
for
you.
Chris
from
the
people.
Somebody
asked
will
actually
support
some
kind
of
user
interaction
like
input
step
in
Jenkins
some.
So
some
action
that
young
girl
could
ask
for
human
input
to
approve
or
decline
to
continue
workflow
or
I,
bought
it
with
canceled
or
fill.
What
is
the
general
roadmap
of
Arab
action.
B
B
Just
gonna
read
it
over
again,
so
that
we
are
all
on
the
same
page,
so
gross
WS,
get
abused
across
ws
Oh
gross
WS
says,
will
actually
support
some
kind
of
user
interaction
like
input
step
in
Jenkins,
for
example.
Some
action
that
Yama
could
ask
a
human
in
for
input
to
approve
or
decline
to
continue
or
cloak
or
bought
it
with
a
canceled
or
fail.
C
Yes,
it
is
absolutely
something
that
is
on
our
roadmap
to
do.
We
have
a
lot
of
great
things
kind
of
coming
in
that
particular
area.
You
know
that
idea
of
having
sort
of
manual
approvals
for
deployments
more
than
just
the
chat.
Ups
thing
I
showed
the
ability
to
trigger
manual
workflows
manually
to
request
specific
input.
C
A
A
C
B
C
So,
as
NAT
mentioned
this
morning,
github
actions
and
getup
packages
are
both
coming
to
github
Enterprise
Server.
We
plan
to
ship
that
later
on
this
year,
I
can't
divulge
the
exact
exact
date,
but
it
is
absolutely
happening
this
year.
We
are
working
incredibly
hard
on
that.
We
have
a
couple
of
different
plans
for
how
we're
going
to
let
people
use
the
community
so
in
the
in
the
box
or
with
Enterprise
Server,
we
will
ship
the
actions
that
we
github
have
produced
that
we
deem
safe
and
have
been.
C
You
know
we
check
the
security
and
we
know
who
builds
them
and
all
that
kind
of
stuff.
We
will
also
have
a
way
for
you
to
configure
your
Enterprise
Server,
to
reach
out
to
the
marketplace
and
be
able
to
potentially
use
anything
in
the
entire
marketplace
and
then,
finally,
obviously
for
those
security,
conscious
organizations,
we
actually
have
the
need
for
this
on
github.com
as
well.
Let's
get
up
Enterprise
Server.
C
We
will
provide
a
way
for
administrators
to
go
in
and
limit
the
set
of
actions,
maybe
there's
particular
orgs
or
so
they're,
saying:
hey,
we're
absolutely
happy
to
use
actions
from
AWS
or
from
Asia
or
from
a
Shi
Corp
or
docker.
But
we
don't
want
to
use
the
random
ones
in
the
marketplace.
Just
because
we
don't
know
the
Providence
or
if
there's
two
factor
auth
or
those
kinds
of
things.
B
C
Know
if
you
want
to
just
use
actions
for
some
of
those
sort
of
we
call
sdlc
events
you're
absolutely
welcome
to.
In
fact,
we
do
have
some
actions
that
we
ship
that
are
sort
of
breeding
our
first
time,
contributor
ones,
there's
a
whole
bunch
of
other
ones
in
the
marketplace.
So
if
that's
where
you'd
like
to
start
I,
think
that's
great
I'll.
A
Take
the
next
one
mode
you
so
we
have
one
from
Tinney,
tenem,
laker,
I'm.
Sorry,
if
I
butchered
that
that's
the
house,
that's
the
handle,
but
it's
a
great
demo.
Where
do
you
see
actions
have
the
biggest
advantages
compared
to
other
CI.
/Cs
may
be
that
most
supposed
to
be
CD
products
like
jenkins
or
get
lat
pipelines
I.
C
Really
think
that
the
the
coolest
feature
of
actions-
and
the
thing
that
makes
a
difference
is
the
fact
that
we
are
trying
to
focus
beyond
just
CI
CD.
We
absolutely
want
to
have
a
very,
very
flexible,
a
very
powerful
enterprise
class
CI
CD
system,
but
there
are
so
many
more
things
that
developers
automate
and,
as
we
add
more
things
into
github
and
into
the
github
family,
take
it
take
a
look
at
the
NPM
acquisition
like
as
you
know,
and
we
have
that
plus
we
have
dependent.
C
But
over
time
we
can
do
really
great
scenarios
like
hey
every
time.
Dependable,
recognizes,
there's
a
dependent
new
dependency
of
your
new
version
of
a
dependency
of
your
repo.
Could
we
fire
an
event
and
let
you
run
all
your
unit
tests
against
that
new
dependency
automatically
to
kind
of
get
yourself
a
litmus
test
of?
Did
they
break
you,
and
maybe
you
can
just
automatically
take
it.