►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
good
morning,
how's
everybody
doing
this
morning.
How
would
welcome
to
github
we're
so
excited
to
be
here
today?
I've
been
looking
forward
to
this
day
and
the
news
we're
going
to
share
with
you
here
today
for
months
and
the
whole
github
team
has
there's
a
lot
of
github
employees
here
in
the
room.
There's
a
lot
of
developers,
open-source
developers,
developers
locally
here
in
San,
Francisco
and
there's
thousands
more
folks
watching
on
the
various
livestream.
So
welcome
this
morning
to
get
up
very
excited.
A
This
is
the
second
time
in
about
three
and
a
half
months
that
we've
done
a
new
product
announcement
on
this
stage
and
it's
a
lot
of
fun.
It's
really
great.
We
do
one
announcement
super
crisp
and
exciting,
and
for
those
of
you
who
are
here
in
person,
the
github
employees
who
are
here
are
the
ones
who
built
the
product,
we're
announcing
so
they'd
love
to
talk
to
you
about.
You
know
what
you
think,
get
your
feedback
answer.
Your
questions,
that
sort
of
thing
before
we
get
into
our
announcement
today.
A
A
At
the
beginning
of
spring,
we
announced
the
github
package
registry
so
that
you
can
share
packages
for
private
and
public
repos.
You
get
a
feed
for
every
repo.
We've
had
an
awesome
reception
that
we
announced
the
acquisition
of
dependable,
create
automatic
security.
Remediation
pull
requests.
If
you
have
vulnerable
dependencies.
That's
now
free
for
all
developers
in
May,
in
Berlin,
we
announced
github
sponsors
which
allows
you
to
financially
support
the
developers
that
you
follow
on
github.
A
If
you
like
their
work,
if
you
want
them
to
do
more
of
it,
you
have
the
option
to
subscribe
and
give
them
your
patronage,
which
we're
very
excited
about.
It's
been
really
well
received
and
then
really
recently,
we
announced
pull
Panda
the
acquisition
of
pull
Panda,
which
helps
you
and
your
teams
more
productively.
Work
together
stay
on
top
of
pull
requests.
You
know
reduce
your
code
review
times.
A
Developers
are
a
lot
pull
panda
and
then,
just
last
month
we
released
github
desktop
2.0,
which
now
has
support
for
rebasing
and
stashing,
and
lots
of
other
great
features,
and
it's
just
been
an
awesome
run
for
the
last
six
months,
or
so.
This
isn't
everything,
though
this
is
really
just
the
tip
of
the
iceberg.
The
team
has
shipped
over
a
hundred
new
product
enhancements
just
this
year,
so
it's
been
awfully
busy.
A
The
team
has
worked
really
hard
here
at
github
and
I'm
happy
to
share,
though,
that
the
momentum
that
we're
seeing
is
not
just
in
our
engineering
teams
and
the
stuff
we're
shipping
in
the
product,
it's
in
the
community
as
well,
and
so
today,
I
want
to
share
with
you
that
more
developers
are
using
github
now
than
ever
before,
and
in
fact
just
this
week
we
hit
a
huge
milestone
with
more
than
40
million
developers
on
github.
This
is
astounding,
stat.
A
If
you
go
out-
and
you
read
industry
surveys,
people
will
say
there's
about
15
to
20
million
total
developers
in
the
world.
So
who
are
all
these
40
million
people?
Man?
That's
what
I
want
to
know
now
with
so
many
developers
on
github.
We
hear
all
the
time
from
you
from
developers
about
what's
exciting,
was
fun
and
also
what's
challenging
about
building
software
in
2019,
and
one
of
the
things
that
comes
up
again
and
again
is
the
need.
A
The
developers
and
teams
have
to
automate
manual
processes
so
that
you
can
focus
on
the
hard
problems
in
the
projects
that
you're
building.
So
you
can
do
the
creative
work
and
write
the
code
that
matters
and
automate
everything
else
eliminate
the
drudgery.
So
the
way
teams
typically
do.
This
is
there's
a
set
of
services
and
tools
that
are
out
there
and
you'll
kind
of
wire
these
together
and
connect
them
to
build
your
workflows.
A
So
at
the
end
of
2018,
we
introduced
github
actions,
which
is
a
platform
for
developer,
workflow,
orchestration
and
automation,
and
we
launched
it
at
our
big
annual
conference
github
universe
in
October
last
year
and
since
then,
tens
of
thousands
of
developers
have
been
using
actions
and
we've
been
getting
a
ton
of
great
feedback
and
your
creations
you've
been
releasing
them
publicly.
We've
seen
hundreds
of
really
creative
and
inspiring
actions,
open
sourced
or
released
on
the
github
marketplace,
but
over
the
course
of
the
last
nine
months
we've
been
receiving
tons
of
feedback
about
github
actions.
A
A
I
can't
tell
you
how
hard
people
have
worked
to
make
this
possible
and
when
we
decided
to
add
C
ICD
to
github,
we
didn't
want
to
just
do
it
the
basic
way
we
wanted
to
do
it
the
github
way
right.
What
does
that
mean?
It
means
doing
it
the
way
that
developers
want
it
to
work,
and
so
first
of
all,
github
actions
is
fully
integrated
into
github.
It's
built
in
from
the
merge
box
to
the
checks
tab
from
the
UI
to
the
API.
It
works
the
way
github
works.
A
Second,
we
know
that
you
want
to
run
jobs,
not
just
when
someone
pushes
new
code
or
on
a
pull
request.
You
want
to
be
able
to
trigger
workflows
on
any
github
event,
write
any
event
that
occurs
on
github
a
new
contributor,
a
new
issue.
Maybe
a
dependency
in
your
github
package
registry
gets
updated
and
you
want
to
trigger
a
workflow
based
on
that
any
event
where
there's
a
web
hook
that
you
can
listen
on
can
now
be
used
to
trigger
a
workflow
with
github
actions.
Third
community
is
really
at
the
heart
of
github.
A
Github
is
about
sharing,
so
anything
that
you
build
with.
Github
actions
is
shareable
because,
ultimately,
it's
just
code
in
a
repo,
so
you
can
make
it
public.
You
can
fork
it.
You
can
edit
it
build
on
it
and
make
it
yours
and
then
finally,
github
is
agnostic,
whatever
language
you're,
using
whatever
platform
you're
building
for
wherever
you're
deploying
your
code,
it'll
work
with
github
actions
and,
of
course,
because
it's
built
in
we
eliminate
all
the
drudgery
for
you,
there's
no
need
to
manually,
configure
and
set
up
C
icd.
A
You
don't
have
to
set
up
web
hooks,
you
don't
have
to
buy
hardware,
go
reserve,
some,
you
know
instances
out
there
keep
them
up
to
date,
security
patches
and
your
images,
spool
down
idle
machines.
None
of
that
we
do
everything
for
you.
You
just
drop
one
file
in
your
repo
and
it's
working.
So
the
best
way
to
understand
the
power
of
github
actions
is
actually
for
you
to
see
it,
and
so
please
welcome
my
colleague
from
the
github
actions.
Team,
Jeremy
Epling
come
on
up
Jeremy.
B
Really
excited
to
show
what
we've
been
working
on
for
the
last
couple
of
months,
with
github
actions
and
I'm,
just
one
person,
it's
part
of
a
big
team
across
all
of
github.
That's
been
making
this
happen
so
the
best
way
to
go
see
this
is
to
actually
see
it
live
and
in
action.
So,
let's
jump
into
a
repo.
What
I
have
in
this
reap
as
I've
built
a
simple
node
module.
That's
never
had
C
ICD
setup
at
all
and
I'm
going
to
show
you
how
easy
it
is
to
get
started
with
github
actions.
B
So
the
first
thing
I'm
going
to
do
is
just
go
over
here
and
click
on
the
actions.
Tab
right
in
this
repository,
one
of
the
things
that
you'll
notice
is,
we
automatically
suggest
it
a
set
of
workflows
to
help
you
get
started.
So
we
know
that
I'm
using
javascript
in
this
repository.
So
we
said:
hey
here's
to
sample
workflow
files
that
you
could
use
to
get
started.
One
of
them
sets
up
CI
for
a
node.js
app.
B
One
of
them
looks
at
a
package
and
not
only
does
CI
that
it
also
will
deploy
that
to
github
packaged
registry
and
to
NPM,
but
we
know
it
get
hubs
a
lot
more
than
just
a
single
language.
We
support
any
language
any
platform
in
any
cloud.
So
if
I
go
down
depending
on
what
my
repo,
what
the
code
is
in
that
you'll
notice,
we
have
starter
CI
templates
for
every
single
language.
You
can
imagine,
so
you
can
see
rust
Python
if
I
scroll
down
you
can
see.
B
We
have
many
many
more
of
these
just
to
make
it
really
easy
for
you
to
get
started.
But,
as
NAT
said,
get
up.
Actions
is
really
a
lot
more
than
just
CI
CD.
It
really
can
connect
all
of
the
different
tools
and
services
that
you
use
and
it
can
respond
to
any
event
on
github.
It
doesn't
just
have
to
be
a
code
push
or
something
like
that.
B
You
can
go
ahead
and
automate
that
if
someone's
a
new
contributor,
you
can
automatically
label
issues
based
on
files
that
are
changed
in
the
repository
or
label,
pull
requests,
and
you
can
automatically
mark
and
close
stale
issues,
and
these
are
really
just
the
beginning
of
what
I'm
excited
to
see
the
community
go
and
build
I.
Think
of
github
when
it's
at
its
best
for
really
a
canvas
for
developers
to
express
their
creativity
and
build
lots
of
cool
things.
B
So
let's
go
back
up
and
just
get
started
with
CI
CD,
so
I'm
going
to
click
right
here
and
set
up
this
workflow
and
what
you'll
notice
is
we
automatically
created
a
yeah,
my
workflow
file,
directly
in
your
repository,
so
we
have
a
very
easy
syntax.
That's
easy
to
go
and
learn
and
get
started
with.
We
have
a
simple
CI
template
again
set
up
right
here
and
then
you'll
notice
over
here.
We
actually
just
to
make
it
even
easier
to
get
started.
We
have
a
sample
of
some
of
the
common
thing.
B
B
So
go
over
here,
make
some
edits
to
this
yamo
file
and
because
it's
just
a
file
in
my
repository
I'm
gonna,
go
through
the
normal
process
of
committing
and
creating
a
pull
request.
So
we'll
go
through
and
create
a
new
branch
and
then
let's
go
ahead
and
kick
off
a
pull
request
and
what
you'll
notice
is
we
immediately
started
running
CI,
so
you
can
see
the
CI
jobs
coming
in
now,
where
we're
running
across
Linux
Windows
and
Mac
OS.
B
B
So
just
like
you
would
expect
from
anything
that
you
would
see
on
your
terminal.
You
see
here
right
here
in
all
of
its
glory
and
beauty.
So
over
here
you
can
see
we
already
finished
the
Linux
build.
The
max
build
is
running
as
well
and
then
Windows
is
coming
to.
Maybe
I
want
to
go
search.
My
logs,
though,
because
a
lot
of
the
times
I'm
looking
for
a
test
or
there's
an
error,
I'm
trying
to
go
find
so
I
can
go
over
here
and
look
for
a
specific
test.
B
Get
list
and
I
can
search
across
all
of
my
logs
right
there.
If
I
click
here,
I
can
do
other
things
too.
Maybe
I'm
debugging
a
time
sensitive
error
and
I
want
to
go,
show
timestamps
on
every
single
line.
Maybe
I
want
to
go
download
an
archive
of
all
the
logs,
so
I
can
get
all
the
logs
all
together
across
all
the
different
jobs
or
I
can
just
view
the
raw
logs
right
there
in
plain
text.
B
So
this
shows
you
how
easy
it
is
to
get
started,
but
let's
look
at
a
little
bit
more
interesting
case.
So
a
lot
of
open
source
is
really
about
building
and
deploying
packages.
So
let's
go
in
here
and
look
at
a
workflow
file
that
does
a
little
bit
more.
So
one
of
the
things
you'll
notice
is
right.
In
my
repository,
I
have
a
dot.
Github
folder,
with
workflows
and
I
can
have
multiple
different
workflows
in
there.
B
B
So,
let's
click
on
the
CI
yeah
Mille
and
see
a
little
bit
more
interesting
case
here.
One
of
things,
you'll
see,
is
I
named
this
workflow,
so
it's
my
CI
workflow
over
here
you'll
notice,
this
on
of
it.
This
is
where
you
can
specify
the
trigger
for
your
workflow
and
we
work
with
any
events
that
happens
on
github,
but
not
just
events
that
happen
on
github.
B
You
can
go
ahead
and
trigger
workflows
off
those
as
well
or
github
events
as
well,
so
just
to
show
you
that
I
can
show
you
the
broad
list
of
events
that
we
support
here,
and
it's
just
about
everything
you
can
imagine
editing
on
a
wiki
uploading,
a
package
to
github
package
registry,
doing
a
deployment,
a
comment
on
an
issue
when
a
label
is
created
any
of
those
events.
You
can
automate
so
down
here.
What
I've
done
is
for
this
one
at
CI,
so
I'm
just
doing
a
couple
code,
events
so
I'm
doing.
B
Okay,
let's
go
ahead
and
kick
this
off
on
a
purl
pull
request
happens,
but
I
only
want
to
do
that
if
the
pull
request
is
targeting
the
master
branch
and
the
same
for
push,
so
we
have
built-in
filtering
as
well.
We
can
filter
on
branches
in
the
NOSSA
file
paths
and
again
many
more
things
down
below
here.
You
can
see
the
jobs
that
are
running
in
the
build,
so
we
have
a
matrix
strategy
running
right
here,
so
this
one
is
doing
a
little
bit
more.
It's
not
just
building
across
three
different
operating
systems.
B
It's
also
building
across
multiple
different
versions
of
node
as
well,
and
this
doesn't
have
to
be
node.
It
could
be
go
or
any
other
runtime.
So
what
this
is
doing
is
really
multiplying
this
out,
so
there
will
be
nine.
Simultaneous
jobs
kicked
off
at
the
same
time.
So
what
that
allows
you
to
do
is
really
speed
up
your
testing
and
deployment
processes
by
doing
all
this
much
faster
and
getting
a
much
broader
set
of
testing
down
here.
B
These
are
the
individual
steps
that
are
running
inside
this
job,
and
this
is
where
it
gets
really
exciting
for
me
to
think
about
github
actions,
one
of
the
things
you'll
notice
is:
we
have
this
users
command
right
here,
so
this
lets
you
reference
an
action
that
lives
in
another
repository
and
one
of
the
awesome
things
about
this.
Is
you
don't
have
to
go,
install
an
action
or
a
deal
with
any
of
that
or
install
a
github
act
just
to
be
able
to
leverage
another
action?
B
All
you
have
to
do
is
put
a
javascript
file
inside
a
repository,
and
that
is
an
action.
So
let's
go
over
here
and
see
this
one.
This
one
is
living
in
the
actions
or
we're
going
to
github
into
setup,
node
repository
and
the
version
of
that
one
I'm
picking
is
just
a
branch,
so
that
could
be
a
branch
or
a
tag.
B
So
one
of
the
things
that
you'll
know
right
here
again,
actions
are
just
a
repository,
so
we
can
go
into
a
drill
into
the
source
for
this
and
we
can
see
we
wrote
this
one
in
typescript
and
again
this
is
just
a
JavaScript
file
setting
in
a
repository.
That's
how
easy
it
is
to
get
started
with
github
actions.
Again,
when
you
think
of
the
evolution
of
where
that
github
platform
has
come.
B
Originally,
we
had
commit
status
where
you
could
just
post
some
basic
data
to
let
people
know
hey:
is
this
good
or
bad
is
or
something?
Then
we
had
github
apps
where
you
could
extend
now
you
don't
even
have
to
worry
about
setting
up,
compute
or
deploying
a
server
or
anything
like
that.
You
just
go
ahead
and
check
a
javascript
file
into
a
repo,
and
anyone
on
the
entire
github
community
can
go
ahead
and
leverage
that
so
we're
running
that
for
you
right
in
the
github
cloud.
B
So,
let's
jump
back
to
our
workflow
file
and
in
addition
to
having
these
different
actions,
you
can
obviously
pass
in
parameters
for
those
actions
just
using
width,
and
then
we
also
support
running
inline
scripts,
so
any
tool
that
you
can
imagine
that's
out
there.
That
has
a
COI
github
action
supports
it
down
below
here.
Obviously,
I've
kicked
off
a
lot
of
these
build
and
tests
all
simultaneously
for
a
fan
out
scenario.
B
Now,
I
want
to
fan
back
in
to
actually
publish
my
packages,
so
in
this
case,
I
have
two
publishes
going
in
parallel,
so
you
can
see
I'm
publishing
two
NPM
right
here
and
then
I'm
also
publishing
to
github
package
registry,
and
this
needs
is
basically
saying
hey
whenever
the
build
completes,
whenever
all
those
completes
go
ahead
and
kick
these
off
in
parallel
and
what
you'll
notice
is
obviously,
when
I
publishing
to
NPM.
The
last
thing
I
want
to
be
doing
is
checking
my
credentials
into
my
source
code.
B
So
get-up
has
a
built-in
secret
store
to
make
it
easy
to
go
ahead
and
deploy
to
any
package
registry
or
to
any
cloud
and
you'll
notice
right
here.
I
just
set
an
environment
variable
and
I
said
here's
my
token
and
then
I
do
secret
NPM
token,
and
then
that's
how
I
reference
our
secret
store.
But
let
me
show
you
where
that
is
it's
right
in
your
repository.
So
if
you
just
click
on
settings
and
then
you
go
over
to
Secrets,
you
can
see
my
tokens
right
there.
B
C
As
you
might
know,
Yan
is
a
quite
large
open-source
project,
and
that
means
that
we
have
to
interact
with
a
lot
of
different
people,
users
and
contributors
alike,
in
order
to
make
it
work.
What
you
might
not
know
is
that
we
are
also
a
very
small
core
maintainer
team,
so
in
this
context
anything
we
can
do
to
decrease.
The
maintenance.
Friction
is
welcome,
be
the
time
spent
running
CIS
or
repeal
to
request
a
review
process
or
is
hugely
aging
everything
we
can
trim
else.
C
C
So
one
thing
I
did
in
particular
was
about
reproduction
cases,
see
one
of
the
problem
we
have
when
working
in
the
open
source
is
that
we
often
get
issues
and
most
of
this
time
isn't
spent
actually
fixing
those
issues.
Most
of
the
time
is
often
spent
trying
to
understand
the
issues,
try
to
figure
out
how
to
reproduce
it
is
it
actually
a
problem?
Why
can't
I
reproduce
it?
C
For
example,
if
I
want
to
release
a
new
version
of
the
project,
then
the
bot
can
just
check
whether
all
the
upend
issues
are
still
a
valid
or
not.
So
this
kind
of
automation
is
extremely
valuable
for
us,
because
working
in
the
open-source
I
dimension
is
extremely
time
consuming.
So
the
last
time
we
have
to
spend
on
the
maintenance
side
is
the
more
time
we
can
spend
on
the
building
the
project,
which
is
what
really
matters
even
better.
B
B
That's
what
gets
me
up
every
day,
it's
like.
Why
do
I
love
to
work
at
github,
I
love
to
see
what
developers
can
do
with
the
platform
we
build.
It's
just
so
exciting
and
I.
Think
that
actions
is
this
brand
new
part
of
the
github
platform.
That'll
really
expand
it
out.
You
don't
have
to
worry
about
running
your
code.
You
don't
have
to
worry
about
our
runtime.
B
You
can
just
write
some
JavaScript
and
automatically
automate
anything
that
happens
on
github
or
anything
on
the
entire
github
ecosystem,
and
it's
just
amazing
to
see
what
people
will
build
and
I
know.
This
is
just
the
beginning.
People
are
gonna,
be
remixes
actions
into
different
workflows
and
because
they're
just
files
in
a
repository,
you
can
go
to
any
open
source
project.
You
can
go
up
to
yarn
and
be
like
I
love.
The
way
yarn
works.
Let
me
see
what
those
are
you
can
go
ahead
and
fork.
You
can
look
at
those
workflow
files.
B
B
So
we've
shown
you
a
couple
different
examples
here,
but
obviously
we
can
do
a
lot
more
than
build
test
and
publish
packages,
another
core
scenario
in
a
CI
CD
for
web
services
as
well.
So
what
I
got
here
in
this
repository
is
I'm
actually
building
a
container
testing
it
and
then
I'm
deploying
it
to
multiple
different
clouds.
B
So
let's
go
ahead
and
open
up
this
workflow
file
and
one
of
the
things
you'll
notice
again
familiar
syntax
at
the
top
on
like
and
subscribe
to
any
event.
I'm.
Looking
at
a
couple,
different
events
here
and
then
I
have
this
build
job
again,
I'm
checking
out
using
a
built
in
action
and
then
I'm
just
running
a
script
right
here
to
go
ahead
and
build
a
docker
image
and
then
push
this
to
get.
How
package
registry
down
here
below
I'm
immediately
kicking
off
the
deployment
that
I
could
have
had
my
event?
B
But
again,
this
is
how
easy
it
is
just
to
get
set
up
to
deploy
to
any
cloud.
That's
out
there.
So
now,
let's
go
over
here
and
look
at
a
pull
request
that
I
merged
a
little
bit
ago
and
see
what
the
output
of
one
of
these
looks
like
so
go
over
to
the
checks
and
just
as
you
saw
before,
we
have
live
logs
that
are
all
right.
There.
I
can
go
ahead
and
open
this
up
right
here
and
see
the
output
of
what
happened
while
I
was
building.
This
docker
container
image
so
you'll
notice.
B
We
also
have
code
folding
built
directly
in
as
well,
so
this
allows
you
to
really
focus
on
what
matters
when
you're
reading
the
logs
and
not
get
kind
of
drowned
and
repetitive
output,
one
of
the
cool
things
that
we
do
here,
though,
is
we
actually
color
code
and
highlight
the
exact
lines
of
what
you
wrote
in
your
file.
So
you
can
easily
see
what
did
you
wrote
and
how
did
we
interpret
that?
So
in
this
case
we
took
this
and
turned
it
into
a
shell
script,
just
to
execute
it.
B
But
again,
if
you
have
pass
parameters
or
anything
like
that,
you'll
be
able
to
see
all
that
right
there
and
then,
if
I
scroll
down
you'll
notice,
we've
automatically
color-coded
this
warning.
So
maybe
this
was
an
error
or
a
warning
actually
I'm,
not
really
sure
what
this
is
telling
me
so
I
want
to
go
share
this
with
somebody
else
and
get
some
help.
What
I
can
do
is
just
come
over
here
and
with
one
click.
I
can
copy
a
link
directly
to
that
line
in
the
logs
go
over
here
and
you'll
notice.
B
The
entire
page
will
refresh,
we
will
go
ahead
and
scroll
the
logs
down
directly
to
the
line,
and
then
you
can
see
that
that
line
is
already
highlighted
so
again
when
you're
going
to
someone
else.
Instead
of
telling
them
hey
open
up
this
stuff,
go
to
this
line,
number
they're
digging
they're.
Looking
for
what
it
is,
you
can
send
a
line
directly
to
what
they
need
to
do
to
keep
them
in
their
flow.
B
D
Mean
atharva
I'm,
the
founder
and
CEO
of
lunch.
Dirkly
lunch
directly
helps
software
teams
worldwide,
deliver
and
control
their
software
feature.
Management
is
a
best
practice.
That's
used
by
our
customers
like
NBC,
Intuit
and
BMW,
and
then
we
serve
over
300
billion
features
a
day.
So
I'm
really
passionate
about
feature
flagging,
and
here
is
what
I'm
excited
about
in
particular,
is
a
major
complaint
about
feature.
D
Flagging
is
technical
debt
so
to
back
up
a
little
bit
a
feature
flag
is
a
way
to
ship
a
bit
of
code
off
and
then
selectively
turn
it
on
for
different
people.
So
this
is
the
launch
darkly
dashboard,
and
here
we
have
a
show
Live
Tiles
feature
that
we
selectively
enabled
to
turn
on
to
people
after
a
certain
date.
You
can
also
do
stuff
with
us
like
a
kill,
switch
and
even
do
a
progressive
rollout
with
some
people
at
a
time.
So
this
features
live.
D
D
So
with
github
actions,
we
added
this
feature
of
code
references
and
this
tab
allows
you
to
click
in
and
see
exactly
all
the
places
where
a
feature
is
used
and
then
you
can
go
and
view
it
in
source
and
it
jumps
down
to
exactly
where
it
is
in
your
source
so
that
you
can
really
easily
clean
it
up,
and
this
is
all
enabled
by
actions.
So
we've
built
an
action
here
where
every
time
somebody
checks
in
code,
it
is
pushes
out
to
lunch
directly
exactly
where
the
code
is
used.
D
So
now
we
have
a
workflow
where
a
developer
could
say
when
a
code
when
a
feature
is
completely
rolled
out,
they
can
go
in
exactly
where
it
is
pull
it
out
and
then
have
a
much
tidier
code
path
without
stale
code,
and
this
is
all
enabled
by
an
extremely
simple
yamo
file.
This
is
just
18
lines
of
code,
so
very
simple
and
very
easy
to
use.
D
D
A
Okay,
Thank
You,
Jeremy,
Mel
and
Edith.
Isn't
that
awesome
pretty
excited?
Let's
recap
a
few
of
the
highlights
of
what
you
just
saw
and
some
of
the
reasons
that
we're
excited
about
github
actions.
So,
first,
your
github
actions
can
run
in
a
container
or
on
a
virtual
machine
with
support
for
Linux,
Mac,
OS
and
Windows
actions.
Support
matrix,
builds
natively
so
that
you
can
run
parallel
jobs
across
operating
system
versions,
runtime
versions
or
any
variable.
A
You
want
to
use
to
multiply
your
workflows
and,
as
Jeremy
showed,
actions
have
built-in
support
for
real-time
feedback
in
the
form
of
streaming
logs
that
are
searchable,
support,
colors
emojis
and
our
deep
linkable
that
you
can
use
to
help.
You
know
pinpoint
a
log
wine
and
send
that
to
a
friend
or
colleague.
We
know
that
a
lot
of
the
work
that
you
need
to
do
with
github
actions
and
in
your
workflows
involves
integrating
third-party
services
and
tools
and
to
do
that
securely.
You
don't
want
to
put
your
tokens
in
your
source
code.
A
You
need
a
secret
store,
and
so
every
repo
on
github
now
comes
with
a
secure
secret
store
where
you
can
store
your
secrets,
update
them
easily
and
then,
of
course,
because
it's
github
actions
are
easy
to
write,
they're
easy
to
share.
You
can
build
on
them,
and
this
is
really
I.
Think
for
me
at
the
core
of
what
we're
doing
here
right.
A
Our
world
view
at
github
is
this
view
that
software
development
is
actually
a
global
team
sport
and
we
often
think
about
developers
is
working
in
isolation,
kind
of
solo,
on
projects
alone
in
their
rooms.
But
the
truth
is
that
every
line
of
code
we
write,
builds
on
the
work
of
thousands
of
other
developers
and
with
github
actions,
because
your
workflows
are
just
code
right
you,
you
can
now
build
on
people's
workflows
too.
So
we're
really
excited
to
open
up
this
possibility
for
all
of
us
to
learn
from
the
world's
most
productive.
Most
inventive
teams.
A
I
was
also
super
blown
away
by
Mel's
action
that
he
demoed
earlier,
where
he
can
automatically
check
issues
that
get
filed
to
see
if
they're,
reproducible
or
not
like
that's
an
incredible
creative
idea.
Now
we
can
all
go
to
metals,
repo
and
learn
from
that,
so
I
think
that's
incredibly
exciting
and
so
to
make
this
possible,
we
are
making
github
actions
completely
free
for
public
repositories.
So
if
the
open
source
community.
A
Our
aim
is
to
support
any
community
that
chooses
to
use
github
actions
for
CI,
CD
or
workflow
automation
now
for
private
repos,
we're
gonna
offer
really
simple
pay-as-you-go
per
minute
pricing.
Every
github
user
will
get
a
bunch
of
free
minutes,
whether
you're,
a
free
user
or
whether
you're
paying
us
to
get
you
started
and
then
above
that
you'll
just
pay-as-you-go,
so
you'll
get
anywhere
between
two
thousand
minutes
a
month
for
free
accounts
up
to
50,000
minutes
a
month
included
in
your
github
planned
for
enterprises.
A
And
then,
if
you
need
extra
minutes,
we
have
really
competitive
great
pricing,
different
prices
for
Linda,
Linux,
Windows
and
Mac,
and
so
by
including
these
offers
in
every
github
plan
and
by
making
it
have
actions
free
for
public
repositories.
We
are
enabling
40
million
developers
around
the
world
to
leverage
github
for
CI
CD
and
for
workflow
automation,
out-of-the-box
at
no
extra
cost
really
excited
about
that.
Now.
A
If
you
don't
want
to
run
on
our
machines,
you
don't
have
to
later
this
year
we
are
going
to
release
an
open-source,
our
runners,
so
that
you'll
be
able
to
run
all
these
actions
all
these
workflows.
All
these
builds
and
your
own
machines
for
free
at
no
cost
to
you
at
all,
it'll
work
on
Linux,
Windows
and
Mac.
It's
the
same
one
that
we're
running
up
on
our
hardware.
It's
super
portable
runs
on
x86
runs
on
arm.
A
You
can
even
run
it
on
a
Raspberry
Pi
if
you
want
to
so
we're
pretty
thrilled
about
this
look
forward
to
getting
your
pull
requests.
Now
you
heard
from
now
and
the
yarn
project,
but
over
the
last
several
months,
we've
been
so
lucky
to
get
to
work
with
a
bunch
of
really
great
open-source
projects
on
github
actions.
These
are
all
projects
that
have
been
using
actions
and
providing
us
with
feedback.
A
They
include
awesome
communities
like
Syfy
and
bootstrap
and
Ruby
and
numpy
and
others,
and
so
later
today,
you'll
be
able
to
go
to
some
of
these
repos
like
yarn
and
bootstrap,
and
just
look
at
their
workflow
files,
see
how
they're
using
actions
learn
from
them
and
build
on
them.
We're
also
incredibly
lucky
at
github
to
be
working
with
some
of
the
biggest
companies
in
the
world,
and
so
we
want
to
offer
our
thanks
to
companies
like
UBS.
Doubt
Philips
an
SI
P
for
all
their
great
feedback
on
github
actions.
A
So
far
as
well,
you
know
thousands
of
developers
at
these
companies
rely
on
github
every
single
day
to
do
their
jobs
and
we're
honored
to
have
the
opportunity
to
serve
their
workflow
automation
and
CI.
Cg
needs
as
well.
Now
one
of
the
things
that
I
find
most
amazing
about
github
is
it's
not
just
a
tool
that
you
use?
A
It's
also
a
platform
that
developers
around
the
world
can
extend,
and
every
day
we
see
these
different,
creative
and
unexpected
ways
that
developers
and
companies
are
extending
github
expense,
extending
developer
workflows
using
the
github
platform
and,
as
Jeremy
said,
what's
really
exciting
about
github
actions.
Is
it
makes
the
platform
more
rich?
It's
a
richer
platform,
there's
more
new
ways
that
you
can
extend
the
platform.
There's
new
api's,
there's
new
events
that
you
can
listen
to
and
any
github
app
can
also
generate
its
own
custom
events
that
can
trigger
workflows.
A
So
there's
a
real
extensibility
play
here
that
we
think
is
really
exciting
for
developers.
Any
third
party
like
launch
Darkly
can
use
actions
to
trigger
a
CI
CD,
build
or
any
other
workflow
and
can
listen
on
any
event,
and
then
you
as
developers
and
your
teams,
can
choose
any
tool
in
the
world
to
integrate
with
github
through
get
up
actions
very
easily,
whether
that's
one
of
our
partners
like
launch
Berkeley
or
code
curve
or
coveralls
or
another
CI
vendor
like
circle
CI
or
code.
Fresh
github
gives
you
the
choice
and
that's
very
important
to
us.
A
So
we're
working
with
all
the
companies
that
are
listed
here
to
provide
great
integration
with
github
actions,
and
some
of
these
have
already
released
some
integration,
and
some
of
it
will
be
coming
soon.
I
personally
can't
wait
to
see
what
the
community
does
on
github
actions
and
to
see
more
creative
ideas
get
released
and
for
us
all
to
get
to
learn
and
kind
of
work
like
the
best.
So
you
can
actually
get
started
doing
that
today
by
signing
up
for
the
beta.
A
A
A
It's
coming
and
we'll
be
letting
a
new
signups
in
aggressively
over
the
course
of
the
next
month,
but
we
are
not
going
to
be
in
beta
for
long
in
fact,
we're
planting
a
stake
in
the
ground
today,
because
github
actions
will
be
generally
available
on
github
for
all
users
on
November
13th
this
year.
That's
in
97
days.
A
There
will
be,
there
will
be
97
day,
countdowns
in
front
of
every
github
developer
over
the
next
and
github
package
registry,
we're
also
planning
to
make
generally
available
at
the
same
time.
So
that's
that's
just
97
days
away.
Please
give
it
a
try,
send
us
your
feedback.
People
seem
to
have
no
trouble
finding
me
on
Twitter,
so
continue
to
do
that.
It's
totally
fine
November
13th
is
also
a
special
day
for
us,
because
it's
the
first
day
of
our
annual
developer
conference,
github
universe,
where
we
first
unveiled
github
actions.
A
Last
year,
it's
here
in
San,
Francisco,
it's
November,
13th
and
14th,
and
in
addition
to
the
news
that
we
just
made,
we've
got
some
other
major
product
announcements
that'll
be
coming
out,
then
that
we're
really
excited
about
so
tickets
are
on
sale
now
and
we
hope
you
can
join
us
in
person.
Ok,
the
github
team
has
worked
awfully
hard
to
get
to
this
day.
This
is
the
culmination
of
a
ton
of
work.
We
are
so
excited
that
we
got
to
share
it
with
you.