►
From YouTube: Day 2 Keynote - GitHub Universe 2018
Description
Join Julio Avalos, GitHub's Chief Strategy Officer and General Counsel, as well as Kyle Daigle, Jess Frazelle, and others, including in-depth demos 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
B
Hello
good
morning,
everybody
how's
everyone
feeling
great.
We
I'm
not
sure
if
we're
the
only
developer
conference
that
starts
at
9:00
a.m.
the
crack
of
dawn
in
most
engineers
time.
But
thank
you
all
for
coming
and
thank
you
for
coming
to
day
two
of
universe.
I
want
to
thank
all
of
you
for
joining
us.
I
want
to
thank
everyone.
That's
had
a
hand
in
getting
the
conference
set
up
and
I
also
want
to
thank
my
wife,
Sonali
who's
here
in
the
first
row.
B
Sorry,
her
first
universe,
like
lots
of
folks
that
work
at
businesses
and
all
of
you
that
are
engineers
or
entrepreneurs
sonali's,
had
to
listen
to
me
complaining
aspiring
dreaming
about
almost
nothing
other
than
github
for
the
last
six
years,
and
I
really
appreciate
that,
even
while
I
don't
know
giving
me
three
children,
a
lovely
family
and
somehow
being
a
trial
partner
and
litigator.
So
thank
you
Sonali
very
much.
Thank
you.
Thank
you
and
that's
yeah,
and
then
thank
you
to
all
the
spouses.
B
I'd
say
the
partners
everyone
at
home,
while
you
know
folks,
are
out
there
building
companies
and
and
all
that
hard
work
that
that
everyone
does.
As
our
head
of
technology
Jason
Warner
said
yesterday,
we
believe
that
software
is
the
future
and
that
improving
software
development
and
making
it
easier,
more
collaborative
and
more
accessible,
serves
to
bring
people
together
to
improve
their
quality
of
life
and
to
make
their
work
and
business
smarter,
more
productive
and
more
fun.
B
Jason's
keynote,
along
with
our
new
product
launches
point
to
what's
possible
when
we
take
a
developer
first
approach,
not
just
to
coding,
but
to
the
fuller
experience
of
software
development
and
what
it
means
to
be
and
remain
a
developer
today
and
tomorrow.
Today's
conversation
will
continue.
Those
threads
and
I
think
that
you'll
be
even
more
excited
about
github
actions
and
better
understand
its
potential.
B
Once
you
get
to
hear
directly
from
developers
who
have
been
using
it
for
even
a
short
period
of
time,
and
that's
our
focus
today,
the
developer,
the
human
being
at
the
center
of
code
and
the
humans
who
are
building
and
propelling
the
world's
digital
revolution.
After
all,
github
isn't
just
the
world's
most
popular
software
development
platform
or
a
code
repository.
It
is
the
home
of
its
developer
community,
a
meeting
place
for
their
ideas,
their
products,
their
projects
and
their
issues.
That
fact
has
never
been
lost
on
us.
B
B
Many
still
remember
that
for
our
first
six
years
as
a
company,
github
Inc
ran
itself
like
an
open
source
project
of
sorts
and
I've
noticed
that
when
I
talk
about
our
open
structure
days,
people
immediately
want
to
jump
quickly
to
the
fact
that
we
didn't
have
managers
or
titles
or
formal
departments
or
reporting
structures.
And
it's
true.
Then,
when
I
started
in
2012
and
I
see,
Matthew
remembers
and
I
started
in
2012.
B
We
had
none
of
those
things
and
we
were
proud
of
it,
but
taking
our
cues
from
the
way
that
developers,
work
and
think
has
always
meant
more
at
github
than
an
org
chart
or
no
managers.
Our
lawyers
write
in
markdown
and
exchange
contract
red
lines
with
our
sales
team
by
way
of
pull
request,
they
open
source
our
employment
agreements
and
request
edits
to
our
Terms
of
Service
and
Privacy
Policy
by
way
of
open
communication
and
repo
issues
with
our
community.
B
Our
policy
team
advocates,
on
behalf
of
our
community
all
over
the
planet,
on
topics
and
on
perspectives
and
with
perspectives
that
are
important
to
them,
not
necessarily
the
latest
tech
industry,
talking
points
or
white
papers,
but
what
is
actually
important
to
and
motivating
individual
human
developers.
So
when
I
say
that
github
is
a
developer
company,
I
don't
mean
simply
because
we
build
developer
tools,
but
rather
that
everything
that
we
create
is
inspired
by
the
way
that
human
developers
work
or
wish
that
they
could.
B
Today,
github
is
focused
on
building
tools
for
the
future
of
software
development,
breaking
down
silos
between
development
environments
and
reimagining,
core
developer,
workflows,
all
is
code
and
all
accessible
from
within
a
repository
github
actions
which
we
launched
yesterday
will
change
how
developers
write,
share,
review
test
and
deploy
their
code
with
actions.
Anyone
can
write
an
open-source
library
or
in
action
and
I
can
then
add
it
to
my
workflow
and
have
github
execute
that
code
on
my
behalf.
It
removes
friction
from
the
development
experience
and
makes
getting
into
and
maintaining
software
easier
and
more
accessible.
B
It's
the
first
time
that
github
will
be
running
code
directly
today,
you're
gonna
hear
directly
from
people
already
leveraging
actions
to
bring
their
ideas
and
projects
to
reality
and
I.
Thank
all
of
them
for
coming
and
for
participating.
Our
industry's
empathy
and
ethics
have
come
into
question
over
the
past
several
years
and
it's
going
to
be
a
measure
of
our
future
success.
B
The
world
finds
itself
at
a
crossroads.
Over
the
last
several
years,
we've
seen
increasing
discontent
and
impatience
with
the
status
quo,
including
push
back
on
the
technology
industry
and
a
call
for
greater
scrutiny
of
tech
and
Internet
company
and
their
practices.
This
has
been
particularly
true
of
organizations
that
handle
and
control
our
data,
which
is
to
say
that
handle
and
control
our
digital
lives.
B
B
What
do
what
can
we
do
to
get
rid
of
the
scaffolding
that
so
often
surrounds
and
hides
the
true
passion,
the
true
idea
that
a
developer
had
when
they
first
decided
to
log
on
to
github
and
create
their
first
project
or
issue
or
repository
according
to
our
own
internal
data
and
was
confirmed
just
very
recently,
I.
Think
the
last
couple
of
weeks
by
stripes
recent
developer
coefficient
report,
nearly
half
of
every
developers
time
is
spent,
not
writing
code.
B
That's
time,
that's
spent
with
bad
code
error,
maintenance,
debugging,
refactoring,
visiting
a
wiki
searching
for
a
fix
to
a
bug,
a
workaround.
What
the
right
tool
is
for
the
job
that
they
have
or
for
the
stack
that
they
happen
to
be
working
within
its
time,
spent
doing
something
other
than
what
developers
are
passionate
about
and
what
they
were
hired
to
do
in
the
case
of
working
at
a
business.
B
The
decisions
that
we
make
on
the
issues
facing
technology
and
software
development
today,
given
the
foundational
place
in
time
that
we
find
ourselves
in,
will
impact
software
and
technology
infrastructure,
data
and
digital
lives
for
decades
to
come
or
longer.
So
what
should
we
do
at
github?
We
believe
very
strongly
that
we
ought
to
continue
to
humanize
the
experience
and
to
humanize
the
technology
that
we
are
using.
Several
years
ago,
I
was
speaking
at
FOSDEM,
the
free
and
open-source
developers
European
meeting
it
was.
B
It
was
a
fun
meeting
as
I
was
walking
through
the
booths
speaking
to
and
getting
to
know,
members
of
that
community
of
our
community
of
the
software
community,
a
banner
from
the
FSF
caught
my
eye.
It
said
there
is
no
cloud,
it's
just
other
people's
computers.
The
message
was
an
important
one
for
a
variety
of
reasons.
B
Second,
the
fundamental
truth
of
the
statement
of
what
was
being
said,
just
resonated
with
me,
is
true.
There
is
no
cloud
we're
all
just
writing,
storing
and
accessing
data
on
someone
else's
computer
or
on
someone
else's
server
from
where
developers
host
their
code
to
where
they
run
their
code.
The
technology
we
use
every
day
was
created
and
maintained
by
people.
B
It's
important
to
remind
ourselves
now
in
2018,
some
late-stage
of
the
dawn
of
the
digital
age,
that
the
history
of
software
and
the
history
of
software
development
is
one
in
the
same
as
the
history
of
software
developers
from
Ada
Lovelace,
creating
the
first
algorithm
to
Grace
Hopper,
inventing
the
first
compiler
coining,
the
term
bug
to
Margaret
Hamilton
coining,
the
term
software
engineering,
while
leading
the
development
of
the
Apollo
space
program
or
software
program.
The
history
of
software
and
development
is
a
man's
history.
It's
a
woman's
history.
B
It
is
a
human
history
if
the
tech
industry
is
to
find
itself
out
of
the
morass
that
it
finds
itself
in
github
believes
that
it
will
do
so
first
by
recognizing
its
basic
humanity,
its
empathy.
If
ethics
and
its
leadership,
here's
another
quote
from
our
theater
as
a
Brooklyn
artist,
I
like
the
Internet
is
handmade.
B
B
I
would
argue
that
we're
living
in
an
age
that
is
unique
in
human
history,
where
we
have
become
so
reliant
on
technology
that
most
of
us
do
not
understand
that
we
can't
tinker
with
most
of
the
world
has
lost
contact
with
the
fact
that
a
person
or
that
people
have
created
the
names
in
the
world's
tech
companies
and
the
services
that
we
use
on
a
daily
basis.
Someone
built
Facebook,
someone,
wrote
Google
search,
someone
wrote
Netflix
and
the
technology
that
allows
my
wife
to
watch.
B
Bob's
Burgers
on
an
iPhone
at
35,000
feet
was
written
by
a
human
being.
We
need
to
bring
awareness
and
understanding
of
our
tech
to
more
people.
Tech,
literacy
and
fluency
should
become
elements
of
base.
Public
education,
not
just
in
the
obvious
sense
that
more
and
more
kids
should
be
learning
to
code
which
is
a
given,
but
that
we
need
to
build
a
better
understanding
into
the
nature
of
these
technologies
themselves.
What
the
landscape
looks
like
who
owns
what?
B
How
servers
function,
how
websites
operate
what
data
is
actually
necessary
in
order
to
achieve
the
results,
speed
and
services
that
users
have
come
to
expect
from
their
online
offerings
and
that
we
take
as
a
given
in
today's
modern
world?
Github
is
committed
to
teaching
and
mentoring
this
next
generation
of
developers
and
helping
to
ensure
that
key
technologies
are
accessible
to
all.
B
Educating
and
preparing
the
next
generation
of
developers
is
one
of
the
core
tenets
of
github
mission
to
make
software
development
more
open
and
more
accessible.
Github
aspires
to
lower
the
barrier
of
entry
and
provide
an
easy
path
towards
learning
the
tools
and
skills
required
towards
becoming
a
developer,
which
increasingly
are
the
skills
that
are
necessary
to
be
employable
in
the
21st
century.
B
All
of
these
things
have
an
impact
we
have
to
do
both
of
these
things
top
down
and
bottoms
up
to
close
the
job
gap
that
is
increasingly
existing,
and
that
will
be
exacerbated
over
the
next
five
to
ten
years.
That
impact
is
felt
beyond
our
room
and
beyond
the
city
beyond
Silicon
Valley
beyond
this
country.
The
developer
ecosystem
is
not
limited
by
geography.
These
are
community
problems
and
hyper
local
problems
shared
all
over
the
world.
B
The
move
to
international
is
accelerating
we're,
seeing
more
and
more
contributions
to
open
source
from
outside
the
United
States.
If
you
look
at
this
chart,
the
dotted
line
is
growth
from
within
the
US
everywhere.
Outside
of
the
US
is
the
solid
line
it's
picking
up.
The
demand
for
developers
will
only
continue
to
rise.
Encoding
literacy
will
only
continue
to
be
an
existential
necessity
to
employability
in
the
21st
century,
not
just
in
the
United
States,
but
in
macroeconomic
labor
markets.
B
B
1
million
software
development
jobs
at
the
current
pace,
just
in
this
country
alone,
will
go
unfilled
by
2020
unless
we
impact
meaningful
change
to
technology,
how
we
think
about
technology
and
how
we
teach
it,
and
if
we
extrapolate
this
number
to
all
over
the
world,
it's
easy
into
the
many
many
millions,
if
not
tens,
of
millions
of
jobs,
85
billion.
This
is
also
from
the
coefficient
report.
85
billion
dollars
is
assumed
to
be
lost
annually
to
bad
code.
B
What
good
is
it
if
we
increasingly,
if
we
increase
the
number
of
developers
but
don't
make
progress
on
how
we
write
software
or
how
we
access
and
find
the
tools
that
we
need
or
the
way
that
we
learn
the
top
10
countries
were
new
users
coming
from
span
the
globe
new
signups
sped
up
across
the
Middle
East
Africa
and
South
Asia?
In
particular,
we've
witnessed
a
dramatic
increase
in
businesses,
contributing
to
open
source
as
well
any
guesses
on
what
entity
has
the
most
open
source
contributions
on
github,
just
shout
it
out.
B
I
heard
it
I
heard
it
it's
Microsoft
with
almost
8000
contributions
on
github.
This
would
have
been
unthinkable.
10
years
ago
we
have
two
point:
1
million
organizations
using
github
a
40%
increase.
Since
last
year
every
company
is
becoming
a
software
company,
which
means
that
every
company
is
becoming
a
developer
company
and
because
developers
love
open
source.
All
companies
will,
if
they're
not
already
be
forced
to
become
open
source
companies,
but
even
as
I
say
that
the
disjunction
doesn't
resonate
with
me
is
true.
B
We're
coming
out
of
a
period
of
time
with
many
many
false
dichotomies
we've
inherited
paradigms
of
thinking
from
the
20th
century
and
superimposed
them
on
technology,
for
which
it's
in
opposite.
The
20th
century
was
incredibly
disjunctive.
For
too
long
we
were
forced
to
choose
between
business
or
open
source,
private
or
public
profit
versus
non
profit,
where
companies
were
forced
to
choose
between
running
a
successful
business
or
making
a
positive
impact
in
the
world.
B
The
present
and
the
future
will
be
increasingly
conjunctive,
I'm
a
developer
and
an
artist
I'm
a
developer
and
an
entrepreneur
I'm
a
for-profit
company,
but
I
care
about
the
imprint
that
my
company
is
making
in
the
world,
and
my
employees
do
too.
The
lines
are
blurring
all
over
our
societies
and
all
over
the
world
and
for
good
reason.
B
The
same
principles
that
govern
open-source
communities,
the
same
workflows
that
developers
use
to
maintain
projects
the
same
open-source
projects
themselves
are
all
being
adopted
as
in
an
astonishing
rate
by
business
and
we're
seeing
that
reflected
back
in
the
open
source
community.
An
adopting
open
source
to
my
earlier
point
about
github
zone
experiences
isn't
just
a
matter
of
ingesting
open-source
libraries
or
non
proprietary
code.
It's
a
matter
of
teen
culture.
It's
a
matter
of
project
management.
It's
a
matter
of
the
values
that
are
embedded
within
your
teams,
your
companies
and
with
your
employees.
B
It
makes
no
sense
for
your
company
or
for
your
developer,
to
try
to
undertake
an
engineering
challenge
or
to
solve
a
problem
on
the
Thursday
morning
that
a
different
company
saw
the
Wednesday
night
before
or
the
Wednesday
night
six
months
before
or
the
Wednesday
night
a
year
before.
This
is
an
open
source
challenge.
B
Tech
companies,
CTOs
CIOs,
are
too
often
waking
up
every
morning,
not
just
building
the
same
mousetrap
over
and
over
and
over
again,
but
rediscovering
the
very
existence
of
mice.
It
doesn't
make
any
sense
the
problems
of
scale
and
complexity
that
the
world
is
increasingly
facing
and
that
users
end
up
suffering
for
with
the
latest
security
breach
or
privacy
issue
and
their
credit
card
information
floating
around
the
world.
All
of
these
are
functions
of
an
irrelevant
way
of
working
that
companies
are
doing
right
now.
We
need
to
share
with
one
another.
B
We
need
to
share
information
in
a
way
that
open-source
projects
and
open-source
communities
pioneered
decades
ago
and
that
for-profit
companies
and
corporations
are
beginning
to
get
hip
to
today.
We
at
github
are
active,
maintainer,
zuv,
important
projects
that
serve
the
interests
of
developers
and
businesses.
B
We
built
octo
DNS,
we
built
a
technology
that
would
help
to
mitigate
this
and
again
because
we're
not
in
the
DDoS
mitigation
business
and
because
it's
something
that
other
develop
another
developer
companies
could
benefit
from.
We
open
sourced
it.
The
world
should
never
have
to
experience
the
same
problem
again
and
again,
our
legal
team
so
much
and
for
those
entrepreneurs
and
startups
in
the
room.
B
You
know
that
so
much
of
what
goes
into
building
and
creating
and
sustaining
a
software
company
is
legal
in
nature
form
agreements
raising
money,
employment
contracts,
IP
agreements,
Terms
of
Service
privacy
policy.
All
of
these
things
that
every
company
is
paying
for
every
single
day
why
our
services
are
not
so
different.
These
are
opportunities
to
open
source.
These
are
opportunities
to
ingest
open
source.
These
are
opportunities
to
share
with
one
another.
B
Thousands
of
businesses
are
getting
involved
in
open
source
philosophies
and
development
methodologies,
meaning
that
companies
are
able
to
focus
on
their
unique
value
proposition
their
core
business
without
having
to
reinvent
those
mousetraps
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.
None
of
this
future,
we
all
dream
of,
is
possible
without
our
community
and
without
the
human
beings
that
are
building
on
github
and
that
will
build
on
github.
B
All
of
us
together
have
a
responsibility
to
educate
collaborate
and
build
the
most
promising
future,
and
now
I'd
like
to
turn
it
over
to
hear
more
about
what
that
future
might
look
like
with
the
use
of
github
actions,
I'm
going
to
turn
it
over
to
Kyle
Daigle,
director
of
ecosystem
engineering
and
some
amazing
developers
who
are
doing
just
that
with
github
actions.
Thank
you.
C
Thanks
to
Leo,
yesterday
we
showed
you
github
actions,
a
new
way
to
build,
share
and
automate
your
workflows
with
github
actions.
You
can
easily
integrate
the
tools
that
you
already
use,
use
actions
that
other
people
have
built
or
build
brand-new
actions
and
have
complete
control
over
your
workflow.
We
want
to
put
the
power
in
developers
hands
in
your
hands,
like
Julio
mentioned
the
technology
that
we
build
needs
to
be
in
the
purpose
of
something,
and
not
just
for
technology's
sake.
C
When
we
set
out
to
work
on
github
actions,
we
went
in
with
a
bit
of
a
mission.
We
wanted
to
solve
the
pain
of
a
disjointed
developer,
workflow
that
extended
from
writing
software
to
the
act
of
building
testing
and
deploying
that
software.
There
are
many
different
ways
that
we
could
have
tackled
this,
but
while
we
were
building
it,
we
realized
that
there
was
only
one
way
that
github
could
build
this
by
providing
the
power
directly
to
our
users
in
the
open-source
community.
C
By
letting
you
build
the
actions
share
them
with
each
other
and
connect
them
together.
Any
way
that
you
want,
we
would
handle
the
complexities
of
running
the
code.
We'd
handle
the
VMS,
the
execution,
the
api's.
We
would
solve
those
problems,
we'd,
let
you
solve
your
unique
problems,
share
them
with
the
world
via
open
source
repositories
and
let
other
developers
use
them,
fork
them
and
execute
the
workflow.
That's
right
for
them.
No
one
size
fits
all
but
composable
workflows
that
are
perfect
for
you.
C
Yesterday
we
shared
how
you
can
use
github
actions
to
build
and
publish
an
NPM
module,
automate
parts
of
your
github
workflow
to
help
open-source
maintainer
z'
and
deploy
to
any
service
any
cloud.
This
was
just
the
beginning
of
what
we
could
come
up
with,
but
we
didn't
want
to
be
the
only
ones
telling
you
about
github
actions.
About
two
weeks
ago
we
shared
github
actions
with
members
of
our
community
to
see
what
they
could
do
with
it.
These
were
open-source
maintainer,
x'
customers,
ecosystem
partners,
and
we
were
so
surprised
and
delighted
by
their
reaction.
C
We've
been
so
lucky
to
work
with
them.
They're
all
incredibly,
smart,
passionate,
talented
people,
building
some
incredible
improvements
for
github
users.
The
team's
been
working
with
them
over
the
past
two
weeks
and
today,
I'm
going
to
show
you
some
of
what
they've
come
up
with
first
I'm
gonna
show
you
some
really
interesting
uses
of
github
actions
from
our
community
and
from
some
of
the
actions
team.
These
examples
stretch
what
we
thought
was
possible
with
github
actions
and
I
want
to
start
with.
C
Pulu
me
paluma
is
a
cloud
development
platform
that
lets
you
write
cloud
applications
in
infrastructure
in
your
favorite
language.
By
combining
with
github
actions,
we
get
continuous
deployment
to
any
cloud,
AWS
Asscher,
Google
cloud,
kubernetes
or
even
on-premises.
Here
we
see
a
containerized
Ruby
on
Rails
application.
It's
built
in
publish
to
doctor
hub,
runs
as
a
service
inside
a
kubernetes
cluster
and
uses
a
hosted
Postgres
to
sequel
database.
C
The
app
code
in
our
repo
is
just
a
standard
Ruby
on
Rails
application
with
a
docker
file
in
the
paluma
code,
configurator
defines
configuration
for
each
of
the
environments
in
addition
to
the
cluster
database,
kubernetes
object
or
any
other
cloud
services
using
a
collection
of
typescript
modules.
By
using
github
actions
with
paluma,
we
can
edit
any
files,
application
or
infrastructure
related
to
trigger
deployments,
either
by
directly
committing
changes
or
merging
pull
requests.
C
No
manual
steps
or
bash
scripting
required
paluma
uses
infrastructure
as
code
to
take
it
from
there
deployments
can
be
previewed
dift
and
are
recorded
so
that
you
always
know
what
changed,
who
changed
them
win?
Why?
It's
all
very
good,
like
Pulu,
mieze,
github
application,
adds
to
this
and
enables
get
ops
so
that
teams
can
propose,
approve
and
promote
code
from
staging
to
production,
using
pull
requests.
C
Github
actions
logs
page
plus
Kalume
ease
console
together,
give
you
total
insight
into
the
deployment
status,
including
the
docker,
build
logs,
cooper,
nettie
status
updates
and
more
so
that
we
always
know
what's
going
on
just
like
github
checks
already
works.
The
combination
of
github
actions
in
paluma
gives
teams
an
easy,
automated
solution
for
continuous
deployment
of
cloud
applications
in
infrastructure
to
any
cloud
purely
by
using
code,
get
and
get
up
actions.
C
C
So
Nick
opens
an
issue
in
a
repository
and
you'll
notice
that
he
tags
it
with
urgent
to
trigger
a
workflow,
and
this
is
what
the
workflow
looks
like.
First,
we
see
the
issue.
We
checked
that
the
issue
is
labeled
and
that
the
label
is
urgent
and
then,
if
built,
both
of
those
steps
pass
will
go
to
Twilio.
C
Yesterday,
I
mentioned
that
we
don't
only
have
the
visual
editor.
Everything
ultimately
goes
down
to
a
workflow
file.
That
looks
like
this.
We
have
the
title
the
trigger
what
it
resolves.
We
check
for
the
label
and
you'll
notice
that
the
last
action
needs
both
of
the
other
actions
to
pass
in
order
for
it
to
work.
The
final
action
is
also
a
private
action.
This
is
an
open
source.
This
is
inside
the
repository,
so
only
the
folks
that
have
access
to
my
code
will
have
access
to
that
action.
C
Here's
what
the
action
looks
like.
First,
we
pull
in
the
payload
data
that
we
automatically
have
inside
of
the
action
we
create
a
Twilio
client
and
a
github
client.
In
order
to
listen
to
the
text
response
from
Twilio,
we
initialize
a
pub/sub
client
where
we
connect
to
a
pubsub
server.
We
call
the
Twilio
api.
We
wait
to
hear
from
the
pub
sub
server
once
we
do.
We
post
that
response
from
Twilio
into
github
using
qdubs
api.
C
Now
let
me
show
you
what
this
conversation
looks
like
first
I
get
the
message
from
our
action:
I'm
a
little
busy
right
now
and
so
I'll
get
back
to
the
Nick
later
and
you'll
see
what
it
looks
like
inside
the
issue.
My
text
response
is
added
as
a
github
comment.
So
thank
you
so
much
the
actions,
team,
Nick
and
Twilio
for
building
this
demo.
C
Net
left
eye
provides
an
all-in-one
workflow
that
combines
global
deployment,
continuous
integration,
automatic
HTTP
for
your
website,
there's
such
a
useful,
powerful
tool.
That's
also
a
joy
to
use
I
love
this
product.
They
put
together
a
github
action
that
helps
augment
their
core
products.
So
let
me
show
you
what
that
looks
like
when
you
have
a
mono
repo
with
more
than
one
site
in
it.
You
can
now
trigger
the
deploy
only
in
the
sub
sites
that
need
to
be
built.
C
So
in
this
example,
they
have
a
demo,
god
repository,
and
if
we
check
on
net
left
by
we're
building
two
different
sites,
the
demo
god
mo
and
the
documentation
site,
we
can
see
they're
both
live
within
the
same
repository
on
github
now
they've
set
up
a
github
workflow
so
that
every
time
we
push
to
this
repository
it'll
run
our
test
suite,
and
if
the
tests
pass,
then
it
would
check
for
changes
in
both
the
docs
site
and
the
demo
site.
It'll
only
deploy
the
site
that
it
finds
a
change
in.
C
So,
let's
see
that
by
changing
some
code,
I'm
going
to
change
this
simple
index
file
on
the
documentation
site
will
change
the
header
to
say
Ojai
github
or
something
like
that.
Then
we're
going
to
commit
these
changes
and
push
it
to
the
repository
and
now
the
workflow
will
kick
in
so
we'll
head
back
to
net
liffe,
I
and
check
on
the
documentation
site,
as
this
is
running
now,
when
this
deploys
net
Liffe
I
will
actually
build
the
new
build
that
was
triggered
and
once
the
deploy
finishes,
we
can
preview.
C
Those
changes
live,
and
this
is
all
powered
by
connecting
github
actions
to
the
existing
net
left
I
integration.
So
that
way,
the
sub-site
is
only
deployed
using
a
single
mono
repo
I'd
like
to
especially
thank
the
net
laughs
I
team
for
building
this
demo.
They
also
have
a
booth
here,
so
go
check
them
out
today.
Okay,
thanks
bye,.
C
I'm
ridiculously
excited
to
show
you
this
next
one,
so
this
is
a
flick
button.
If
you're
here
at
universe,
you
probably
saw
this
in
your
bag,
and
maybe
you
were
really
curious.
Why
you
got
this
little
silly
thing,
but
now
I'm
gonna
show
you
so
a
flick
button
is
an
IOT
button
that
will
connect
to
your
phone
today.
If
you
download
the
flicked
app
we'll
show
you
how
you
can
use
this
button
to
trigger
any
github
action,
workflow
I'm
github.
C
C
So
yesterday,
I
glossed
over
a
new
event
that
we
added
to
get
up
actions
called
repository
dispatch.
With
the
repository
dispatch
event,
you
can
trigger
actions
from
outside
of
github
into
a
github
actions.
Workflow
so
say
you
have
a
deployment,
dashboard
or
an
existing
tool.
Now
you
can
click
a
button
in
those
apps
and
trigger
a
github
workflow
without
worrying
about
the
get
up
event
itself.
So
I
want
to
show
you
what
it
looks
like
to
change
my
demo
from
yesterday
to
use
this
new
repository
dispatch
event.
C
So,
first
at
the
top
you'll
see
the
flick
button
which
triggers
the
repository
dispatch
event.
Then
very
similarly,
we'll
build
the
docker
image.
We
ensure
we're
only
working
on
master,
we
deployed
a
site
using
sites,
github
action
and
finally,
we
link
the
urls,
and
this
is
how
we
trigger
a
repository
dispatch
event.
You
send
an
API
post
to
our
server
with
whatever
information
you
want
that
event
to
have
you'll,
see
the
button
press,
payload
and
we'll
take
that
payload
and
we'll
pass
it
to
the
github
action.
C
So
you
can
use
that
data
within
the
action
itself.
You
can
go
and
download
the
flick.
App
today
connect
your
github
account
for
the
flick,
app
choose
the
workflow,
you
want
to
run
and
then
literally
just
click
a
button.
This
has
been
so
fun.
The
team
has
really
enjoyed
using
this,
and
so
because
you're,
all
getting
one
I
want
to
see
what
you're
going
to
do
with
your
flick
button.
C
I
want
to
see
your
craziest
idea
the
most
useful
idea,
the
most
valuable
idea,
and
if
you
want
to
skip
the
enormous
line
for
github
actions,
please
share
them
with
us.
By
using
the
hashtag
github
actions,
the
team
will
go
through
the
best
ideas,
the
best
demos
and
will
choose
you
put
you
in
the
demo,
so
the
world
can
use
your
best
github
action.
So,
let's
see
your
ideas.
C
When
we
started
seeing
the
demos
we
knew
we
had
to
have
the
creators
come
and
show
you
their
work
themselves.
Today
we
have
demos
from
Jessie,
Frizzell,
prolific,
open-source,
maintainer
and
champion
of
all
things.
Containers
launched,
darkly,
a
feature
management
platform
for
helping
you
be
confident
with
your
deployments
and
feature
rollouts
hashey
Corp,
providing
workflows
for
provisioning,
securing
and
running
any
infrastructure
for
any
application,
but
first
I'm
very
excited
to
welcome
one
of
our
business
cloud
customers.
C
When
I
showed
github
actions
to
Peter,
he
was
so
excited
about
lowering
the
friction
of
their
compliance
workflows
by
building
a
simple
workflow
using
github
actions.
I
can't
wait
for
him
to
show
you
what
he's
built.
So,
ladies
and
gentlemen,
please
welcome
Peter,
Buckley
senior
automation,
manager
from
chewy.
D
Hi,
my
name
is
Peter
Buckley
and
I
work
for
chewy
at
chewy.
We
sell
food
to
dogs
on
the
internet
dogs,
like
my
very
own
dog
here
Rubik,
but
in
addition
to
food,
treats
toys
even
prescription
medication.
We
sell
everything
for
pets,
millions
of
customers,
multiple
enormous
fulfillment
centers
around
the
country,
picking
packing
shipping
thousands
of
packages,
24/7
support
this
ecommerce
and
we
have
a
bunch
of
in-house
custom
built
software
across
a
number
of
these
ecommerce
and
fulfillment
systems
to
support
all
of
it.
At
chewy
we
use
github
business
cloud.
D
D
Various
software
systems
that
we
support
can
touch
on
the
areas
of
payment
card
info
and
personally
identifiable
in
faux
security,
paper
trails,
audits
and
regulatory
compliance
are
important
to
our
business.
We
need
our
reporting
and
release
notes
to
be
practically
error-free
when
it
comes
to
JIRA
and
bamboo.
They
have
some
quirky
requirements
to
tie
everything
together
from
source
code
through
release
candidate
deploying
to
production.
Jira
wants
that
issue
number
to
be
in
the
branch
name
itself.
It
also
wants
it
in
the
commit
message.
D
Bamboo
as
well
uses
that
issue
number
in
the
commit
message,
and
then
the
PR
title
when
we
merge
two
master
becomes
the
new
commit
message
and
the
issue
number
better,
be
there
too.
Lastly,
bamboo
matches
the
branch
name
format
and
that
selectively
triggers
our
CI
builds
most
of
the
time.
Everyone
remembers
to
include
all
of
these,
it's
kind
of
miraculous
that
they
do,
but
we
want
to
rule
out
the
chance
for
errors
and
mistakes
and
catch
these
formatting
problems
early.
D
Without
that
issue,
number
Peppard
all
around
can
break
down,
and
we
can't
accurately
answer
questions
like
which
build
includes
a
specific
issue.
Can
you
provide
a
report
of
all
the
issue
numbers
between
version,
2.0,
1
and
version
1.9
8,
or
when
did
a
specific
bug
fix
right
down
to
the
minute?
Actually
go
live
on
the
site,
so
at
chewy
we
follow
that
gold
standard
of
the
pull
request,
standard
workflow.
D
It
works
well
with
github
and
it's
a
great
place
to
build
in
value
in
quality
in
no
small
part,
due
to
github
x'
platform
to
catch
some
of
these
unique
PR
and
JIRA
formatting
constraints,
we
were
starting
to
use
Pro
bot,
a
web
hook,
event-driven
nodejs
app,
and
we
chose
to
host
it
in
AWS.
It
works
well,
but
we
found
it
had
some
drawbacks.
D
We
have
to
host
it
ourselves,
which
isn't
too
much
cost
or
time,
but
it
ends
up
being
another
thing
to
maintain
secure
and
patch,
and
it's
written
in
nodejs
and
has
its
own
DSL.
We
found
it
was
a
bit
of
a
learning
curve
to
contribute
features
to
it.
So
when
github
approached
us
a
couple
weeks
ago
with
this
idea
for
a
beta
project,
we
were
really
excited
to
try
out
a
native
to
github
solution
that
would
ease
some
of
these
pain
points
that
we
were
hitting
with
our
current
setup.
D
We
thought
this
would
be
a
quick
win
to
squash
this
bug
in
this
area
of
branch
and
PR
formatting.
When
we
tried
github
actions,
they
just
worked
simple
to
create
setup
and
configure.
They
had
a
really
low
barrier
to
entry,
which
was
very
important
to
us
and
they're
built
into
github.
So
it's
all
right.
There
we
were
able
to
get
up
and
running
right
away.
In
our
beta
period,
we've
been
able
to
get
our
initial
actions
in
place
in
under
a
week.
Now.
Let
me
show
you
what
we
built
using
github
actions.
D
D
So
we
built
this
pair
of
github
actions,
branch
format
and
JIRA
format,
they're
pretty
simple
to
view
and
edit
from
the
built-in
GUI
and
they're,
backed
by
a
txt
file.
That's
a
subset
of
hash,
a
Corp
configuration
language,
so
it
looks
really
familiar
to
us
in
our
developers.
They
can
be
short
and
simple.
You
can
see
the
text
file
here.
We
can
open
pull
request
to
it
to
edit
it
ours
clocks
in
at
about
30
lines,
to
cover
both
of
these
actions
for
our
formatting
needs.
D
Here
you
can
see
the
actions
running
on
a
tab
right
in
the
github
repo
you've
got
the
current
state
and
the
history
all
available
to
you.
Now
this
is
a
model
PR
that
meets
all
the
formatting
requirements.
This
one
is
perfect,
everything's
correct
here.
It's
circled
the
three
spots
where
we
need
that
ticket
number
to
show
up
and
you
can
see
the
successful
checks
reported
back
by
day
actions.
D
We
got
great
logging
from
our
actions
here.
You
can
see
we're
outputting,
that
branch
name
and
see
that
it
matches
the
requirement
to
have
the
ticket
number
in
there.
It's
very
helpful
when
we're
debugging
or
troubleshooting
either
a
successful
new
or
an
existing
failed
run.
Here's
another
example
of
that
log
where
you
see
each
spot,
we
check
for
that
JIRA
ticket
and
we
output
that
they're
all
consistent
and
the
same
now
the
failure
case.
This
is
the
interesting
one.
D
Here's
a
bad
example
where
somebody
just
forgot
one
part:
they
hit
two
out
of
three,
and
so
you
see
it
gets
caught
by
the
action
and
here's
another
flagged
PR
again
they
missed
one
out
of
three,
but
it
gets
caught.
It
fails
and
it
actually
blocks
the
merge,
so
they
have
to
fix
it
before
they
can
get
approval
and
have
that
PR
get
merged
to
master.
So
I
hope
this
gives
you
some
insight
into
how
we're
using
github
actions
and
how
they're
helping
us
streamline
our
SDLC
workflow.
D
E
Good
morning,
hello,
everyone
so
high
sugar
is
a
tool
as
a
company
that
builds
a
number
of
open-source
tools
for
cloud
and
infrastructure
automation,
as
it
was
mentioned
in
the
last
sort
of
demo.
Here
we're
also
the
company,
that's
behind
the
language
that
github
actions
are
based
on,
which
is
quite
cool
and
has
another
fun
fact.
E
E
Hacha
Corp
has
over
seven
open
source
projects
spanning
from
developer
environments
to
security,
tooling
infrastructures,
code
and
resource
management,
and
many
more
we're
happy
to
call
as
a
business.
Over
100
of
the
Fortune
500
are
paying
customers
and
today,
I'm
really
excited
to
demo
github
actions
with
our
tooling.
E
So,
let's
get
started
with
github
actions
and
terraform
terraform
is
our
tool
for
managing
infrastructure
is
code.
You
could
create
resources
on
AWS,
asher
GCP
and
over
a
hundred
50
other
providers.
This
isn't
just
cloud
providers.
This
is
also
stuff
like
fastly,
natla,
phi
Twilio
and
other
tools
as
well
in
this
repository
I've
already
written
some
terraform,
and
this
terraform
sets
up
a
static
website
on
s3
I've
also
already
run
it
once
so
that
the
website
is
deployed
here,
as
you
can
see,
and
what
I
want
to
do
in
this
demo
is
modify
it.
E
You'll
see
pretty
shortly
that
a
bunch
of
checks
start
kicking
off.
As
you
can
see
here.
These
checks
are
all
defined
in
the
actions
workflow.
If
we
go
to
the
actions
tab,
we
could
see
how
that
workflows,
define
what
we're
doing
is
waiting
for
pull
requests
and
after
a
pull
request
is
created.
We're
running
a
few
checks
here,
a
formatting
check
valve
and
a
plan.
E
We're
gonna
see
exactly
how
each
of
these
interacts
with
the
pour
requests
in
just
a
second,
so
we'll
go
back
to
the
pour
requests
and
just
watch
it
right
there,
and
one
of
the
first
things
you'll
see
here
is
that
the
github
actions
bot
has
responded
to
the
pour
requests.
So
when
one
of
our
actions
fails,
we
respond
with
the
error
message
directly
within
the
pour
request.
So
it's
part
of
the
conversation
in
this
case.
E
We
can
see
that
the
formatting
check
failed
and
for
this
type
of
failure
we
you
could
use
the
toggles
next
to
each
of
the
file
that
failed
and
we'll
show
you
a
diff
of
what
we
actually
expected
and
what
you
wrote.
So
in
this
case,
we
could
see
that
for
proper
formatting
the
bracket
should
have
been
on
another
line,
and
so
given
this
diff,
we
could
then
go
back
to
our
branch
and
make
that
change
so
we'll
open
the
file
hit.
Edit,
do
all
this
from
the
UI.
E
So
this
time,
we'll
see
that
we
get
past
the
formatting
step
and
next,
what
we
see
is
a
validation
failure.
The
validate
command
verifies
that
your
code
looks
good
before
touching
any
real
cloud
resources.
In
this
error
message,
we
could
see
that
we
use
the
local
value
called
air
path,
but
it
doesn't
seem
to
be
defined
so
again,
just
like
the
formatting.
Let's
go
back
and
fix
that
so
with
formatting
and
validation.
E
These
are
both
really
simple,
but
they're
also
really
common
mistakes
that
are
made
and
they're
also
hard
to
eyeball
on
a
pull
request
review.
So
the
nice
thing
about
this
is
you
have
something
automated?
You
don't
need
to
check
out
any
code
and
it's
going
to
show
you
the
error
messages
right
in
line
with
your
poll,
requests
just
really
simple:
to
do
and
eliminates
the
pull
request
reviewer
from
having
to
do
it.
E
So
now
we're
back
in
the
file
and
we
could
see
we
use
the
air
path
and
we
could
see
that
up
at
the
top
with
the
locals.
We
haven't
actually
defined
it.
So
let's
go
ahead,
do
another
copy
and
paste
and
set
up
the
air
path
here
with
that
everything
is
still
looking
good,
so
we
can
make
the
commit
and
again
this
is
on
the
same
branch.
So
this
is
gonna
reach,
rigor,
all
those
same
checks.
E
We
could
go
back
to
that
pull
request
and
and
wait
and
see
what
happens
with
these
checks,
and
so
next,
what
we're
gonna
see
is
that
we
don't
see
any
errors
and
what
we're
actually
looking
at
here
is
the
plan.
The
terraform
plan
shows
you
what
terraform
would
do
if
you
were
to
make
these
changes
now
it
doesn't
actually
impact
any
real
running
infrastructure,
but
it
goes
and
looks
at
what
you
have
and
what
you
want
and
tells
you
what
it
needs
to
do
to
get
there.
E
In
this
case,
we
could
see
that
it
would
create
an
8,
ABS,
s3
object,
and
the
nice
thing
about
having
the
plan
right
in
line
with
your
pull
request
is
in
addition
to
reviewing
that
the
code
looks
good.
You
could
review
that
after
you
merge
this
and
make
these
infrastructure
changes
that
unexpected
things
are
happening.
You
are
destroying
any
servers.
E
You
aren't
making
changes
to
resources
that
that
pull
request
is
sort
of
out
of
scope,
and
what
a
poor
request
reviewer
might
see
here
is
that
we
specified
a
key,
and
we
forgot
during
the
copy
and
paste
to
change
that
to
error.
So
we
would
have
accidentally
changed
the
index
page
here
again,
pretty
common
likely
mistake,
and
so
our
team
member
might
respond
to
the
pull
requests.
E
Ask
us
to
fix
this
up,
because
you
know
the
code
looked
good,
but
clearly
the
plan
was
a
little
bit
off
and
we
could
go
fix
that
again
in
line
so
we'll
edit.
The
file
we
could
see
where
we
made
the
copy
and
paste
mistake,
change,
indexed
error
and
then,
hopefully,
for
the
last
time,
commit
back
to
our
branch,
go
back
to
the
pull
request
and
see
exactly
what's
going
on.
E
We
wait
for
just
a
few
moments
again
and
all
the
checks
run
again,
so
we'll
get
an
updated
plan
and
this
time
in
the
plan,
we
could
see
that
the
key
was
update,
its
error,
dot,
HTML
everything
looks
good
and
hopefully
a
team
member
at
this
point
approves
the
pull
request
and
we're
good
to
merge.
So,
let's
make
that
merge
clean
up
our
repository
by
deleting
the
branch
and
let's
actually
apply
these
infrastructure
changes
to
do
this
today,
you
still
have
to
tab
back
to
your
terminal.
E
The
first
thing
that
terraform
does
is
shows
you
the
plan
one
more
time.
We
really
want
to
make
sure
that
you're
making
the
changes
to
your
infrastructure
that
you
think
you're
actually
making.
So
we
show
you
that
plan
one
more
time
ask
for
verification.
Everything
looks
pretty
good,
and
so
we
say
yes,
terraform
goes
makes
the
changes.
We
could
tab
back
over
to
our
website
refresh
the
air
page,
and
we
can
see
that
we
have
an
error
page
that
looks
different
now.
E
If
we
go
back
to
the
index
page,
we
can
see
that
that
still
works
too,
and
so
in
this
demo,
what
I
showed
you
is
sort
of
how
the
how
actions
interact
with
terraform
to
both
help
you
with
common,
simple
mistakes,
so
that
reviewers
don't
have
to
think
about
it
and
also
helps
you
collaborate
on
infrastructure
by
seeing
the
plan
and
seeing
the
infrastructure
that
would
change
without
having
to
check
out
any
code
or
run
anything
yourself.
This
makes
collaborating
on
infrastructure,
easy
and
seamless.
Thank
you.
A
F
Both
John
and
I
have
been
building
software
for
decades,
so
we're
really
excited
to
talk
today
about
what
we've
done
with
github
actions,
but
before
that
we'd
like
to
tell
you
a
little
bit
about
launch
dirkly
launch.
Darkly
is
a
feature
management
platform
that
developers
all
over
the
world
use
to
build
better
software
faster
feature.
Flagging
is
a
best
practice
of
taking
bits
of
code,
flagging
them
and
deploying
them
separate
from
a
release.
F
Just
like
github
helps
you
use
git,
better
launch,
directly,
helps
you
use
feature
flagging
better.
We
serve
40
billion
flags
every
single
day,
two
tools
that
you
might
already
be
using
like
envision,
plural,
cite
and
meet
up
with
github
actions.
We've
built
some
really
cool
automated
steps
that
we
think
will
help
developers
use
feature
flagging
even
more
seamlessly
and
john
is
gonna.
Show
them
to
you.
Thanks.
G
Edith,
let's
imagine
that
we're
adding
a
new
live
tile
widgets
feature
to
a
dashboard
application
that
we've
been
building.
Here's
our
dashboard
without
the
live,
tiles
feature
and
here's
the
dashboard
with
the
new
feature
enabled
we
want
to
feature
flag.
This
change
and
use
github
actions
to
make
feature
flagging
a
seamless
part
of
the
development
workflow
we've
already
built
this
feature
on
a
branch
and
we've
got
an
action
setup
that
deploys
this
branch
to
our
staging
environment.
G
Once
a
PR
is
opened,
we're
going
to
go
ahead
and
create
the
PR,
and
this
triggers
our
deployment
workflow.
Once
the
workflow
completes,
our
new
code
is
live
on
our
staging
server,
but
it's
hidden
behind
a
feature
flag.
Now
that
the
new
code
has
been
deployed,
we'd
love
for
anyone,
who's
reviewing
the
code
to
see
the
new
feature,
but
we
don't
want
to
impact
anyone
else
who's
using
our
staging
server.
So
we
use
github
actions
to
turn
a
feature
flag
for
anyone.
Who's
been
added
to
the
PR
as
a
reviewer.
G
We've
got
a
new
action
that
makes
this
workflow
automatic.
Let's
invite
Eli
one
of
our
engineers
to
review
the
code
once
we've
added
him.
Another
github
action
runs
when
the
action
completes
in
launch
Darkly
this.
This
will
add
Eli
to
the
list
of
users.
That
can
see
the
new
feature,
so
we
can
interact
with
it
while
he's
reviewing
the
PR.
Now
we
go
back
to
our
PR
Eli
likes
what
he
sees
so
he's
going
to
approve
the
PR,
and
it's
now
ready
to
go
to
production
as
we
built
this
integration.
G
We
realized
that
github
in
github
actions
are
incredibly
flexible,
but
they
can
be
made
even
more
flexible
by
using
feature
flags
within
workflows.
Here,
we've
made
an
action
that
checks
a
feature
flag.
Every
time
we
do
a
commit.
We're
gonna
add
this
action
to
our
deployment
workflow.
This
action
is
going
to
evaluate
a
launch
Darkly
feature
flag.
G
That
controls
where
we
deploy
based
on
information
in
the
commits
to
start
we've
set
up
this
flag
so
that
when
we
deploy
to
a
production
environment,
sorry,
so
that
we
deploy
to
a
production
environment
if
we're
committing
to
master
or
staging
otherwise.
But
by
controlling
this
workflow
with
a
flag,
we
can
easily
change
the
configuration
as
our
workflow
evolves.
For
example,
let's
change
the
logic
to
deploy
our
new
Live
Tiles
branch
to
a
QA
environment.
Instead
we're
going
to
add
a
new
rule
in
launch
Darkly.
G
We
built
a
new
code
tab
in
launch
Darkly,
it's
populated
by
github
actions,
and
it's
updated
with
every
commit
that
you
make.
It
keeps
track
of
all
the
references
to
a
feature
flag
from
within
your
code.
This
makes
it
easy
to
see
which
services
use
a
flag
and
eventually
clean
up
a
flag
when
it's
no
longer
necessary,
we
can
click
on
references
within
launch
Darkly
and
navigate
straight
to
github
to
see
that
reference
in
context.
Thanks.
F
John
lunch
charlie,
has
more
than
500
customers
worldwide,
who
already
used
us
to
move
faster
with
less
risk.
Some
of
these
customers
have
even
said
that
they
see
a
20%
increase
in
velocity
after
they
started
using
lunch.
Darkly
we're
really
excited
about
the
actions
and
lunch
Darkly
integration,
because
we
feel
that
this
is
really
the
perfect
combination.
F
Software
developers
can
focus
on
checking
code
in
getting
it
out
to
production
at
the
same
time,
while
reducing
risk,
because
they
could
turn
on
and
off
who
gets
access
to
it
at
any
time.
Also,
with
this
integration,
we
got
something
that
we'd
been
wanting
to
do
for
a
long
time,
which
was
really
to
help
manage
the
technical
debt
of
future
flagging
with
the
last
integration
that
John
showed
again.
This
is
related
for
us,
the
perfect
combo
of
agility,
plus
stability,
all
the
things
we
showed
you
John
and
his
team
built
within
two
weeks.
F
H
So
what
github
actions
enables
me
to
do
is
not
be
that
person
anymore,
which
is
great
I
personally,
have
a
very
kind
of
obscure
workflow,
with
github
to
begin
with,
I
have
a
few
repos
on
github,
and
so
I
have
these
bots
that
I
maintain
that
do
various
actions
on
github
already
and
a
lot
of
them
were
like
n
+1
scripts,
where
I
like
loop
over
all
my
repositories
and
then
I
again
call
the
API,
which
is
horrifying.
I
know,
I,
have
shame,
so
all
these
bots
can
actually
be
replaced
with
actions.
H
It
syncs
each
event
with
air
table
so
that
I
can
manage
my
entire
workflow
kind
of
and
all
the
open,
PRS
and
issues
for
all
my
projects
in
air
table.
So
since
actions
gives
you
access
to
like
literally
running
on
any
web
hook
event
like
kind
of
the
things
that
you
would
already
run
on
web
hooks,
like
you
have
so
much
power
here,
it's
really
just
like
arbitrary
code
execution,
which
is
great.
You
know
when
you
want
arbitrary
code
execution
and
it's
like
horrifying
when
someone's
hacking,
your
application.
H
So
this
is
why
I
love
it
and
what
I'm
gonna
walk
you
through
right
now,
it's
one
of
my
like
kind
of
more
obscure
and
crazy
workflows.
First
I'm
gonna
go
over
to
that
side.
This
is
literally
like
the
most
we're
buying
part
of
this.
It's
like
walking
to
the
other
side
of
stage
scarier
than
a
live
demo.
I
assure
you
so
I
actually
pushed
docker
images
to
three
different
docker
registries,
because
I've
been
saying
literally
no
person
should
do.
H
H
Second
one
was
just
fries
on
docker
hub
because
it
matches
my
github
handle
and,
like
my
handle
literally
everywhere
else,
so
I
mirror
images.
There
too,
then
I
have
this
private
registry
that
I
just
host,
and
this
just
started
out.
It's
like
an
exercise
in
hosting
a
private
registry,
but
like
once
you
do
something
you
can't
get
rid
of
it
so
like
these
are
all
lessons,
and
you
know
yes
is
forever.
H
H
So
this,
just
like
literally,
is
my
entire
workflow
on,
like
all
my
repos,
and
it's
so
great,
even
though
it
looks
insane,
it
looks
so
cool
just
like
individual
interface
it's
like,
and
it
was
like
pretty
easy
to
write
and
since
everything's
containers.
It's
like
the
dopest
thing
ever
seriously
so
excited
by
this.
H
So
another
thing
that
I
can
do
on
all
my
repos
is
run.
You
know
make
all
which
were
you
know,
builds
my
binaries.
It
runs
linting
like
it
runs
like
go
fum,
it
does
all
that
stuff
and
then
I
can
do
make
cross,
which
you
know
cross
compiles
my
binaries.
So
this
obviously
leads
to
then
like
pushing
up
my
binaries
into
a
release
and
deploying
a
release
on
github
on
every
single
tag,
like
I
hope
you
all
can
kind
of
see
the
extensibility
here.
H
So
what
this
ends
up
looking
like
is
just
the
log
just
like
anything
else.
It's
very
it's
boring
in
the
best
way.
So
this
is
really
cool.
I
am
like
seriously
so
excited
by
actions
and
I
have
like
so
much
fun
playing
around
with
this
and
I
think
that
the
team
did
just
like
an
awesome
job,
building
it
and
like
I'm.
So
grateful
and
I
am
like
so
excited
to
see
what
you
all
build
with
it
and
I
hope
you
get
like
as
creative
as
possible.
B
Thank
You
Jessie
someone
tweeted
at
me
that
they
had
an
extra
pair
of
socks.
If
so,
I'll
find
you
after
I
find
you
after
I
get
down
it's
amazing
to
see
what
everyone
has
been
able
to
do
in
such
a
short
period
of
time
and
we're
so
glad
to
have
partners
like
you
all
who
take
the
products
and
features
that
we
work
on
and
use
them
to
make
something
amazing
something
real.
You
saw
some
of
these
stories
yesterday
in
this
morning
or
when
visiting
our
building
the
future
gallery
it's
over
in
that
direction.
B
If
you
haven't
gone,
please
do
it's
amazing,
go
take
a
look.
I
saw
tears,
I
saw
a
real
emotion
or
they
were
actors.
Each
of
these
videos
profiles
an
individual
using
open-source
to
drive
real
change
and
each
asks
an
important
question.
We
should
all
be
asking
ourselves
regularly.
What
future
will
you
build?
We
have
one
more
for
you
today
and
after
the
short
video
please
stay
put.
B
We
have
our
I'm
very
excited
our
director
of
social
impact
aid,
Muskaan
yogya,
who
will
be
leading
a
panel
discussion
on
how
open-source
is
addressing
important
social
issues
and
will
the
panel
will
be
populated
with
the
human
utility
project.
The
Gates,
Foundation
and
opti
key
stories
like
these
are
what
make
part
of
what
make
I
suppose
working
at
github
so
exciting
the
real
change,
the
real
impact
that
can
be
created
in
the
world.
B
It's
an
enviable
role
that
github
has
and
that
I
have
of
seeing
how
open-source
can
help
the
world
can
help
address
these
social
issues
and
it's
in
the
DNA
of
every
developer
and
it's
part
of
what
it
means
to
be
an
open
source
developer,
contributing
to
the
public
good
helping
one
another
out.
The
problems
that
we
see
in
the
world
are
ever
pervasive
and
persistent,
but
together
we
will
be
able
to
tackle
them.
Thank
you.