►
From YouTube: Integrating continuous integration and deployment with GitHub’s API - GitHub Universe 2018
Description
Presented by Brian Douglas, Developer Advocate (GitHub).
Continuous Integration (CI) is a software practice that requires frequently committing code to a shared repository. When you commit code more often, it can raise errors much sooner which is why this talk will introduce you to how you can leverage the new Checks API alongside your CI to improve your development workflow and reducing the amount of cognitive load code a developer needs for debugging to find the source of the error.
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
A
Good
morning
I
hear
myself:
can
you
hear
myself
see
what
I
did
there
welcome
to
the
Paris
fair
and
the
get
up
universe?
If
you
were,
if
you
came
late,
hopefully
you're
here
to
talk
about,
learn
about
continuous
integration
and
continuous
employment
with
the
github
API,
because
that's
what
I'm
talking
about
so,
if
you're
here
for
that
you're
in
the
right
place,
I'm
actually
I'm
very
happy
to
be
here.
A
This
is
actually
my
third
universe
of
the
for
but
first
time
as
a
github
employee,
so
I'm
really
honored
to
be
speaking
about
github
API
as
an
employee,
because
I
did
that
as
a
non
employee
last
year,
so
show
of
hands.
I
know
80%
of
github
users
are
outside
the
US
raishin.
If
you
came
outside
the
u.s.
A
to
come
to
get
up,
uterus,
I'm,
curious,
okay,
cool,
we
all
did
a
hole
who
came
the
furthest
thing
we'll
just
get
to
write
to
the
talk,
but
I
want
to
be
the
first
to
welcome
you
to
the
Bay
Area
I
know:
Jason
had
talked
about
the
Palace
of
Fine
Arts,
we're
right
next
to
the
Golden
Gate
Bridge.
So
if
you
guys
didn't
know
that
it's
right
outside
so
definitely
check
it
out,
if
you
do
have
time,
it's
quite
a
sight,
it's
actually
we're
having
some
of
the
best
weather
this
week
too,
as
well.
A
So
if
you
are
from
outside
the
Bay,
Area
definitely
take
advantage
that
if
you
can
but
go
to
all
the
talks
too,
as
well
cool,
so
I
understood
myself,
I'm
Brian,
Douglas
I
am
a
developer
advocate
on
the
developer
relations
team
at
github.
These
are
all
my
social
profiles.
It's
also
what
I
look
like
on
internet
on
the
internet
and
github.
That's
what
I
look
like,
but
my
role
is
a
developer
advocate.
A
I
get
this
question
a
lot,
especially
a
github
people
aren't
sure
what
a
developer
advocate
evangelist
developer
relations
like
what
they
do
at
github.
We
have
over
900
employees
and
when
get
up
first
started
10
years
ago,
everybody
was
an
advocate,
and
now
we
have
focus
roles
and
my
role
is
actually
focused
on
the
API
ecosystem.
A
So
a
lot
of
what
you
heard
earlier
today
in
the
keynotes
is
what
the
stuff
I
get
the
tinker
around
with
and
share
with
you
guys,
but
better
describe
my
role,
I
like
to
call
myself
the
Beyonce
of
github,
so
I
I'm,
queen
bee,
so
github
is
a
lot
of
user.
You
have
31
million
developers,
users,
designers,
product
managers,
using
our
platform,
so
I
get
to
constantly
talk
to
you
guys
about
our
products
and
get
your
experiences,
but
I
also
got
to
ask
my
question.
A
I
get
asked
this
question
to
myself
every
single
day,
which
is
what
would
they
do
so?
This
will
be
our
theme
for
today,
if
you
guys
aren't
tracking,
but
for
me
and
what
I
do
as
a
developer
advocate
at
github
is
I
go
to
bat
for
the
hive.
So
Beyonce
is
a
she's,
a
superstar.
Let's
just
say
that
she's
she
doesn't
a
really
good
job
at
what
she
does.
She
also
has
a
very
large
super
fan
group,
probably
teetering
around
the
same
number
as
github
users,
but
she
is
constantly
always
reaching
out
they're
fans.
A
She
is,
she
always
turns
back
and
here's
her
fans,
and
she
also
is
doing
a
really
good
job
of
bringing
up
the
next
wave
of
singers
in
the
stardom
through
Beyonce's
mentoring
program,
which
I
won't
talk
any
more
about
Beyonce,
but
what
I'm
really
focused
on
is.
How
is
your
experience?
I
really
want
to
know
this,
so
if
you
did
get
my
Twitter
profile,
it's
also
in
the
corner
reach
out
to
me.
Tell
me
your
question:
share
your
interaction
today,
get
ahead.
A
A
We
we
created
the
API
a
few
months
after
we
launched
the
pull
request,
mainly
to
talk
to
integrators
all
our
sponsors,
all
the
people
that
we
were
represented
on
stage
earlier
today
are
our
partners,
including
yourself
developers,
so
we
want
you
to
be
having
a
better
interaction,
a
better
experience
with
the
API.
When
that
being
said,
my
focus
of
my
talk
is
about
continuous
integration
and
continuous
deployment,
and
these
are
our
tools
really
to
give
us
the
peace
of
mind.
So
continued
integration.
A
We
have
the
opportunity
to
push
our
code
to
github
and
stuff
happens
like
we
don't
have
to
run
our
tests.
I
came
from
a
team
a
couple
companies
ago
where
our
test
suite
ran
45
minutes.
That's
something
I,
don't
have
to
sit
in
front
of
my
computer
and
run
the
tests.
I
want
the
CI
to
run
that
for
me,
so
I
I
would
shoot
like
Travis
and
circle.
A
So
briefly,
this
is
what
we'll
cover
will
cover
architecting
sea
ice
Club
bit
of
an
overview.
Continuous
integration
is
not
something
new.
We
talk
about
this
every
year
at
universe,
a
lot
of
companies
are
using
this
I'll
just
come
I'll
run
through
a
quick
diagrams
of
explaining
that
process
to
kind
of
support.
My
talk
I
also
want
to
talk
about
the
checks
P
I,
which
is
in
Developer
Preview
as
of
this
summer
earlier
this
summer,
and
show
you
how
you
can
better
integrate
your
apps
and
your
workflow
to
get
into
github
is
API.
A
Also
our
deployments
API
mention
deployments
has
been
around
for
a
very
long
time
since
2014
we
launched
it,
but
we
actually
shipped
some
new
features
which
I'll
talk
about
as
well,
and
then
I'll
talk
about
some
dashboards
as
well,
so
continuous
integration
to
deployments
this
summonses
might
be
a
review
for
you
guys,
but
continuous
integration.
It's
all
about
the
pipeline
like
we're
all
about
get
water
flows.
Continuous
integration
gives
you
a
pipeline
where
you
don't
have
to
worry
about
your
test.
A
Running
you're,
not
too
worried
about
how
you're
staging
and
your
deployment
about
environments
are
getting
shipped
to
production
or
the
staging,
and
this
is
really
based
on
the
backbone
of
automation,
like
there's
no
reason
for
us
to
sit
45
minutes
in
front
of
our
computers
about
45
minutes
an
hour.
It's
barely
six
times
anybody
work,
eight
hours
a
day,
cool
anybody
work
more
than
eight
hours
a
day.
I,
don't
wanna
spend
my
entire
time
as
a
developer
running
tests.
A
That's
that's
pretty
painful,
so
ship
that
to
your
CI
system,
use
parallelization,
so
you
can
run
that
that
test
suite,
like
maybe
a
couple
minutes
if
possible,
and
the
cool
thing
about
CI-
is
that
it's
all
built
in
the
the
the
backbone
of
source
control.
Now
I'm
gonna
make
an
assumption
that
a
lot
of
us
in
the
room
or
github
users
right
was
maybe
I
are
using
git.
You
guys
roll
your
own
stuff.
So
well,
if
you
aren't
using
github,
you
should
definitely
use
it.
A
Hopefully
you
are
since
you're
here,
but
because
you
use
github
as
the
start
of
your
version
control
and
your
interaction
with
your
team,
you
get
to
unlock
a
lot
of
different
cool
features
as
part
of
your
workflow
and
your
solution
for
you
contributing
to
your
codebase
and,
as
Jason
mentioned
early
I'm,
the
kid
Jason
Canada
stole
a
lot
of
stuff.
I
was
gonna
mention,
so
I'm
gonna
keep
referring
to
Jason,
but
last
year
we
two
years
ago
we
launched
github
apps
github
adapts
our
are
our
better
way
to
integrate.
A
What
they're
our
API
and
we
have
a
lot
of
stuff
out
of
the
box
forget
about
and
with
github
apps,
we
also
launched
marketplace,
which
is
a
really
awesome
place
for
you
to
collaborate,
share
your
projects,
but
also
use
other
projects
from
large
companies
and
teams
as
well.
One
of
my
favorite
github
apps
that
are
out
there.
Actually
that
disjoint
marketplace
not
too
long
ago
is
pull
reminders,
pull
reminders.
Is
it
awesome
get
about
built
by
one
developer
developer?
A
Just
like
you
guys
in
the
audience
who
had
an
idea
of
he
was
working
on
a
development
team
and
he
wanted
people
to
look
at
his
poor
quests.
So
he
built
a
tool
first,
integrating
with
slackin
and
later
with
github,
to
notify
your
team
of
you
app
or
quest
that
was
ready
for
Rio,
which
was
his
pull
request.
It's
a
nice
gentle
nudge
I
used
to
always
throw
gifts
at
@mention
people.
A
Now
we
have
a
proper
review
system
with
employ
requests,
so
it's
a
little
easier
that
way,
but
that
the
creator
of
polar
Biden
is
actually
here
today
and
well
speaking
tomorrow
on
the
same
stage,
I'm
standing
on
so
definitely
check
out
Abby
here
about
his
story
and
how
he
switched
tracks
and
careers.
Sorry,
he
tricked
switched
jobs
to
work
on
this
full-time
and
his
experience
is
pretty
awesome
but
an
obvious
example.
A
He
was
able
to
build
a
good
app
app
just
the
fit
his
use
case
with
the
github
API
for
a
feature
that
did
not
exist
on
github.
This
is
pretty
key
like
we.
We
have
a
lot
of
developers.
We
want
to
ship
features
as
fast
as
possible,
but
we
can't
address
every
single
needs,
so
I'm
here
to
hear
your
complaints,
your
your
wins
but
I'm
also
just
gonna
document
those
and
issues
and
PR,
hopefully
eventually,
but
with
obby.
He
was
able
to
identify
exactly
where
in
his
github
app
he
needed
access
to
github
data.
A
Now,
historically
OAuth
apps,
we
opened
up
the
box
to
everything
on
github,
so
we'd
have
to
have
for
your
repositories.
We'd
have
to
have
access
to
organization
repositories
which
is
uncomfortable
for
some
people
for
good
reason.
I
would
github
apps.
You
could
actually
just
present
ooofff
sorry
API
data
for
just
the
interaction
as
you
need
so
obvious
use
case.
A
He
used
his
paw
request,
so
he's
able
to
get
fine-grained
permissions
and
granule
physicians
for
only
pleura
quests
alone,
so
moving
on
from
the
source
control
talk
about
the
build
process
to
within
the
CI
pipeline,
the
build
a
big
old
red
X
on
my
my
build
stage
and
I
think
a
lot
of
us
at
first
when
we
see
that
the
failure
we
kind
of
get
like.
Oh
man,
what
happened
but
having
failures
as
part
of
you
pushing
to
get
and
getting
notified
automatically.
That's
a
good
thing
like
you
want
to
fail
fast
right.
A
You
want
to
find
out
if
something
is
wrong,
if
something's
not
kosher
based
on
your
linting
scripts,
are
your
testing
tools
you
want
to
know
as
soon
as
as
soon
as
quickly
as
possible.
So
you
can
address
that
as
quickly
as
possible
to
I'm
not
a
big
fan
of
shipping
on
Fridays,
but
if
it
was
on
a
Friday
or
on
three
o'clock,
don't
do
that
by
the
way.
But
if
you
did
ship
on
a
Friday,
like
you
wouldn't
know
before
you
walk
on
the
I
office
to
go,
enjoy
yourself
for
the
weekend.
A
A
What
ever
es6
at
the
time
we
just
threw
all
those
conversations
out
the
door
by
adding
linting
to
our
CI
build
system.
Github
actually
did
this
earlier
this
year,
we
actually
early
in
the
summer
we
launched
this,
but
we've
been.
We
actually
removed
jQuery
from
our
github
comm,
there's
a
public
blog
post
that
went
out
a
couple
months
ago,
but
the
way
we
did
this
is
actually
I,
not
sure
if
you
guys
a
fan
of
jQuery,
if
anybody
using
it,
but
that
wasn't
really
the
issue.
A
A
So
it
makes
the
process
of
like
identifying
I
like
I
know
how
to
do
this
in
jQuery,
but
I,
don't
know
what
the
native
commands
are
in
JavaScript
that
actually
the
bots
actually
give
that
to
you
by
default,
which
is
super
awesome.
I
found
this
on,
while
preparing
citizen
talk,
I
found
this
on
reddit
and
I
thought.
This
was
like
the
the
perfect
antidote
for
the
perfect
CI
and
CD
workflows.
A
I'm,
not
sure
this
is
probably
someone
the
Midwest
I'm
just
guessing
by
the
nice
greenery,
but
for
whatever
reason
this
guy
really
wants
to
put
logs.
He
wants
to
ship
logs
to
his
basement,
and
the
best
way
to
do
this
is
by
building
automation
into
his
system.
So
I
mean
the
next
step
is
basically
getting
a
robot
to
do
this
for
him,
or
maybe
just
using
some
sort
of
app
on
his
phone.
A
The
ship
logs
to
his
house
I'm,
not
sure
if
that's
a
thing,
but
you
guys
have
an
idea
you
can
run
with
it
so
not
sure
if
you're
gonna
get
funded,
though
so,
move
it
along.
I
really
want
to
talk
about
our
first
API,
which
we
we
shipped
earlier
this
summer,
which
is
a
checks,
API
short
hands.
Anybody
using
the
checks
API
directly
if
your
applications
very
cool,
all
right
see
some
familiar
sweaters
as
well,
our
hoodies,
the
checks.
Api
is
the
successor,
not
even
successor,
it's
the
more
advanced
version
of
our
existing
status
API.
A
So
we
provide
way
more
context
to
your
code
and
your
your
CI
systems,
and
this
is
a
brief
example
of
this,
so
you
actually
get
sophisticated
feedback
within
EPR,
so
very
similar
to
what
we
were
talking
about
with
a
jQuery
example
and
providing
checking
your
your
job
of
your
jQuery
code
and
then
providing
those
annotations
within
your
check
system
on
your
pull
request
tab.
You
can
do
that
with
our
checks
API.
So
this
is
available
today
and
developer
preview
for
you
guys
to
tinker
with
and
find
out
ways
to
improve
your
developer
workflows.
A
One
of
our
partners,
Travis
CI,
is
one
of
our
our
first
CI
systems
to
actually
use
the
checks,
API,
so
they're
actually
using
this
today.
So
if
you
install
Travis
on
a
new
repo,
you
will
be
using
their
new
github
app
that
uses
the
checks,
API
system
and
great
part
about
this
is
Travis
really
as
month.
Among
other
solutions,
they
can
really
encompass
this
entire
build
step
and
then-
and
then
some
too,
as
well
by
having
this
part
of
your
CI
workflow.
A
So
once
you
push
to
github
your
test
mode
and
run
on
Travis
and
you
can
find
out
all
information
annotations
within
your
pour
quest
and
the
cool
thing
about
this
is
like
historically-
and
this
is
still
true
like
you-
can
still
go
to
Travis
CI
org
and
look
at
your
your
failure.
If
you're
passing,
look
at
all
your
repos,
but
we're
now
bringing
that
information.
Travis
is
now
a
partner
to
us
us
and
brought
the
information
native
to
your
app
Laura
quests.
A
A
I've
missed
my
last
slide,
but
now
we
have
the
checks.
Api
system
I
asked
a
question:
what
would
they
do?
Alright
sorry,
I
didn't
really
set
my
I
just
ruined
my
my
punch
line
by
doing
that.
But
what
Beyonce
would
do
is
she
would
open
up
a
poor
quest
with
her
lyrics
for
this
song
check
on
it.
Hey
guys,
a
big
fan
of
Pink
Panther
back
in
oh
six
yeah.
So
this
is
the
her
song
and
Pink
Panther.
The
movie
wasn't
that
great!
A
So
not
a
lot
of
people
know
about
the
song
for
fair,
fair
reason,
but
it's
a
great
song
and
I
opened
up
a
poor
quest
at
one
of
my
repos
I've
created
a
markdown
file
and
I
added
the
lyrics
to
Beyonce
song
to
my
PR.
Now
I
wanted
to
test
out
the
checks,
API
system
and
the
great
thing
about
at
github.
We
have
lots
of
people
shipping
code,
so
one
of
my
co-workers
actually
shipped
a
github
app
that
uses
our
checks
API
and
the
Alex
linter.
A
A
So,
for
example,
gender-based
pronouns
might
not
be
a
good
thing
having
in
your
code,
maybe
in
your
documentation
for
Beyonce,
lyrics
I'm,
not
sure
of
Alex
actually
built
this
for
Beyonce
lyrics,
but
you
know
I,
think
having
girl
and
boy
and
your
your
song
for
reason.
It's
okay,
but
it
might
not
be
okay
for
your
team,
so
you
could
actually
set
up
checks
and
sort
of
have
the
balance
of
what
sort
of
language
you're.
A
Looking
for
what
sort
of
language
you
would
like
in
your
documentation,
so
I
think
a
lot
of
one
of
the
best
examples.
I
always
do
is
I
always
look
for
the
words
simply
like
you
get
this
simply
go
to
user
checks.
Api,
if
you
don't
like
that
in
your
documentation
check
for
the
word
simply
and
then
provide
a
recommendation,
and
then
we
have
these
annotations
here
to
also
provide
that
in
the
response
from
Alex
as
well
inside
of
our
PR.
So
this
going
to
briefly
run
through
some
of
our
endpoints
too,
for
the
checks.
A
Api
first
new
thing
as
part
of
the
checks:
API
is
a
check
run
self-explanatory.
These
are
our
runs
that
we
can
run
annotations
for
the
text
API.
So
if
you
want
to
do
linting,
you
want
to
do
dependency.
Checking
on
your
code.
If
you
want
to
provide
suggestions,
you
would
will
first
want
to
set
up
a
checks,
run
to
the
analyze
your
code
and
perform
that
linting.
The
second
thing
you'll
need
to
know
about
is:
there's
a
check.
Sweet
now
check
sweets
is
a
collection
of
check
runs.
A
So
it's
a
suite,
that's
associated
to
your
poor
quest
and
that's
attached
to
either
by
your
tag
or
your
head
sha.
So
basically,
the
original
commit
that
was
that
created
the
poll
or
quest
that's
attached
to
our
API
and
that's
how
we'd
identify
it
so
by
default
all
check
all
PRS
today
have
the
checks
check,
suite
initiated
so
you'll
have
a
tab
start.
If
it's
not
today
will
be
valid
it
rather
soon.
A
If
you
haven't
opted
in
to
our
preview
and
then
you'll
see
new
checks,
so
you
can
now
add
checks
to
your
your
PRS
and
more
diagrams.
So
this
is
the
workflow
for
the
checks
API
by
default.
As
I
mentioned,
check,
suite
is
created
and
the
initiation
of
your
push
and
then
you'll
run
a
check
run
event,
so
you
could
have
as
many
check
run
events
as
you
would
like
onto
your
PR.
A
So
if
these
are
custom
actions,
as
we
had
mentioned
before
the
github
actions
that
we
launched
today
or
if
these
are
github
apps
that
are
gonna,
start
doing
some
checks
for
you,
you
could
also
do
that
as
well
and
then,
after
the
check
runs,
you're
gonna
run
you're
gonna
be
able
to
send
statuses
back
up
to
your
UI,
so
whatever
status
or
annotation.
So
you
want
to
send
back
to
UI.
You
can
do
this
today
within
that
with
the
github
API.
A
And
if
you
wanted
to
test
it
out
as
well,
you
could
also
test
it
by
just
simply
using
curl
or
even
our
graph
qou
api
using
the
graphical
explorer
if
you're
a
graphical
fan-
and
this
is
a
this
another
close-up
of
what
I
was
talking
about
about
using
the
gender-based
pronoun
and
providing
suggestion.
I
may
be
using
the
word
kid
instead
of
girl,
I'm,
not
sure
if
that
rhymes,
with
in
beyonce
scheme
of
her
rhyming
scheme.
But
you
know
it
might
help
you
as
an
artist.
A
Another
cool
thing
is
that
you
can
quit.
You
can
also
set
up
clicking
through
to
your
annotations
inside
of
your
checks,
API.
So
if
there's
a
specific
line
that
you
would
like
to
provide
suggestions,
which
is
a
new
feature
that
we
ship
very
recently,
you
actually
click
through
provide
suggestions.
If
your
checks,
API
or
your
check
suite,
is
not
already
doing
it
for
you,
it
also
provides
suggestion
through
API
as
well,
so
I
think
the
possibilities
of
what
you
can
do
as
far
as
checking
your
code.
A
We
have
a
lot
of
examples
we
had
run
through
just
now,
but
I
would
love
to
hear
your
examples
definitely
reach
out
to
me.
My
twitter
handles
on
the
bottom,
but
we're
not
done
I'm
gonna
talk
about
the
deployments
API
as
well
so
deployments.
Api
is
something
I
mentioned
it's
been
around
since
2014.
It's
something
that
a
lot
of
our
partners
integrators
are
using
today,
but
we
had
shipped
up
some
new
features
out
to
today.
A
So
let
me
just
talk
about
this,
but
before
I
talk
about
the
employments
API
I
want
to
talk
about
my
personal
experience,
so
I
keep
mentioning
this
company
I
work
for
him.
The
company
I
work
for
we're
only
ten
engineers,
and
it
was
here
in
San,
Francisco
Cisco
was
actually
the
company
that
moved
me
to
the
Bay
Area,
oh
hello,
so
it's
the
company
moved
me
to
the
Bay
Area,
so
it's
very
small
team.
We
were
still
tricking
it
out.
We
just
got
funded.
That's
why
they
hired
me.
A
I
was
part
of
that
sort
of
onboarding
process,
but
we
had
a
lot
of
problems
in
the
way
we
we
ship
code
for
one
we
didn't
have
a
staging
environment,
so
I
was
I,
was
part
of
the
team
that
actually
create
staging
environments,
and
the
way
we
did
this
is
that
we
created
a
stage
in
my
honor.
We
were
set
up
on
Heroku
and
we
created
staging
environments
for
it.
A
At
the
time
we
had
four
staging
environments,
not
pictured
his
MO,
but
we
had
each
staging
environments
was
named
by
simple
sentence:
character,
I
think,
there's
two
of
the
hardest
problems
as
developers
today
in
engineers,
one
is
n,
+1
queries
and
the
other
ones
naming
things
so
once
we
started
naming
things
sentence
characters
we
just
kept
going
at
it,
I
think
about
a
time
we
left.
We
had
like
six,
the
staging
environments,
but
this
was
a
very
manual
process.
So
every
morning
I
would
wake.
A
When
I
had
a
feature,
as
at
the
end
of
the
Sprint,
to
have
my
stakeholders
review.
My
product
managers,
marketing
team
I'd
have
to
run
our
art
commands.
We
use
arc
on
the
command
line,
to
sort
of
help
with
our
deployment
process
and
very
similar
to
hub,
if
you
guys
use
that,
but
I
would
have
to
check
arc
and
check
which
stagings
are
available
and
I
would
grab
that
staging
cuz.
We
had
a
script
to
basically
wipe
out
all
stagings.
A
So
that
way,
if
anybody
claimed
the
staging
environment
we
had
to
make
it
fair
to
like
anybody
who
came
in
early
are
logged
in
from
home
can
grab
one.
So
literally,
that's
what
happened
like
there
were
no
staging
environments
by
8
a.m.
because
everybody
was
this
really
wanted
to
ship
their
code
really
fast,
so
I
would
run
our
quit.
Staging
find
out
with
staging
environments
so
I
see.
A
Homer
is
available,
I
grab
Homer
using
another
art
command
and
then
I
go
about
my
day
and
I
can't
to
ping
people
in
slack
and
say,
look
at
my
code!
Look
at
my
code.
Look
at
my
code
and
this
is
super
problematic.
Is
we
only
had
at
the
time
for
stage
environments
and
ten
engineers?
So
we
constantly
had
this
like
weird
battle
of
like.
A
Why
is
this
staging
environment
like,
and
then
we
had
people
who
really
knew
how
to
use
arc
and
the
command
line,
and
they
would
basically
just
own
staging
environments
for
the
whole
week
through
scripting
small
team,
but
people
had
a
lot
of
free
time
apparently,
so
this
is
problematic,
so
I
always
I
always
had
the
same
point.
I
always
wanted
the
operated
the
opportunity
to
basically
when
I,
open
up
law
requests,
I
want
a
staging
environment
like
I'm,
ready
the
codes
ready
for
review.
A
I,
know,
engineering
sort
of
take
atop
some
time
to
review
code
and
QA
and
I
also
want
to
have
that
ready
to
go
so
I
can
start
talk
to
my
stakeholders
and
product
managers.
So,
as
a
developer,
I
wrote
this
I
want
to
trigger
to
place
as
the
pork
was
open,
so
I
can
offline
staging
management
to
my
automation,
my
CI
at
a
mission,
and
the
great
thing
about
that
is
today
there's
a
lot
of
different
tools.
A
You
could
do
for
this,
including
Heroku,
as
I
mentioned
at
that
time,
Heroku
shipped
their
review
app
process
and
their
pipeline
workflow.
So
that's
available
to
you
today.
There's
a
company
that
I
like
which
is
net
with
AI,
which
they
do
this
by
default,
so
they're
using
our
deployments
API
at
github
to
ship
a
poor
request
for
every
push.
So
not
just
for
sorry,
it's
ship
staging
environment
for
every
push
so
including
branches
pour
quests
as
well
as
production.
A
So
just
for
my
example
like
we
do
have
a
lot
of
different
deployment
strategies
that
you
can
use.
Github
is
here
to
you
use
whatever
is
best
like.
We
just
want
to
get
you
shipping
code
as
fast
as
possible
for
my
use
case,
I
use,
Nell,
Fi
and
identified
now
solves
my
problem
for
making
up
Simpson's
names
or
trying
to
keep
up
to
date
with
whatever
season.
31
Simpson's
are
doing
and
creating
new
staging
environments
like
that.
A
Now
that
is
solved
for
me
with
the
deployments
API,
and
it
looks
like
this
so
based
on
a
per
shipment
I,
can
set
up
a
web
hook.
I
guess
I'm
a
github
app
I
can
now,
as
of
today,
set
up
a
github
action
as
well
to
watch
for
a
web
hook
and
then
create
a
deployment
event
so
from
there
I
create
a
deployment
event
I
trigger
my
third
party
service,
which,
for
this
use
case,
its
net
left
nullify
triggers
to
deploy.
A
I
have
a
status
a
bit
and
I'm
updated
it
within
my
my
github
CI
other
cool
thing
I
want
to
mention,
and
the
reason
why
I
chose
nettle
Fi
is
that
they're
also
used
in
the
checks
api
natively
within
their
application.
So
now,
if
I
has
a
lot
of
different
features
which
I
won't
cover
today,
I'll
cover
one
of
them
that
are
using
checks,
basically
they're
running
their
own
checks
on
their
system
and
they're.
Providing
that
data
back
to
github
to
them
per
Mille
to
present
within
our
CI
system,
all
right.
A
Sorry
within
our
PR
requests
like
yeah,
exactly
we
don't,
we
do
have
a
CI
system.
We
use
other
CI
systems.
So
as
I
mentioned,
that
Liffe
I
was
using
checks.
Natla
Phi
has
this
feature
called
redirects.
So
because
it's
a
static
deployment
tool
which
I
did
not
mention,
you
can
actually
set
up
redirects
natively
within
the
net
laughs
I
dashboard.
You
can
also
do
that
within
your
code,
so
you
can
create
a
redirect
file
which
I've
done
so
I
created
a
redirection
file.
A
I
incorrectly
wrote
a
redirect
and
then
you
can
already
see
natla
fires,
checks,
usage
now
prevents
me
and
says:
hey
your
redirects.
It's
not
gonna
work.
If
you
deployed
this,
so
you
wouldn't
actually
check
out
our
docs
to
find
out
exactly
what
you
did
wrong.
If
I
did
something
a
little
more
complicated,
they
provide
annotations
based
on
what
I
did
wrong.
It
may
be
suggestions
and
how
to
fix
it.
So.
A
With
that
being
said,
that's
our
deployments.
Api
I
didn't
mention
specific
things
that
we've
updated,
so
everything
I
mentioned
is
all
been
existing
since
2016
one
of
the
newer
things
couple
new
things
that
we've
hadded,
we
added
a
new
status,
which
is
inactive,
so
it's
possible
that
you
want
to
deploy
something
to
staging,
but
some
services
do
you
do
limit
to
you
and
how
many
instances
you
have
open,
so
you
can
have
setup
inactive.
So
after
a
week
a
couple
days,
she
can
set
inactive
to
this
staging
environment.
A
You're
also
set
inactive
for
on
the
close
up
or
quest.
So
the
core
request
is
closed.
There's
no
need
for
that
staging
environment
go
ahead
and
set
that
the
environment
to
inactive
and
whether
or
not
you
want
to
use
their
API
that
third-party
service.
You
can
also
delete
that
that
environment
as
well
couple
other
things
too,
as
well,
is
that
we
do
have
two
different
flack
are
certain
two
different
attributes,
one
being
the
log
hero
and
the
other
one
being
the
environment
URL.
A
So
now
you
can
set
the
staging
environment,
so
the
URL,
the
public
URL.
You
want
to
share
with
the
rest
of
your
team,
and
you
also
set
up
a
log
URL
as
well.
So
now
that
the
distinction
exists
for
you
previously,
everybody
was
using
the
same
attribute
to
set
up
a
URL,
so
I
say
all
this
and
I
still
haven't
mentioned
one
of
our
biggest
ships
to
for
a
deploys
API,
which
is
the
deployment
dashboard.
A
So
now
natively,
along
with
checks,
you
do
have
access
to
all
you
deploy
so
any
deploy
that
you're
associating
with
the
status.
You
now
can
look
at
your
deployment,
dashboard
and
I
think
that
one
of
the
coolest
things
that
we
got
this
by
default,
because
we
we
ship
github
pages
and
that's
that's
a
feature
that
we
have
all
github
pages
sites
now
have
a
deployment
dashboard.
So
previously,
if
you
guys
have
used
github
pages,
you'd
have
to
kind
of
sort
of
figure
out
whether
it
failed,
whether
it
build
succeeded.
A
A
Sorry
to
add
deployment
statuses
to
your
your
dashboard,
that's
it
today!
So
if
you
Roo
it's
the
not
the
best
code,
I
definitely
worked,
wrote
it
on
Sunday.
But
if
you
want
to
use
this,
you
can
also,
if
you
haven't
delphi
installed,
go
ahead
and
install
log
Fi
and
your
logs
are
actually
be
populated.
Every
time
something
is
deployed,
and
this
is
something
I
built
as
a
get
up
app
to
you
as
well.
A
You
could
also
see
histories
of
what
ships
as
far
as
what
you
deployed
I'll
get
a
pages,
so
your
entire
history
is
available
to
you
within
your
deployment
dashboard
and
with
that
being
said,
we
now
have
a
fully
automated
pipeline.
Like
I
talked
about
staging.
That
was
my
use
case.
That
was
my
problem,
but
she
now
have
production
as
part
of
your
CI
platform.
A
So
if
you
want
to
set
up
an
event
to
whenever
something's
merged
deployed
to
production,
you
can
setup
that
natively
so
I
know
a
lot
of
our
tools
and
a
lot
of
partners
have
this
by
default.
If
you,
if
you
merge
a
floor,
quest
you'll
have
a
deploy,
but
if
you
are
using
a
tool
or
if
you're,
rolling,
basically
building
your
own
AWS
clusters
and
docker
containers,
you
could
also
set
it
up
as
part
of
your
CI
workflow
strategy,
and
all
you
have
to
do
is
know
how
to
use
the
API.
A
Also
mentioning
that
this
a
lot
of
the
newer
features
are
Developer
Preview.
So
you
do
have
this
header
tab
to
basically
use
some
of
these
features.
One
feature
as
well:
I
mentioned
github
Maps,
you
get
a
nice,
a
nice
github
performed
by
github
object.
If
you
do
use
a
github
app
to
do
your
deploys.
So
just
keep
that
in
mind.
I
know
is
I
also
had
some
time
on
stage
talking
about
actions
too,
as
well
and
I'm
a
fan
of
site,
so
I
wanted
to
make
a
mention
that
they
also
ship
their
github
app.
A
So
you
can
also
based
on
pleura
question.
You
also
have
a
review
part
of
your
pleura
question,
can
have
a
staging
environment
for
your
poor
class
and,
of
course,
site
also
doesn't
have
logs.
Yet
so
I
built
a
cool
app.
That's
called
now:
that's
a
deploy,
sort
of
playing
off
that
hole.
Now,
that's
what
I
call
music
but
anyway,
sorry
my
dad
joke
sort
of
fell
fell
flat,
but
so
I
built
an
app.
A
So
if
you
are
using
now
also
very
simple,
20
20
lines
of
code,
if
you
would
like
to
use
that,
I
definitely
check
that
out
with
that
being
said,
like
the
github
API,
as
I
mentioned
before,
when
I
first
started,
it's
been
around
for
10
years,
it's
here
to
empower
you.
So
if
there's
something
this
year
that
we're
missing
or
there's
an
edge
case
that
you
would
like
to
see
in
github,
it's
quite
possible.
A
You
could
also
build
it
yourself
and
share
with
others
very
similar
I
mentioned
with
ABI
and
building
his
own
solution
for
pool
reminders.
You
could
do
the
same
thing,
so
I'd
love
to
hear
your
use
cases
and
hear
what
sort
of
things
you're
building
as
well
so
definitely
hit
me
up.
Some
next
steps,
you're,
probably
wondering
how
can
I
get
started?
How
can
I
start
using
the
API
stuff?
You're,
probably
like
I,
already
know
where
to
go
and
that's
developer
to
get
up
and
calm.
A
So
all
of
our
Doc's
are
available
upper
get
help
calm
there
you
can.
You
can
play
with
what
I
haven't
mentioned
yet,
which
is
the
graph
QL
API
as
well.
We
do
have
graphic
Explorer,
which
is
available
to
you
to
be
able
to
tinker
with.
We
do
keep
up
to
date
with
change
logs,
so
definitely
keep
track
of
our
our
changes.
Tab
on
the
developer,
deck
head
up
calm,
so
you
can
get.
You
can
find
out
quicker
before
gum
in
the
universe
once
a
year
when
we
do
make
changes.
A
Also
on
this
site
is
a
QuickStart
guide,
so
my
coworker,
who
is
based
in
Amsterdam,
wrote
a
QuickStart
guide
on
how
to
get
started
with
the
github
app.
So,
if
you're
curious
of
how
to
what
a
github
app
is,
how
do
you
build
one?
You
can
just
check
out
a
QuickStart
guide
to
building
a
get
up
app.
The
tutorial
itself
is
based
in
Ruby,
but
we
do
have
links
for
other
languages
as
well.
A
If
you
happen
not
to
be
a
ruby
developer,
I
think
ruby
is
enough
to
you
could
probably
sort
of
figure
your
way
through.
We
also
give
you
all
the
code
to
write
to
as
well.
So
it's
a
lot
of
copy
and
pasting
big
fan,
I
see
a
Stack
Overflow
shirt
over
here,
I'm,
a
big
copy
and
paste
ER,
and
with
that
big
said
to
you
as
well
the
next
step
for
that,
if
you're
interested
in
actually
playing
out
checks,
API
demo
I
don't
have
a
screen
shot,
but
it's
a
super
long
URL.
A
You
can
check
out
the
checks
API
Ruby
demo,
which
is
the
successor
to
the
QuickStart
guide
for
getting
a
github
app.
It
will
then
give
you
some
code
to
actually
integrate
checks
with
you
system
and
you
can
ship
that
to
whatever
you
would
like
to
do
as
part
of
your
workflow
other
thing.
If
you
want
to
take
this
picture,
this
slide
as
well
get
all
the
apps
that
I
shipped
the
code
is
available
on
github
open
source
for
free
to
you.
A
So
if
you
do
want
to
see
exactly
what
I
did
and
how
my
interactions
definitely
check
that
out,
those
are
the
URLs
as
well
as
my
coworker,
who
built
the
the
winter
Alex.
We
did
get
a
mention
of
this
on
stage
two
today,
which
is
Probot
robots,
are
really
a
good
way
if
you're
into
JavaScript
and
node.
It's
all
a
lot
of
pre-built
stuff
for
you
for
free
to
get
your
github
app
started
rather
quickly.
A
We
also
have
a
CLI
which
you'll
find
in
the
probodh
docs,
which
is
create
Probot
app
aptly
named
from
the
create
react
app.
It's
basically
mirrored
right
after
that.
If
you
use
react
at
all,
as
well
as
a
couple
other
tools
that
also
copy
that
I
think
ember
is
actually
the
original
creator.
The
CLI
are
the
front-end,
app
CLI
and
so
check
out
Probot.
If
you
would
just
want
to
get
started
or
if
there's
an
app
that
you
haven't
found,
the
microplace
is
a
good
chance
that
the
app
itself
is
on
the
Probot
docs.
A
So
we
have
a
lot
of
our
community
members.
Probot
is
open
source
technically
created
by
a:hover,
but
also
open
source
maintained
by
a
community
of
developers
around
the
world.
I
didn't
have
time,
because
by
the
time
I
got
actions.
Access,
I
didn't
have
time
to
build
an
example,
but
keep
in
mind
because
it's
the
github,
API
and
actions
are
built
on
top
of
web
hooks
within
the
github
API,
there's
probably
use
case.
Well,
you
don't
need
to
get
up
map
and
you
just
want
to
build
it
for
your
own
team's
workflow.
A
You
can
get
build
a
get
up
action
to
interact
with
your
workflow
and
build
that.
So
all
these
deployment
strategies
and
things
I
have
mentioned.
You
also
build
essica,
dev
action,
so
I
encourage
you
to
sign
up
for
the
beta
and
sign
up
on
that
site
that
we
provided
today
also
I
also
run
the
github
developer
program
too,
as
well.
So
if
the
blogs
done
enough-
and
you
want
to
talk
to
me
on
a
regular
basis-
you
can
sign
up
for
the
github
developer
program-
buddy
go
into
this
URL
I
have
this.
This
quote.
A
It
takes
a
community
to
build
great
stuff,
so
definitely
check
that
out.
We
do
a
monthly
newsletter,
I
promise,
that's
the
only
email,
you'll
see
from
me
once
a
month
and
we
just
provide
more
context
around
our
api's
examples
and
you'll
hear
from
a
lot
of
more
community
members
through
that
as
well
speaking
of
community.
We
also
have
the
github
community.
A
So
if
there's
something
that
you're
looking
or
you
just
need
some
technical
help
or
support
check
out
github
community
support
forum,
we
have
entire
team,
that's
helping
to
support
github
and
yeah
sorry
support
github
in
the
API
and
ecosystem,
so
definitely
check
that
out
and
with
that
being
said,
this
is
all
my
my
social
profiles.
If
you
reach
out
to
me
again,
I'm
a
developer
advocate
at
github
I
really
want
to
talk
to
you.
I
want
to
hear
your
use
cases
I
might
be
walking
around
the
microphone
doing
a
podcast.