►
From YouTube: Opening Keynote - GitHub Universe 2018
Description
Learn about what's new in the GitHub Universe from Sam Lambert, Kyle Daigle, Kathy Simpson, Omoju Miller, and Jason Warner, including the debut of GitHub Actions.
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
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
B
Morning,
everybody:
what
would
you
see
y'all
here,
9:00
a.m.
for
a
Developer
Conference,
it's
quite
a
good
turnout.
So
to
start
things
off
right,
I
figured
I'm,
gonna,
go
right
off
script
and
Luke
happy
11th
birthday
and
cuz.
My
son
he's
my
oldest.
He
couldn't
be
here
today,
but
figure
might
as
well
share
that
with
a
hundred.
What
is
this
fifteen
hundred
people
and
a
couple
hundred
thousand
around
the
world?
B
Remember
when
I
found
programming
for
the
first
time
senior
year
of
high
school
I
had
that
same
feeling
with
software
development
and
developers
in
general,
like
they
could
invent
anything,
and
it
was
that
feeling
that
kind
of
drew
me
in
and
led
me
to
believe
that
this
is
what
it
was.
What
I
was
going
to
do
for
my
next
couple
of
decades,
but
as
you
do
something
that
sense
of
awe
and
wonder
that
you
first
had
kind
of
fades.
B
We
all
have
that
experience
with
things
that
you
know
incredibly
well,
but
for
me
today
feels
like
one
of
those
special
days
again
now.
I
have
the
privilege
to
see
what
we've
been
working
on
for
this
past
year
and
we're
here
to
share
that
with
you
today
and
I
hope
that
you
have
that
same
feeling
today,
when
you
see
what
we're
building
so
welcome,
welcome
to
github
universe,
this
event
has
been
crafted
entirely
around
you,
the
developers
around
the
world.
This
is
our
premiere
event.
It's
not
our
developer
event,
its
github
event.
It's
your
event!
B
It's
the
developers
event
for
the
world.
This
is
our
fourth
universe.
Now
is
our
first
of
the
Palace
of
Fine
Arts,
and
this
venue
feels
pretty
fitting
for
this.
Today.
It
was
built
in
1915
for
the
pant
panama-pacific
exposition,
which
is
was
the
years
long
showcase
of
the
technology
at
the
time
that
was
gonna
change
the
world.
So
we
love
that
little
bit
of
history
for
what
we're
gonna
do
today
now,
because
today
we're
here
to
deliver
part
of
our
vision
for
the
future.
We
want
to
share
with
you
and
Grand
github
spirit.
B
B
So
as
you
all
know,
github
is
celebrated
its
10th
year
anniversary.
It's
a
decade
is
a
long
time
and
tech.
As
you
all
know,
trends
come
and
go
fashion
and
software
changes
all
the
time.
But
this
and
I
believe
that
these
past
10
years
have
been
some
of
the
most
transformative
in
tech.
I,
don't
know
what
were
you
all
doing
10
years
ago,
what
were
you
programming
10
years
ago,
as
I
mentioned
before
I
had
just
become
a
new
dad.
I
was
writing
lots
of
Java
code?
Not
JavaScript.
B
B
All
three
of
those
topics,
weren't
going
well
at
the
time
10
years
ago.
Look
back
on
your
own
lives.
What
were
you
doing
10
years
ago?
What
were
you
programming
in?
What
were
the
things
that
you
were
betting
on
from
a
technology
standpoint?
What
trends
did
you
think
that
we're
gonna
take
over
that
aren't
even
relevant
anymore?
Ten
years
in
tech
is
a
long
time.
B
B
How
many
large
corporations
are
not
just
believing
in
open
source
and
investing
in
it,
but
actually
like
all-in
on
open
source?
It's
been
a
pretty
amazing
change
in
just
10
your
time,
but
what
else
has
happened?
I
mentioned
Java.
Well,
it's
now,
JavaScript
half
of
the
world
is
trying
to
outsource
their
software
development
instead
of
understanding
that
that
was
their
competitive
advantage
and
the
most
amazing
change
I
think
in
the
past
10
years
is
that
software
developers
have
become
the
most
sought-after
category
of
employees
in
the
world.
B
B
Look
this
one
up,
so
the
modern
world
is
run
by
software,
but,
as
we
said
it
wasn't
always
this
way
and
github
launched
in
2008
at
a
time
when
technology
was
just
starting
content
to
connect
people
around
the
world,
I
was
doing
it
in
new
and
interesting
ways
and
it
was
trying
to
challenge
norms
at
the
time.
So
we
have
our
founders.
B
So
now
I
want
to
actually
walk
through
some
of
the
ten
year
history
of
what
we've
been
doing
so,
as
you
know,
github
launched
in
April
2008,
we've
tweeted
about
this.
A
bunch
first
line
of
code
is
out
there.
It's
pretty
pretty
remarkable
story,
but
we
never
really
understood
what
we
were
doing
at
the
time.
In
all
likelihood,
you
know
you
can
see
things
in
retrospect
and
look
very
smart,
but
you
know
honestly,
most
people
don't
actually
know
how
big
something
is
going
to
get
at
launch.
B
We
also
launched
with
an
API
service
hooks
and
web
hooks
from
the
very
beginning.
It
was
important
that
this
could
be
connected
to
all
of
the
other
tools
at
the
time
and
at
the
time
the
the
two
predominant
tools
I
connected
to
github
were
campfire
and
lighthouse.
Anyone
still
use
campfire
and
lighthouse
around
here
they
changed
tools
quite
a
bit
and
the
first
version.
Here's
a
fun
fact
about
the
first
version
of
the
API
for
github.
It
returned
a
Yambol
type.
B
Imagine
doing
that
in
2018
and
from
the
very
beginning,
other
companies
around
the
world,
like
travis,
has
started
a
hook
in
and
connected
github
to
do
things
that
they
wanted
to
get
done.
With
this
in
late
2010,
we
launched
the
this
version
of
polar
crest,
mostly,
as
you
all
know,
and
love.
Today
we
had
a
version
of
polar
crest
just
before
this
one,
but
this
is
this
was
the
the
new
version
of
polar
quest
to
point
out.
B
This
was
probably
about
the
time
that
social
coding
really
came
into
effect
on
the
platform.
People
really
start
to
have
conversations
around
code
and
the
first
pull
request
represented
that
step
to
making
code
infinitely
more
approachable
for
people.
Anybody
can
have
conversation
around
code
today.
Poll
requests
are
the
gold
standard
of
code,
collaboration.
B
Early
on,
we
realized
that
we
needed
to
work
where
you
all
worked.
Not
all
of
you
worked
out
in
the
open,
as
I
mentioned
before.
Sas
software
had
not
taken
hold
as
it
does
today
in
the
world,
so
we
needed
to
meet
you
where
you
were
so.
We
launched
github
Enterprise.
We
built
github
Enterprise
as
a
way
to
run
github
wherever
you
needed
it
as
software
developers
to
take
excuses
off
the
table
for
corporations
to
be
able
to
use
it.
B
B
Everyone
knows,
Adam,
we've
got
over
2
million
active
users
on
Adam,
it's
a
very
successful
open
source
project,
but
what
I
think
is
most
remarkable
about
it
is
that
at
the
time
it
set
off
an
editor's
arm
race,
and
now
you
wouldn't
have
things
like
vs
code,
or
even
some
of
the
IDE
integrations
that
you
have
today.
If
Adam
didn't
come
out
and
in
fact
the
hackable
nature
of
Adam
was
so
revolutionary
at
the
time
that
it
caused
other
things
to
happen.
B
What
you'll
see
here
in
a
minute
with
electron,
we
removed,
we
pulled
electron
out
of
atom.
Electron
was
actually
what
we
call
atom
shell
when
it
first
started,
and
it
was
the
basis
of
how
we
built
atom.
It
was
all
based
around
web
technologies
that
the
founders
and
early
at
github
employees
were
using
to
build
github
of
at
that
time,
and
today,
electron
is
such
a
popular
open-source
project
and
a
foundation
for
most
of
the
desktop
applications
that
many
of
us
use
every
day
that
it's
now
changed.
B
The
way
many
people
around
the
world
work,
if
you
don't
know
which
I
think
most
of
you
probably
do
atom,
github,
desktop
visual
studio
code,
Skype,
figma,
discord,
hyper
terminal,
insomnia,
rest
client
for
all,
based
upon
an
electron
continuing
with
the
theme
of
changing
things
up
and
moving
a
into
new
spaces.
We
launched
github
business
cloud
and
2017
business
cloud
was
a
new
way
for
businesses
to
work
seamlessly
with
developers
around
the
world
in
the
in
a
safe
space
way.
It
had
all
the
same
enterprise
controls
it
had
all
the
same.
B
Provisioning
and
user
management
systems
as
github
Enterprise
and
a
couple
of
other
things
that
didn't
get
hub
cloud
is
again
a
way
for
us
to
say
we're
gonna
meet
you
where
you
are.
We
want
you
all
to
have
access
to
all
the
tools
that
everyone
around
the
world
should
have
access
to,
and
we're
going
to
do
the
things
that
we
need
to
do
to
give
you.
Those
2017
was
a
rather
busy
year
for
us.
B
We
also
shipped
github
apps
and
a
large
portion
of
our
graph
QL
API
via
hub
apps,
represented
a
brand
new
way
for
you
to
develop
on
github
I
had
much
more
granular
controls
and
permissions.
It
gave
you
access
to
repositories
only
the
ones
that
you
need
to
do
not
go
off
a
style
just
on
the
org
or
on
the
account.
It
was
a
much
more
modern
way
of
working
and
in
fact,
we've
been
using
github
apps,
almost
exclusively
internally,
with
the
graph
QL
API
to
develop
almost
everything
that
you're
gonna
see
here
today.
B
Two
other
things
we
launched
in
2017
the
github
marketplace.
If
you're
going
to
develop
applications
on
github,
there's,
you've
got
to
find
a
way
to
get
them
out
to
the
world
and
with
31
million
developers
on
github,
we
wanted
to
give
a
venue
for
people
who
are
developing
applications
for
developers
to
showcase
them.
That's
what
we
did.
B
Github
marketplace
is
a
place
for
all
developer,
oriented
folks
to
put
their
their
code,
their
software,
their
projects,
their
applications
out
there,
not
only
that,
we
thought
it
was
incredibly
important
that
the
31
million
developers
have
a
place
to
go,
find
other
things
themselves
right
now.
Most
people
are
installing
integrations
off
the
github
marketplace
in
spaces
like
CI
CD,
even
slack
integrations,
but
we
expect
that
will
change
over
time
as
more
and
more
applications
get
developed
and
pushed
into
the
marketplace.
B
Lastly,
and
probably
one
of
the
more
significant
things
that
we
really
saw
last
year
was
the
security
vulnerability
alerts.
This
was
the
most
recent
platform
wide
service
for
around
languages,
JavaScript,
Ruby
and
Python
with
more
to
come.
But
we
wanted
to
make
sure
that
since
we
sit
at
such
a
important
spot
in
the
software
development
lifecycle,
there's
certain
things
that
only
github
could
do
and
we
decided
we
needed
to
do
those
things
for
the
entire
software
development,
and
that
was
what
this
represented
got
to
take
advantage
of
the
data
that
we
have.
B
Developers
are,
as
I
mentioned,
some
of
the
most
sought
after
people
in
the
world
when
it
comes
to
talent
and
I.
Think
that,
with
the
influx
of
all
the
open
source
projects
in
the
world
and
all
in
companies
like
github
developer
tools
have
hit
a
curve
that
they
never
saw
before
and
I
think
that's
rather
remarkable,
and
it
goes
to
show
the
power
of
what
you
all
do
so
today.
Let's
talk
about
the
present
here
now
too,
let's
talk
about
what
you've
been
doing
this
past
year
and
where
we
are
today.
B
B
B
That's
pretty
remarkable
1.1
billion
and
of
note
you're
working
together
across
more
countries,
more
projects
to
basically
create
something
unquantifiable,
which
is
the
community
of
developers
or
dreamers
or
hackers
or
tinkerers
whatever
you
all
want
to
be
thought
of,
but
you're
working
together
on
these
things
this
year,
more
code,
more
issues
more
polar
quests
than
ever
before,
and
we,
as
I
mentioned
earlier,
we
passed
31
million
developers
on
github,
the
largest
connected
network
of
developers
in
the
history
of
the
planet,
8
million
new
developers
this
year.
This
is
up
from
6
million
in
2017.
B
B
Here's
a
fun
fact
we're
a
San
Francisco
company
that's
distributed
around
the
world.
However,
80%
of
all
access
of
github
comes
from
overseas.
That
to
me
shows
the
phenomenon
of
what
social
coding
is
all
about
all
around
the
world.
Everyone
is
working
together
on
code.
This
I
believe,
is
really
what
the
one
of
the
visions
for
the
founders
really
was,
regardless
of
boundary,
regardless
of
continent
or
even
timezone.
Work
on
your
code
together.
B
B
This
year.
Also,
you
merged
your
two
hundred
millionth
polar
quest
ever
we're
growing
at
about
40
percent
year-over-year
on
almost
all
of
our
statistics,
and
this
is
well
we're
growing
40
percent
year-over-year
on
how
many
pull
requests
were
merged
this
year
alone,
a
third
of
all
200
million
was
was
was
merged.
I,
like
this
statistic
alone,
because
it
shows
that
when
you're
using
pull
requests,
you're
working
together,
you're
having
conversation
around
the
code.
B
Changing
tact
a
little
bit,
what
about
the
future
of
software
development?
Who
are
your
co-workers,
gonna,
be
in
the
next
5-10
years?
1.1
million
students
have
learned
to
code
on
github
we're
continuing
to
make
sure
that
we
equipped
the
next
generation
of
software
developers
with
all
the
tools
that
they
need.
So
we
partner
with
folks
like
Heroku,
get
cracking
and
JetBrains
to
make
sure
that
the
best
tools
are
available
and
weave
in
that
includes
teachers.
B
There's
20,000
educators
around
the
world
using
github
for
free
via
our
education
idea,
have
education
program,
and
this
is
an
amazing
thing
too.
Just
to
give
away.
You
want
folks
to
have
access
to
the
best
tools
I
got
into
software
by
falling
into
it
and
I
remember
falling
into
the
open-source
ecosystem,
largely
because
I
couldn't
afford
anything.
That's
not
I
found
Linux
and
giving
software
away.
Is
it
a
great
enabler
for
people
to
actually
get
into
this
into
the
craft,
but
also
to
find
the
best
tools,
not
just
what
they
have
access
to.
B
Professionally,
we
have
two
point:
1
million
organizations
using
github.
This
is
across
all
public
and
private
repositories
and
includes
our
on-prem
installations,
as
well
as
our
business
hosted
and
cloud
stuff
and
we're
growing
at
about
40
percent
year-over-year
on
this
as
well,
more
organizations
more
professional
organizations
using
github
than
ever
before.
B
So
if
you
love
numbers
and
what's
behind
them,
come
see
that
it'll
be
fun,
so
I
hope,
you're
sensing
a
theme
here:
231
million
developers
around
the
world
using
github
you're,
all
doing
amazing
things
from
open-source
maintainer
x'
to
enterprises
and
everyone
in
between
the
theme
of
universe,
is
all
about
building
the
future
and
we've
taken
the
stroll
down
memory.
We've
seen
the
state
of
the
octave
versus
a
little
bit
and
we've
talked
about
some
of
the
current
state.
Let's
talk
about
future
state.
B
This
is
where
I
I
think
you're
all
here
to
seize
what
we're
releasing.
So,
let's
talk
about
the
future
and
there's
three
things
I
feel
like
I
can
definitively
say
about
the
future.
First,
no
one
can
actually
predict
the
future,
but
we
can
be
ready
for
it
and
that's
largely
our
jobs,
as
software
developers
is
to
be
adaptive
and
be
ready
for
the
future.
Second,
it's
going
to
involve
change.
That's
the
only
thing.
I
can
actually
tell
you
about
the
future,
but
that
change
is
both
going
to
be
good,
is
gonna,
be
hard.
B
There's
gonna,
be
things
about
that
and
my
annoy
us:
oh
there
will
be
changed,
let's
be
ready
for
it
and
third,
it
basically
involves
all
of
you,
but
it's
really
because
all
of
you,
because
of
what
you're
developing
today,
what
the
software
you're
gonna
be
releasing
tomorrow,
whatever
open
source,
you're
gonna,
be
doing
you're
gonna
be
literally
changing
the
future
and
speaking
of
big
changes,
it's
talked
about
a
couple
to
change
that
github.
So
let's
talk
about
one
you
might
have
heard
about
so
we're
getting
acquired.
B
Yeah
this
we're
pretty
excited
about
this
one,
a
github,
and
we
think
this
is
a
watershed
moment
for
developer,
oriented
companies
and
tools
around
the
world.
Ten
years
ago,
everyone's
trying
to
outsource
their
software
development
now
Microsoft's
buying
one
of
largest
developer
tools:
companies
in
the
world.
This
is
a
pretty
remarkable
decade
of
change
and
we've
been
fans
of
Microsoft
inside
github.
Now
too,
because
of
the
changes
they've
been
making
and
their
open
source
approach
and
how
they
approached
community
and
software
development
as
well.
Now
there
might
be
some
concerns,
but
our
developer.
B
First
ethos
are
distinctive
sphere
and
our
open
extensibility,
that's
not
going
anywhere,
that's
part
of
who
we
are
and
what
made
us
special
to
Microsoft
in
the
first
place,
and
while
we
don't
have
a
closed
date,
yet
we
do
anticipate
that
will
close
by
the
end
of
the
year.
As
many
of
you
know,
open-source
veteran
NAT
Friedman
is
going
to
be
our
CEO
once
that
does
closed,
and
that
is
here
today
somewhere,
it's
probably
in
the
audience,
raise
his
hand.
You
might
want
to
stay
anonymous.
Cuz
he'll
get
a
lot
of
bug,
requests
and
reports.
B
It's
all
the
software
think
about
the
phones,
the
cars,
the
devices
in
your
homes,
your
your
home
itself
is
powered
by
software.
Heck
I
have
a
pair
of
sneakers
that
has
software
in
it.
That's
okay,
yeah
yeah,
someone's
jams,
software
into
sneakers.
So
software
is
what
matters
and
you
all
are
the
ones
writing
the
software
and
we
get
hub
we're
focused
on
bringing
the
world
of
software
development
to
everybody,
and
we
want
to
bring
the
world's
best
experience
of
writing
software
to
everybody.
B
So
one
of
the
things
with
software
is
that
there's
still
too
many
challenges,
there's
too
much
wasted,
motion
and
entropy.
There's
just
there's
too
much
ceremony
in
software
too
many
config
files
in
too
many
trade-offs.
So
the
result
is
obviously
frustration
or
friction
fragmented
tools
and
services
lost
productivity
which,
if
you're
Evan
MBA.
What
you
would
say
is
the
worst
thing
in
the
world,
but
we
at
github.
We
think
about
your
lost
creativity
in
the
spark.
B
We
want
you
to
have
that
excitement
about
software
all
the
time
and,
if
you're
banging
your
keyboard
or
swearing
at
your
monitor,
because
the
tools
and
config
it's
it's,
it's
gonna
grate
on
you
every
day,
so
we
will
think
about
advancing
the
state
of
the
art
we
think
about
how
we
bring
software
to
its
next
level
and
we,
we
don't
think
about
mashing
together
a
whole
bunch
of
disks
or
disparate
or
discrete
technologies.
We
want
to
find
a
way
just
to
get
you
shipping.
We
don't
think
about
just
a
specific
aspect.
B
B
What
would
the
world
look
like
if
we
focused
on
the
developer
experience
for
every
developer
in
the
world,
all
31
million
of
you?
What,
if
software
development
workflows
we're
not
disjoint
what
if
they
all
work
together?
What
if
developers
didn't
have
to
build
every
single
connection
between
thousands
of
tools?
And
this
isn't
about
buzzwords,
or
this
isn't
about
again
mashing
together
technologies
to
make
them
work.
This
is
about
how
you
feel
when
you
experience
software
and
the
workflows.
B
B
Every
change
that
we
do
goes
out
to
one
individual,
we're
trying
to
make
your
life
better,
but
we're
31
million
people,
our
experience
you
go
as
well,
so
we
take
that
responsibility
incredibly
seriously,
but
it's
quite
invigorating.
There
is
moments
of
pause
when
we
want
to
release
something
saying
what
is
Twitter
gonna
say
about
this,
and
sometimes
we
do
roll
back.
Some
changes
that
weren't
well
liked,
but
what
we
really
want
to
do
is
give
you
all
that
same
experience.
We
want
to
do
something.
B
That's
fundamentally
different,
so
today
we're
proud
to
introduce
a
couple
of
new
features
and
products
to
get
help
so
features
that
unify
the
developer.
Experience
features
that
are
for
offer
a
smarter
or
more
interconnected
workflow
and
it's
all
powered
by
code.
So
you're
gonna
hear
from
a
lot
of
folks
around
github
today,
they're
talking
about
collaboration,
they're
gonna,
talk
about
the
business
aspects,
they're
gonna
talk
about
security
and
they're,
going
to
talk
about
the
core
underlying
platform
as
well,
so
to
kick
that
off.
B
C
Thank
you
so
much
Jason
today,
31
million
developers
choose
github
for
where
their
software
development
happens
and
over
8
million
new
accounts
were
added
in
the
last
year
alone,
and
this
is
really
strengthening
our
commitment
to
developers
and
earns
us
our
position
as
the
home
for
developers
and
as
developers.
We
want
to
solve
problems,
share
knowledge
and
together
change.
C
The
world
around
us
and
the
open
source
community
on
github
continues
to
be
the
best
place
to
do
it
all
we're
focusing
on
solving
problems
for
developers
for
those
who
work
with
developers
and
those
who
build
for
developers.
So
when
you're
in
your
groove,
we
want
to
keep
you
there,
we
want
to
remove
any
barriers,
blockers
and
bottlenecks
for
you
and
your
team,
because
we
know
that
there's
simply
too
much
effort
required
to
write
code
share
code
and
review
code,
so
we're
making
a
commitment
to
you.
C
Our
commitment
is
to
never
give
up
on
improving
our
product
and
our
platform.
Our
commitment
is
to
better
serve
you
and
the
developer
community
now
I
know
each
of
us
have
those
small
blockers
or
pain
points
that
take
us
out
of
our
rhythm
throughout
the
day.
Now
imagine
that
pain
point,
but
for
31
million
developers
who
might
share
that
same
frustration.
That
is
a
lot
of
lost
productivity,
effort,
time,
energy
and
money
that
could
otherwise
be
spent,
keeping
you
in
your
workflow.
C
So
that's
why
this
past
year
we've
been
hard
at
work,
keeping
you
as
productive
and
focused
as
possible.
We
have
shipped
hundreds
of
iterative
improvements
to
our
product
and
our
platform,
and
some
of
my
favorites
are
on
this
list
like
ignoring
the
plus
and
minus
markers.
When
you
select
a
diff
line,
that's
a
good
one
or
resolving
a
conversation
on
a
pull
request
and
we
are
constantly
improving
our
product
cuz.
C
We
want
to
better
serve
all
of
you
and
we're
gonna
keep
doing
it
because
we
know
that
you
do
your
best
work
when
you
don't
have
to
deal
with
all
of
these
issues
and
that's
why
today
is
no
different.
It's
just
another
Tuesday
here
at
github
shipping,
the
stuff
you
love!
So
I
want
to
introduce
you
to
suggested
changes.
What
suggested
changes?
It's
just
the
latest
improvement
to
our
github
PR
workflow,
and
it
means
that
authors
don't
need
to
copy
and
paste
their
code
suggestions
from
reviewers
and
your
reviewers.
C
You
no
longer
have
to
branch
and
make
a
commit.
You
can
actually
just
add
a
suggested
change
and
the
the
author
can
accept
it
with
a
single
click
and
that's
it
so
I
want
to
show
this
to
you
in
action
here,
Kyle
Daigle,
who
will
be
on
stage
later
today.
He
opened
up
a
pull
request
and
he
wants
me
to
review
it.
He's
added
a
method
and
I
think
he's
being
a
little
too
clever.
I,
don't
know
if
this
is
gonna
scale,
so
I
want
I'm.
C
Gonna
suggest
you
add
a
randomizer
because
it'll
be
easier
to
maintain
I'm
gonna
select
the
line.
I
give
him
a
little
bit
of
information
about
what
I'm
thinking
and
then,
instead
of
typing
out
all
my
code
and
markdown
I
can
actually
just
click
this
button
and
it
inserts
my
the
code
into
my
comment
and
then
I
can
make
my
suggestion
and
then
after
I
do
this.
Let's
actually
check
this
out
and
see
what
it
looks
like
for
Kyle.
C
So
he
can
clearly
see
the
different
and
my
suggestion,
and
this
gives
him
all
the
confidence
he
needs
to
know
that
I
was
right
and
he
can
accept
this.
So
what
I
love
about
this
is
that
it
removes
a
lot
of
the
back-and-forth
during
the
pull
request
review
and
we
can
actually
stay
more
productive
together.
C
Now
github
is
largely
synonymous
with
open
source,
but
did
you
know
that
thousands
of
companies
use
github,
Enterprise
and
github
business
cloud
and
that's
in
addition
to
the
two
point,
1
million
organizations
that
are
using
github
to
collaborate
as
teams
of
developers,
but
every
developer,
regardless
of
where
you
work,
deserves
the
best
developer.
Experience
possible
the
code
that
you're
writing
at
your
job
with
your
teammates.
That
code
is
just
as
important
as
the
code
that
you're
writing
an
open
source
with
maintainer,
z'
and
workflows
and
open
source
are
becoming
increasingly
more
present
in
business
setting.
C
But
these
environments
still
have
their
unique
needs.
You
still
have
to
learn,
get
and
github,
and
you
still
have
to
learn
you're
in
Toyland
your
employers,
tools
and
processes,
and
this
all
takes
time
and
energy
and
that's
time
and
energy
that
sometimes
your
businesses
don't
have.
So
that's
why,
earlier
this
year,
we
shipped
Learning
Lab.
C
So
if
you
want
to
learn
more
about
how
to
get
up
and
running
with
the
Learning
Lab
programs,
I
encourage
you
to
go
to
lab
github,
comm,
slash
organizations,
so
businesses
and
enterprises
leverage
github
in
two
ways:
either
on-premises
with
github
enterprise
or
with
github
business
cloud
on
github.com
and
as
businesses
grow,
so
do
their
teams,
and
this
means
that
so
do
the
challenges
they
face.
But
what's
valuable
to
these
organizations
is
that
they're
actually
able
to
tap
into
the
knowledge
of
31
million
developers,
96
million
repositories
in
over
five
hundred
terabytes
of
data?
C
However,
companies
using
github
Enterprise
hosted
on
their
own
servers
are
siloed
from
that
data
and
those
communities
and
some
companies
have
multiple
organizations
which
makes
identity
management
of
their
developers
very
difficult.
So
what
we
want
to
do
is
bring
on-premises
closer
to
where
the
innovation
happens
in
the
cloud
we
want
to
unify
this
experience
for
developers,
regardless
or
wherever
that
wherever
these
developers
are
across
organizations
regardless
of
deployment
type
and
that's
why
we're
shipping
github
connect,
get
up,
connect,
breaks
down
silos
across
organizations?
C
It
gives
developers
access
to
data
and
communities
regardless
of
whether
they're
running
in
Gog
or
they're
running
with
github
business
cloud,
and
it
does
this
all
while
ensuring
that
developers
remain
productive,
engaged
and
connected
to
the
larger
world
of
github
calm.
So
ghetto
Connect
addresses
three
common
pain
points
that
we
have
heard
from
developers
and
organizations.
C
First
developers
need
access
to
private
code
beyond
the
firewall.
Second,
those
developers
who
are
coding
behind
the
firewall
they
can't
get.
They
can't
showcase
their
commits
on
their
public,
github,
calm
profile
and
third,
as
developer
teams
scale.
So
do
the
needs
of
their
administrative
tasks.
So,
let's
dive
into
some
of
these
and
how
github
connects
all
of
them,
so
developers
on
github
Enterprise.
C
Now,
companies
maintain
different
organizations
in
order
to
scale
the
development
teams,
efforts
and-
and
they
do
this
also
to
keep
their
teams
moving
fast.
But
this
creates
a
lot
of
administrative
overhead
so,
with
the
unified
business
identity,
administrators
can
unify
multiple
organizations
in
a
single
account
and
this
is
going
to
help
them
improve
billing,
improve
licensing
and
permissions
and
policies.
So
for
administrators,
wherever
you
see
an
org
setting
today,
you're
also
going
to
see
a
business
identity
setting.
C
One
company
and
I'm
super
excited
to
tell
you
that
this
is
all
available
today
with
the
enterprise
215
release
that
come,
that
is
available
now
you're
going
to
find
unified,
search,
enhancements
and
unified
contributions
and
we're
also
releasing
the
unified
business
identity
in
a
limited
public
beta.
So
if
you'd,
like
access
to
that
program,
I
encourage
you
to
talk
to
your
account
representative
now
as
developers,
we
know
that
we're
doing
our
best
work
when
we're
also
doing
our
most
secure
work
and
as
github.
C
We
have
a
responsibility
to
enable
this
level
of
security
and
that's
why
we've
been
hard
at
work
this
past
year,
helping
developers
prevent
the
next
security
breach,
and
these
threats
can
come
in
all
forms.
They
can
be
leaked
information,
use
of
malicious
code
or
malicious
attackers,
and
developers
and
orgs
have
to
fight
these
threats
in
their
projects
and
their
businesses,
and
it
can
be
challenging
to
stay
vigilant
and
up-to-date
on
what
the
latest
new
security
alert
is
and
the
risks
are
significant.
C
They
can
mean
substantial
financial
liability,
declines
in
trust
and
loyalty,
or
even
test
the
ability
for
your
business
survive
in
2017
over
1,500
significant
data
breaches
affected
cause
major
distress.
Re
excuse
me
cause
major
disruptions
to
businesses,
government
organizations
and
the
lives
of
everyday
people,
and,
as
organizations
continue
to
invest
in
innovation,
you
have
to
realize
that
you're
doing
so
in
an
increasingly
hostile
and
risky
world.
But
what
you
don't
realize
is
that
these
security
challenges-
these
are
not
just
challenges
for
individual
CISOs
or
IT
administrators
or
maintainer
x'.
C
This
is
a
community
challenge
and
at
github
it
is
our
responsibility
to
protect
our
users
and
our
community
from
these
from
these
threats,
and
so
with
the
data
and
the
power
of
the
network
that
github
maintains
as
the
most
popular
software
development
platform
in
the
world.
We
can't
help
but
see
the
opportunity
in
front
of
us
to
enhance
security
across
the
entire
software
development
ecosystem
through
the
detection
of
or
through
the
automation
of
detection,
remediation
and
tracking
security
vulnerabilities.
We
believe
that
we
can
be
of
service
in
the
name
of
public
good,
enhancing
security.
C
For
all
that's
why,
last
year
we
released
security,
vulnerability
alerts
for
JavaScript
and
Ruby
and
why
we're
extent
we
extended
that
functionality
to
Python
later
that
summer,
but
earlier
this
summer
we
have
to
take
a
community
approach
and
a
platform
approach
to
security.
Otherwise
we
all
fail
and
it's
working.
Since
we
shipped
last
year,
we
have
sent
over
5
million
alerts
to
github
users,
so
today
we're
very
happy
to
be
shipping
security,
vulnerability
alerts
for
two
new
languages,
Java
and.net.
C
And
this
is
all
powered
by
the
github
dependency
graph,
which
Maps
how
a
developer's
repository
depends
on
other
repositories
and
projects
across
all
of
github.
So
for
all
five
of
these
languages,
we've
redesigned
the
developer,
the
dependency
graph
and
the
vulnerability
pages.
So
when
you
get
one
of
these
vulnerabilities,
you
can
click
into
it
and
you
can
get
more
information
about
remediation
and
you
can
confidently
take
next
steps
now.
C
We
really
want
to
ensure
that
tokens
and
keys
never
accidentally
get
aget
committed
and
exposed
publicly,
and
so
that's
why
we
scan
repositories
and
we
search
for
known
token
formats
and
if
one
is
found,
we
contact
the
provider
they'll
validate
it,
contact
the
owner
and
then
issue
a
new
token
and
we're
doing
this
all
automatically
so
that
we
can
keep
your
tokens
from
getting
into
public
repositories
and
potentially
into
the
wrong
hands.
And
finally,
we
wouldn't
be
the
platform
that
we
are
today
if
we
didn't
take
a
holistic
view
of
security
across
all
of
github.
C
So
as
that
software
development
platform
of
choice
for
31
million
developers
were
the
only
ones
who
can
collect
and
share
information
about
security
across
millions
of
projects
and
we're
taking
a
developer.
First
approach:
we're
allowing
you
to
consume
security
vulnerabilities
at
scale
with
the
security
vizor
e
api
to
power.
Github
security
features
we're
using
existing
processes
to
aggregate
and
validate
security
advisories,
and
we
decided
to
make
this
available
publicly
to
all
of
you
free
of
charge
for
the
community.
C
So
when
you
interface
with
this
API
you'll
have
access
to
all
the
vulnerabilities
that
we
have
detected
starting
today.
All
of
this
data
is
at
your
fingertips.
It's
ready
to
be
integrated
into
the
tools
and
services
that
you
already
use
so,
for
example,
if
you're
responsible
for
compliance
at
your
company,
you
can
track
these.
These
vulnerabilities
programmatically
at
scale
across
your
code
in
your
projects,
and
you
can
create
your
own
advisories.
C
So
we
just
talked
about
a
developer
first
workflow
and
how
we're
empowering
individual
developers
and
teams
of
developers
to
learn
together,
how
we're
bridging
the
gap
between
enterprise
and
open-source
and
how
we
are
making
security,
a
platform
level
service,
and
it
all
happens
on
github,
which
is
the
only
place
you
can
so
to
tell
you
more
about
the
power
and
the
future
of
the
github
platform.
I
would
love
to
welcome
to
the
stage
github
head
of
platform,
Sam
Lambert.
D
D
D
More
than
12
million
developers
are
now
using
an
integration
on
github,
and
this
one
really
surprises
me.
Our
data
shows
us
the
developers
in
organizations
that
have
an
integration
contribute
twice
as
much
as
developers
the
dome.
It
takes
a
lot
of
infrastructure
to
host
the
home
of
open
source
github.com
and
the
services
that
operate
it
run
on
over
40,000
CPU
cores,
and
we
have
more
than
5.4
petabytes
of
storage,
supporting
your
code
and
collaboration
on
github
comm.
D
When
the
world's
code
is
building
and
deploying
from
one
place,
it
generates
a
lot
of
traffic.
Our
network
edge
serves
over
a
hundred
gigabits
per
second
a
daily
peak
at
github.
We
say
it
isn't
shipped
until
it's
fast.
We
continue
to
bring
you
fast
access
to
the
to
github
by
deploying
points
of
presence
in
Europe
and
Asia.
Now,
when
you
clone
your
repository,
you'll
have
lower
latency
and
higher
throughput.
D
We
know
more
about
the
connections
between
code
than
ever
before
how
code
is
shared
across
our
ecosystem
and
how
repositories
depend
on
each
other,
we're
at
the
beginning
of
a
journey
bringing
AI
and
machine
learning
into
our
network
and
thus
the
world
of
software
development.
I
would
like
to
welcome
emoji
Miller
senior
data
scientist
from
our
machine
learning
group
to
share
where
our
platform
will
take
us
in
the
future.
E
E
E
It's
not
necessarily
about
the
code
that
we
write
or
the
typing
or
the
compilers
it's
about
the
products
we
build
and
the
effect
that
it
has
on
people.
People
like
my
friend,
Tiffany
Ashley,
Bell
Tiffany,
is
a
developer
and
a
couple
of
years
ago
she
was
on
social
media,
where
she
learned
that
the
city
of
Detroit
was
gonna
turn
the
water
supply
off
for
a
few
of
its
citizens,
because
they
couldn't
pay
their
water
bills
as
a
developer.
She
was
deeply
moved
by
this
and
she
decided
that
she
could
do
something
about
it.
E
She
reached
out
to
a
couple
of
people,
some
of
whom
she'd
never
ever
met
before,
and
they
decided
to
build
an
app.
What
would
later
become
the
human
utility
project?
A
non-profit
civically
minded
nonprofit,
designed
specifically
to
crowdsource
collaboration
and
give
money
to
people,
so
they
could
pay
their
water
bills.
In
the
early
days
of
github.
There
were
three
major
things
that
we
were
really
interested
in.
We
wanted
to
make
sure
that
we
were
a
developer
first
comfort
of
developer
first
company.
E
We
wanted
to
reduce
the
friction
in
the
workflows
of
those
developers
and
we
wanted
to
work
to
lower
the
barrier
to
entry
into
software
development.
Nine
years
of
having
all
these
kinds
of
data,
we
decided
we're
gonna
form
the
machine
learning
team.
Last
year,
the
machine
learning
team
used
our
follows
data
and
build
the
discovery
dashboard.
The
discovery
dashboard
allows
you
to
discover
our
open
source
repositories
that
might
be
interesting
to
you:
open
source
repositories
like
faster
AI,
a
project
specifically
designed
to
make
deep
learning
accessible
to
everybody.
E
Since
then,
we've
spent
the
year
balancing
the
tension
between
iteratively
shipping
products
to
you
that
are
data
enabled,
as
well
as
doing
fundamental
research.
That
lets
us
understand
what
is
possible.
We've
shifted
our
focus
on
focus
in
our
languages.
We
focus
in
on
understanding
human
languages
like
English
Spanish,
my
local
language
yoruba,
as
well
as
programming
languages,
programming
languages
like
Java,
Ruby
and
Python,
one
of
the
most
interesting
things
about
doing
machine
learning.
I
github
is
often
we
use
github
to
do
machine
learning
at
github.
Something
like
the
discovery.
E
Dashboard
shows
us
all
kinds
of
interest
in
open-source
projects
around
ml
that
we
might
want
to
explore.
Few
weeks
ago
we
launched
experiments.
Experiments
is
a
window
into
our
Applied
Research
and
the
reason
why
we
did
this
is
because
we
have
a
lot
of
things
that
we're
working
on
that
are
not
quite
production.
Ready,
but
we
wanted
to
share
it
with
the
world.
We
want
to
make
sure
that
we
continue
building
in
an
open-source
fashion.
We
want
to
have
that
constant
conversation
with
you.
E
That's
why
we
shipped
experiments
when
we
think
about
how
we
write
code
today,
we
think
about
writing
code
in
an
imperative
fashion.
There
is
something
that
I
do
all
the
time.
There's
a
function
I
find
myself
writing
over
and
over
and
over
again,
it's
called
fatten
a
list
of
Lists
as
an
ml
person.
I
have
to
do
this
and
whenever
I
want
to
flatten
a
list
of
list,
I
ended
up
thinking
about
all
the
things
I
have
to
do.
Okay,
I
have
to
define
the
function,
I
have
to
count
the
list
and
append
them
together.
E
Maybe
I
use
a
list
comprehension.
You
understand
what
I'm
saying
I
have
to
go
through
this
entire
thing
in
my
head
and
actually
write
out
the
code
in
the
future,
with
machine
learning
with
the
kind
of
data
we
have.
We
don't
have
to
do
that
anymore.
If
I
want
to
flatten
a
list
of
lists,
I
can
do
declarative
reasoning.
I
can
actually
just
say,
flattened
list
of
Lists
type.
It
and
I
should
be
able
to
get
a
bunch
of
functions
that
achieves
that
goal.
True
semantic
search
that
is
going
from
intent,
natural
language
to
code.
E
E
Semantic
code
search
is
one
of
those
capabilities
we're
bringing
to
the
platform
I
want
you
to
think
about
not
me,
but
yourself,
think
about
where
you
are
on
this
data
universe,
with
the
capabilities
that
the
machine
learning
team
is
going
to
be
bringing
to
the
platform.
I
want
you
to
imagine
the
kinds
of
things
you
will
build.
I
look
forward
to
hearing
about
this.
Thank
you.
D
Emoji,
thank
you.
The
scale
of
our
network
is
truly
or
inspiring,
and
that's
why
we're
here
from
day
one
github
has
been
a
company
committed
to
openness
and
the
belief
that
open
platforms
drive
increased
innovation,
which
in
turn
creates
choice
and
opportunity
for
developers.
We
are
the
center
of
software
development.
We
make
it
our
mission
to
evolve
our
platform,
so
that
is
accessible
for
all
developers,
regardless,
though,
of
the
choice
of
tools,
languages
or
framework.
As
a
result
of
this
commitment,
31
million
developers
have
been
given
so
much
choice.
D
For
years,
we've
seen
companies
solely
built
on
our
platform
to
serve
our
users
with
solutions
that
extend
the
functionality
of
github,
but
developers
still
spend
too
much
time
today
and
wasting
energy
configuring
workflows.
They
are
also
stuck
with
inflexible
architectural
choices
as
new
tools
and
innovative
software
practices
emerge.
We've
set
out
to
fix
that
with
something
brand
new
and
I
am
so
excited
for
this.
As
a
software
developer,
your
workflow
is
your
working
life.
D
We
want
to
bring
the
power
of
open
source
and
our
network
into
your
workflows.
The
core
of
github
is
code,
so
we
knew
we
had
to
create
a
way
to
build
workflows
with
code.
Today
we
bring
you
something
truly
much
remarkable
for
the
past
year.
That
has
been
our
goal:
to
simplify
the
process
of
automation,
with
an
approachable
standard
framework
living
within
a
github
repository.
We
want
developers
to
have
infinite
choice
and
customization
potential.
D
Our
job
is
to
delight
you,
our
users.
Your
job
is
to
delight
your
users
by
enabling
workflows
as
code
executed
and
hosted
on
github,
calm
and
supported
by
an
expanding
ecosystem
of
you
created
functionality.
We
believe
we
will
once
again
revolutionize
software
development,
together
with
you,
one
global
community
of
software,
to
get
developers
to
realize
this
vision.
Today,
we
are
announcing
github
actions.
D
Now
you
can
build
share
and
execute
actions
inside
containers
right
on
github
all
within
a
few
simple
steps.
I
truly
believe
this
is
our
bigger
ship,
since
the
pull
request,
no
words
can
do
this
justice,
so
let
me
introduce
you,
Kyle
Daigle,
director
of
ecosystem
engineering,
to
show
you
the
power
of
github
actions.
F
Thank
you,
Sam
I'm,
so
excited
to
show
you
github
actions.
Today,
over
the
past
year,
while
we've
been
building
it
I've
been
using
the
feature
with
the
team
and
I
really
think
it's
going
to
change
your
developer,
workflows
with
github
actions.
We've
created
a
way
for
you
to
build,
connect,
execute
and
share
code
containers
to
run
your
software
development
workflow.
You
can
use
any
language
to
build
an
action.
F
You
can
find
an
action
that
someone
else
has
already
written
and
use
that
and
you
can
represent
your
entire
workflow
as
code,
but
the
best
way
to
help
you
understand,
what's
possible
with
github
actions,
is
to
show
you
so
I've
come
up
with
a
few
examples.
My
first
example
I've
created
a
node
module
to
help
celebrate
github
universe.
It's
pretty
simple,
but
I
want
to
make
it
easy
to
publish
it
to
NPM
as
I
make
tweaks
now.
F
Normally,
with
this
I'd
have
a
set
of
scripts
and
incantations
I'd
have
to
run
on
my
local
computer
and
share
with
all
my
contributors,
but
with
github
actions.
We
can
automate
this
entire
workflow.
Let
me
show
you
what
that
looks
like
this:
is
my
very
small
node
module.
It
has
a
few
functions
that
print
out
various
celebrations
about
github
universe
to
start
using
github
actions,
I
create
a
main
dot
workflow
file
inside
of
the
dot
github
directory.
Now,
instead
of
editing,
this
manually
I
want
to
show
you
our
visual
editor.
F
This
is
a
github
actions
workflow.
It
starts
with
two
things,
a
name
and
when
the
workflow
should
run
for
the
name,
I'll
go
with
test
and
publish
to
NPM
and
then
for
running.
I
want
to
run
this
workflow
each
time.
I
push
up
a
tag.
I
know
this
is
the
push
event
so
I'm
going
to
choose
that
we
support
dozens
of
different
events
to
start
a
workflow
with
each
of
these
events
will
add
the
payload
data
into
the
action
you
can
use
that
payload
to
make
decisions
and
we
use
it
to
power.
F
A
couple
of
cool
gate
of
actions
features,
but
I'll
show
that
to
you
later,
ok,
once
I've
set
up
the
workflow
trigger
I
choose
my
first
action
in
the
sidebar.
There's
a
list
of
open
source
actions.
I
can
choose
each
action
here
is
either
an
open
source
repository
an
action,
that's
private
inside
my
repository
or
an
action
in
a
docker
registry.
Each
action
does
particular
thing
and
they
can
be
used
in
different
ways.
F
So
I
only
want
to
publish
to
NPM
when
I
tagged
a
release,
so
I'm
going
to
choose
the
filter
action
that
Brandon
Keepers,
one
of
our
developers
built
it
lets
me,
stop
a
workflow.
If
a
particular
detail
in
the
payload
isn't
a
match.
We
only
want
to
process
push
events
if
they
have
a
tag,
so
we'll
add
a
filter
and
then
add
the
tag
command
here
to
ensure
that
we
stopped
the
we
stopped
the
flow
if
there
is
not
a
tag
in
the
push
and
then
I'll
save
my
first
action
now.
F
I
know
that
I
have
a
tag.
I
need
to
run
my
tests
to
ensure
I'm
not
releasing
a
bad
build.
Every
action
has
a
copy
of
the
repository
inside.
That
action
makes
it
really
easy
to
run
tests
or
take
other
actions
on
your
code.
I'll
choose
the
npm
action,
give
it
a
name
and
then
I'll
give
it
the
test
argument
which
will
be
passed
into
the
container,
to
tell
it
to
run
that
particular
command
and
I'll
save
this
action
to
okay.
F
Once
my
tests
pass,
I
actually
need
to
publish
this
module
to
NPM,
so
I'll
drag
down
in
the
visual
editor
to
create
another
action
with
this
action,
I
need
it
to
publish
so
I'll
choose
NPM
again,
give
it
a
name
and
then
I'll
add
the
publish
argument,
but
in
order
to
publish
I
need
to
authenticate
with
NPM,
but
we
think
we've
solved
that.
Let
me
introduce
you
to
the
github
secrets.
Vault
with
the
secrets
vault,
you
can
store
credentials
that
you
need
as
part
of
an
action
when
you
put
it
into
the
UI.
F
We
encrypt
it
using
a
live
sodium,
sealed
box
inside
the
browser.
Then
we
push
that
encrypted
secret
to
our
servers.
Where
we
store
it
encrypted,
then
you
can
tell
us
which
secret
you're,
using
in
each
action
we'll
handle
things
like
API
tokens
certificates,
passwords,
sensitive
information,
keeping
it
secure
in
transit
until
your
action
needs
it.
Okay.
So
let
me
go
back
to
my
demo.
All
I
need
to
do
now
is
add
my
NPM
authentication
token
into
the
secrets.
F
Vault
I'll,
give
the
token
a
name
and
then
I'll
simply
paste
in
my
NPM
authentication
token
you'll
notice
that
the
check
box
here
turns
blue,
which
says
that
this
action
is
to
use
this
secret
and
that's
it.
I
have
a
complete
workflow
to
kick
this
off.
All
I
have
to
do
is
push
up
a
tag
to
github
by
tagging.
The
release
locally
and
pushing
it
now.
I
want
to
show
you
the
next
piece,
which
is
the
actions
tab.
F
F
But
giddup
actions
isn't
just
for
testing
and
publishing
code.
We
also
give
you
the
full
power
of
github
apps
by
providing
you
with
an
API
token,
in
your
action
that
you
can
use
to
query
github
API
if
you've
ever
wished.
I
know
how
I
have
to
do
an
automatic
action
like
delete.
A
branch
put
an
issue
close
an
issue
merge
a
pull
request.
Now
you
can
do
that
automatically
using
github
actions.
Let
me
show
you
how
myself
a
new
open-source
maintainer
can
automate
a
few
best
practices
of
open
source
projects
using
github
actions?
F
Ok,
so
this
is
the
first
workflow
that
I've
built
for
this.
One
I
want
to
send
a
welcome
message,
the
first
time
contributors
when
they
create
a
new
issue
on
a
project
for
the
first
time.
First,
we'll
look
for
the
issue
event,
then
we'll
filter
for
only
issues
that
have
been
opened
down.
One
more
step.
We
look
at
the
payload
like
I
mentioned
earlier,
to
see
that
the
author
of
this
issue
is
the
first
time
contributor.
F
In
this
example,
we
decided
to
use
a
command
line
tool
JQ
to
look
at
the
payload,
and
then
we
can
post
the
welcome
message
to
the
user
by
using
a
new
tool
that
we've
built
called
ghx
I'm
really
excited
about
this.
So
let
me
show
you
what
it
looks
like
with
ghx
we've
made
the
easiest
way
for
you
to
interact
with
key
parts
of
github
API
like
issues,
comments,
check,
statuses
and
more.
It
doesn't
really
work
like
curling
or
using
hub,
because
with
github
actions
we
have
the
context
and
the
environment.
F
So
you
don't
need
to
tell
us
the
API
token
or
what
issue
that
you
want
to
comment
on.
We
know
because
we
have
that
payload
data
inside
the
action
we
can
infer.
All
that-
and
all
you
need
to
do
is
push
the
data
that
you
want
to
put
into
the
comment
in
this
case
a
welcome
dot,
MD
file,
we'll
run
this
command
and
boom.
We
have
a
comment
now.
F
Ok,
so
we've
set
up
this
workflow
to
post
a
welcome
message
on
the
first
issue
of
a
new
contributor.
Let
me
show
you
what
this
looks
like
in
action
here.
Brandon
a
contributor
commented
on
my
project
and
we've
sent
a
very
nice
welcome
message
with
some
kids
linked
to
Guidelines
all
automatically,
but
I
want
to
take
this
a
step
further.
Let
me
show
you
a
workflow
that
will
help
triage
issues
and
reduce
duplicate
issues.
First
again,
we
take
the
issues
event.
F
We
ensure
we're
dealing
only
with
opened
issues
and
then
I
use
an
action
that
I've
put
privately
inside
my
repository
to
add
a
triage
label
on
to
the
issue.
Finally,
we'll
use
a
pro
bot
application
to
detect
and
provide
duplicate
issues.
If
you
haven't
heard
of
Probot,
the
pro
bot
project
is
an
easy
tool
to
build
bots
that
respond
to
events
on
github.
A
few
weeks
ago,
we
worked
with
the
maintainer
zip
robot
to
make
Probot
apps
compatible
with
github
actions.
So
there
are
pro
bot
apps
the
track.
F
Work-In-Progress
handle
duze,
closed
sale,
issues,
set,
reminders
and
many
more.
There
are
hundreds
of
these
bot
applications,
and
now
they
can
work
with
github
actions.
So
we
it's
really
exciting.
We
set
up
our
issue
triage
and
duplicate
issue,
Probot
all
automatically
running
in
github
actions.
Now,
let's
show
you
what
it
looks
like
in
action.
An
issue
comes
in,
we
label
it
with
the
triage
label
and
then
the
pro
bot
app
runs
finds
the
duplicate
issues.
In
my
repository
and
post
it
to
the
issue.
F
Now
I
think
github
actions
is
an
amazing
way
to
deploy
your
application
as
well,
regardless
of
what
cloud
provider
you
use
or
service,
you
can
use
open
source
actions
to
build
and
deploy
your
application
in
a
few
simple
steps.
For
this
example,
I
built
an
optical
generator,
app
and
I'd
like
to
deploy
it
using
Zeit
site,
helps
power
global
service
deployments.
F
They
make
it
tremendously
easy
to
take
a
node.js
application
or
a
docker
container
and
deploy
it
globally
in
a
few
simple
steps,
that's
perfect
for
what
I
need
to
do
so
I'm
going
to
use
site
in
my
github
actions,
workflow
first
we'll
build
the
docker
image
using
the
docker
command
line
tool.
Then
we'll
filter
pushes
to
only
deploy
it's
from
the
master
branch,
we'll
use
sites,
github
action
to
deploy
site,
giving
the
token
that
we've
already
stored
and
then
finally
we'll
give
our
new
deployment
the
URL.
F
We
want
it
to
have
using
sites
alias
command
and
that's
it.
Now
we
have
a
complete
continuous
deployment
workflow,
where
I'll
deploy
to
Zeit
every
time
the
master
branch
gets
new
commits.
So
I
want
to
show
you
what
this
application
looks
like
deploy
to
site,
but
deploying
to
a
single
service
is
a
little
too
obvious.
Why
would
I
not
deploy
both
to
site
in,
say
another
service
like
Heroku
as
well?
Let's
do
a
parallel
deployment
to
both
site
in
Heroku.
F
At
the
same
time,
with
both
of
these
deployed
we'll
be
able
to
get
deployed
URLs
for
each
service
at
the
end
of
the
workflow.
Now
this
works
because
with
github
actions,
you
can
actually
run
any
action
in
parallel,
because
actions
are
built.
As
a
resolution
tree,
you
define
what
each
action
relies
upon
up
the
stack,
and
that
includes
allowing
parallel
actions,
will
stop
you
from
creating
circular
dependencies,
but
will
support
anything
that
we
can
deterministically
execute
up
until
this
point,
I've
shown
you
the
visual
editor,
but
you
can
also
edit
the
workflow
completely
in
text.
F
In
this
example,
you'll
see
I
have
the
workflow
name.
My
workflow
will
trigger
this
every
time
the
on
event
happens
and
we
resolve
actions.
2
&
3
that
rely
on
different
actions.
You'll
see
also
that
one
ample
is
an
open
source
repository.
The
second
example
is
a
docker
registry.
The
third
example
is
a
private
action
inside
my
repository.
So
if
the
visual
editor
isn't
your
style,
you
can
use
your
code
editor
of
choice,
okay,
so
when
a
push
comes
into,
master
will
deploy
to
both
site
in
Heroku
in
parallel.
F
F
Will
run
each
unique
step
for
each
cloud,
so
we're
not
forcing
you
into
an
abstraction
that
you
don't
like
and
we'll
end
up
with
a
deployment
URL
for
each
and
every
environment.
Now
let
me
show
you
what
this
looks
like
sped
up
a
bit.
We
kick
off
all
of
these
deployments.
At
the
same
time,
simply
by
pushing
code
to
master
and
get
up,
actions
will
deploy
to
all
five
of
these
cloud
providers.
This
flow
is
using
parallel
actions,
secrets,
environment
variables,
open
source
actions
and
the
new
deployments
UI
all
working
together
to
deploy
the
site.
F
We've
built
a
variety
of
github
actions
to
work
with
tools
like
GCP
AWS
site
asher
are
filtering
action
ghx
and
many
more
alongside
the
supported,
Probot
applications.
We
have
four
hundred
and
fifty
available
actions
during
beta
tomorrow.
We'll
share
some
more
stories
and
examples
when
we
gave
members
of
our
community
early
access
to
get
up
actions
and
you
can
see
what
they've
built
with
it.
Okay,
let's
recap:
git
up
actions
is
about
giving
developers
the
same
power
they
have,
while
writing
software
to
the
act
of
publishing
that
software
for
an
individual
developer.
F
That
might
mean
automating
some
common
tasks
that
you
do
each
day,
if
you're
a
startup
or
a
business
using
github
actions,
you
can
seamlessly
connect.
All
of
the
tools
that
you're
using
or
create
actions
of
your
own
as
an
enterprise,
you
can
roll
out
lifecycle
processes
that
are
repeatable,
audible,
compliant
using
the
business
cloud
environment
just
by
updating
your
workflow
files
and
as
a
partner
in
our
ecosystem.
You
have
a
new
way
to
connect
with
our
users
and
offload
the
processing
of
tasks
if
you've
been
waiting
to
build
a
developer
tool.
F
B
Thank
You
Kyle,
I'm,
ojou-sama
and
Kathy,
so
anyone
have
a
favorite
that
they
saw
today.
The
actions
team
is
over
here
so
yeah
supposed
to
pick
favorites
when
you
have
children
and
products,
but
I
think
today
is
at
least
my
favorite
universe.
I've
been
to
this
is
a
good
one.
So
these
ships,
together
in
aggregate,
represent
some
of
the
most
significant
updates
we've
had
to
the
entire
github
platform,
since
the
pull
request
and
I
hope
that
you
all
see
that
and
have
some
fun
with
it.
B
We're
really
excited
to
see
what
you
do
with
this
actions.
Also,
though,
when
we
think
about
this
is
really
about
your
workflows,
your
day-to-day
jobs,
everything
that
you
do
when
you
wake
up
in
the
morning,
we
talk
about
github
as
the
first
half
open
last
tab
closed
for
developers.
We
want
you
to.
We
want
this
to
be
your
home,
so
whether
that
be
CI
CD,
integrating
with
partners
or
deploying
to
any
of
the
major
cloud
services
actions
is
for
you.
We
want
to
see
what
you
can
do
with
it.
Things
that
were
not
possible.
B
Just
yesterday
are
going
to
be
possible
tomorrow
with
all
the
software
that
were
writing
together.
Actions
is
the
quintessential
collaborative
community
effort.
We
have
this
amazing
platform,
but
it's
not
going
to
become
what
it
could
be
unless
you
all
out
there
put
some
of
the
open-source
actions
together.
We
want
to
see
what
you
are
going
to
do
with
this.
This
is
gonna,
be
amazing,
so
we
do
it
because
of
you.
We
do
it
because
we
wake
up
every
day.
B
Thinking
about
your
workflows,
your
lives,
the
fiction
and
pain
that
you
have,
and
we
want
to
solve
that.
So,
as
we
come
to
a
close
this
morning,
I
want
to
ask
you:
what
does
the
future
look
like
for
you?
What
do
you
need
to
do?
Make
your
life
better?
How
can
we
help
you?
How
do
the
things
that
we
announce
today
bring
some
closure
to
that?
Among
all
the
things
that
you
saw
today
we're
going
to
be
talking
about
these
things
in
detail
tomorrow
as
well,
so
what
we'd
love
to
do?
B
We
would
love
to
see
what
you
build
next
year.
I'll
say
on
stage
next
year,
2019
we'd
love
to
see
what
you
can
do
with
actions
so
submit
your
code
open
source,
it
hashtag
would
github
universe
and
you
have
actions
and
we
want
to
take
a
look
and
put
and
showcase
them
here
next
year.
What
are
you
gonna
build
next,
so
thank
you.
Everybody
enjoy
universe.