►
Description
Presented by Jamie Jones, GitHub.
GitHub has a rich API available for developers and consumers alike, but it can be a bit daunting to build a full fledged integration. This talk will center on using Probot to accelerate the process, and best practices related to this. It will also touch on some existing Probot apps teams can use today, as well as some ideas for where your next app could go!
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
Okay,
everyone
again,
this
is
building
on
github
with
Probot.
Hopefully,
if
that's
what
you're
looking
to
hear
about
you're
already
here
and
if
not
you
don't
know
to
not
be
here,
so
thank
you
all
for
coming.
I'm
Jamie,
Jones
I'm,
a
Solutions
Architect
here
at
github,
working
mostly
with
our
government
in
public
sector
customers,
but
also
some
of
our
regulated,
regulated
and
compliant
restrictive
customers.
So
financial
services,
healthcare
other
folks
along
those
nature's
so
I
work
out
in
the
field.
A
I
work
out
with
both
for
github
Enterprise
customers,
as
well
as
get
up
calm,
open
source
organizations
based
in
Washington
DC,
open
source
enthusiasts,
as
you
can
imagine,
which
helps
Hayase
into
this
talk
right
here.
So
this
talk
and
my
interest
in
Probot,
if
you
haven't
heard
about
before
you'll,
learn
all
about
it
during
this
talk
comes
from
what
is
in
reality
a
typical
day
in
my
life
out
in
the
field
talking
to
customers.
It
goes
something
like
this.
A
I
want
github
to
do
a
thing
right,
whether
it's
code
review,
whether
it's
a
tit
code
analysis,
whether
it's
making
my
toast
for
me.
Can
you
just
help
me
make
it
up?
Do
the
thing
and
I
typically
then
go
to
that
customer
or
that
prospective
customer
or
that
open
source
group
and
say
have
you
tried
marketplace?
A
Have
you
tried
works
with
right
so,
as
you've
already
heard
today
and
talk
about
platform
and
ecosystem,
we
have
marketplace
which
makes
it
really
easy
to
add
tools
into
your
github.com
environment
really
add
a
lot
of
functionality
and
if
that
doesn't
have
what
you
need.
There's
work
works
with
over
150
integrations,
we've
categorized
them
and
list
them
all
out
for
you.
So
there's
a
lot
of
great
things
you
can
do,
but
then
that's
not
what
the
customers
looking
for
right.
It's
like
I,
don't
want
that
thing.
A
I
want
this
new
thing,
so
I'm
like
cool
great.
We
have
this
great
API.
It's
awesome
you
can
build
on
top
of
it.
A
lot
of
other
people
have
done
that
already.
You
know.
Before
we
had
code
review,
we
saw
a
lot
of
work
done
with
tools
like
for
view
ninja
or
looks
good
to
me
and
then
even
past
that
we
see
things
like
ray
gun
and
century
and
the
CLA
bot,
which
helps
to
ensure
that
all
contributors
to
a
project
have
assigned
the
appropriate
CLA,
so
they
can
contribute
their
code.
A
All
of
this
is
awesome
right,
but
that's
not
what
the
customer
says
right.
The
customers
are
like
that's
so
hard.
It's
going
to
take
too
much
time,
I'm
out
there
with
authentication
ooofff
tokens
HTTP
headers
for
previews.
This
is
all
too
much
for
me
to
deal
with
and
that's
where
I
can
bring
in
my
friend
Probot
to
help
answer
these
questions.
So
if
you
don't
know
yet,
hopefully
you
will
at
the
end
of
this
talk,
there
will
be
a
quiz.
A
Probot
is
a
bot
framework
for
building
things
on
top
of
github
right
incapsulate,
all
the
key
things
needed
to
build
it
get
up,
integrations
yourself
and
make
it
very
easy.
There's
a
webpage
pro
bot
that
github
do
that.
You
can
find
out
more
information
after
this
talk.
So,
let's
look
at
some
examples
of
Probot
bots
that
are
out
there.
Probot
apps
I
guess
is
the
proper
terminology
for
them
that
are
out
there.
Already
right,
you
see
in
the
top
left.
Is
the
new
issue
welcome
bot?
This
helps
you.
A
When
you
have
a
new
contributor
on
board
to
your
project,
it
can
give
a
brief
overview,
maybe
point
them
towards
Docs
the
contributing
information
or
general
things
that
you
would
want
all
new
contributors
or
users
to
know
when
they
join
your
project,
automate
it
with
robot
in
the
middle.
You
have
the
stale
bot.
This
is
one
of
our
most
popular
BOTS
that
we've
seen
deployed
almost
200
times
throughout
the
community.
That,
basically,
can
let
you
mark
issues
a
stale
enclose
them
after
a
certain
amount
of
time
period.
A
For
those
of
you
who
are
used
to
maintaining
open
source,
open
source
projects,
environments
apps,
you
get
a
lot
of
great
feedback
from
the
community,
but
not
all
of
it's
actionable.
Maybe
some
of
it's
just
comments.
Maybe
some
of
it's
pie-in-the-sky
features
they'd
like
to
see
in
the
future
stale
lets.
You
come
back
and
automatically
after
3
months,
6
months,
90
days
whatever
it
may
be
and
say:
hey
thanks
for
this
feedback,
but
I'm
gonna
go
ahead
and
close
it
for
the
time
being
and
finally,
the
bottom.
A
We
have
reminders,
which
is
another
sort
of
pro
bot
app
which
actually
uses
a
command
API,
so
that
you
can
remind
yourself
to
come
back
to
this
issue
in
the
future
right.
Maybe
it's
because
you're
going
on
leave
or
maybe
because
you're
waiting
on
another
feature
to
ship
before
you
can
tackle
this
bug
or
issue
you
can
set
a
reminder
to
yourself.
Hey
remind
me
at
some
time
in
the
future,
to
pop
this
notification
back
up
to
me
a
lot
of
really
interesting
things
that
sort
of
help
to
build
on
to
the
github
workflow.
A
Another
great
example
for
pro
bot
app
right
now
is
the
to
do
bot
or
a
to-do
app,
and
this
will
look
when
you
merge
code
that
still
has
to
do
Xin
them
it'll
go
ahead
and
open
up
a
new
issue
for
you
in
your
repository
with
the
to
do
and
some
information
from
that
to
do
to
remind
you
to
go
ahead
and
fix
it
in
the
future.
You
can
imagine
where
you
can
take
an
app
like
this.
Maybe
you
don't
open
up
an
issue.
Maybe
you
spawn
off
a
branch
and
open
up
a
pull
request?
A
Maybe
you
can
start
sort
of
automating
some
of
the
tools
again
reading
reading
the
comments,
reading
the
lines
to
help
make
this
process
easier,
as
we
saw
earlier
today
with
Help
Wanted
labels
and
other
ways
to
onboard
and
find
new
contributors
to
your
project,
you
could
integrate
that
with
the
to-do
app
to
really
streamline
this
process.
So
these
are
pro
bot
apps
that
are
available
today,
but
not
the
only
ones
right
so
on
the
pro
bot
website,
we
list
over
17.
A
What's
that
13
right
now
I'm
sure
the
numbers
higher
than
when
I
took
this
screenshot
a
couple
weeks
ago,
but
these
are
apps
already
out
there
self
registered
by
the
community
that
you
can
go
ahead
and
install
on
to
your
repositories
right
now.
This
is
a
great
way
to
sort
of
explore
and
see
some
of
the
things
that
are
already
out
there.
A
So
choice
bruit
from
collective
idea.
I
went
getting
ready
to
do
this.
Talk
I
asked
out
in
the
community
for
people
who've
been
working
with
pro
bot.
If
they
had
any
quotes,
they
had
any
advice.
They've
give
because
again
this
this
talk
for
me
is
hopefully
to
give
best
practices
a
to
get.
You
all
excited
to
build
with
robot,
but
then
to
give
you
best
practices.
A
So
when
you're
building
yourself,
you're
sort
of
have
a
leg
up,
you're,
not
starting
from
scratch,
and
so
this
was
the
crew
D
Gabe,
which
I
think
really
sums
up
where
Pro
bot
is
and
why
it's
so
helpful
to
me-
and
hopefully
all
of
you
robots
solved
the
problem.
So
so
simply
for
us
and
saved
us
a
ton
of
time.
We
were
no
longer
looking
for
authentication
and
the
other
complications
of
getting
going.
A
A
So,
let's
talk
about
what
Probot
really
is
under
the
covers
and
why
it's
able
to
be
so
easy
and
and
and
so
stable
already
so
back
at
github
satellite,
much
like
universe,
but
in
Europe
in
May,
announced
that
get
up
gets
more
API
traffic
on
a
daily
basis
than
we
do
get
traffic
from
from
the
web.
Ui
so
think
about
what
that
means.
That
means
that
the
API,
a
much
B
must
be
rich
enough,
so
that
people
can
use
it,
but
B
that
it
must
be
accessible
enough.
A
You
know
from
my
command
line
am
I
trying
to
use
some
sort
of
API
browser
built
into
my
build
into
an
IDE
or
my
browser,
no
I'm
probably
actually
accessing
the
API
through
an
SDK
right.
So
this
abstract
Saul
of
the
API
calls
all
the
functionality
into
the
language
and
technology
that
I'm
already
using
right.
Maybe
that's
something
like
new
github.
A
So
when
I'm
writing
JavaScript
code-
or
maybe
that's
something
like
octo
kit
when
I'm
writing
Ruby
code
and
that's
awesome-
but
this
quote
by
well,
it
could
be
by
someone
is
that
api's
are
nothing
if
they
can't
be
easily
built
upon.
I!
Think,
that's
really
true
right!
So
we
talked
about
how
SDKs
make
communicating
with
either
of
the
REST
API
or
the
graph
QL
API
easy.
There
was
a
bunch
of
other
things
out
there
too.
We
talked
about
web
hooks.
A
We
talked
about
github
apps
and
that's
where
Probot
comes
in
right,
it's
the
glue
for
interacting
with
github.
So
what
it's
really
doing?
Is
it
subtracting
away?
Not
only
your
SDK
but
your
web
hooks
and
your
github
apps
to
have
you
to
give
you
one
simple
framework
for
communicating
with
github
and
all
that
you
need
so
before
we
go
into
what
it
actually
looks
like
to
build
with
Probot.
Of
course,
pro
bots
used
by
a
lot
of
github
properties,
right,
of
course,
github.
A
It's
you
see
a
lot
of
the
open-source
developers
for
pro
bot
being
get
up.
Employees
and,
of
course,
then
other
technologies
like
electronic
Adam
or
building
with
pro
bots,
are
using
Pro
bot
for
their
for
the
repositories
in
orgs.
But
what
really
excites
me
is
that
group
at
the
bottom
right.
These
are
companies
not
really
related
to
get
help
I
mean
they
have
github
orgs.
They
work
with
github
they
integrate
with
github
but
they're
using
Pro
bot
because
it
solves
this
problem
for
them,
and
it's
made
this
easier.
A
Woful
I
was
looking
at
a
repo
yesterday,
where
one
of
their
new
integrations
to
do
with
projects
is
build
on
top
of
it
built
on
top
of
robot.
You
see
the
same.
A
century
auth0
and
they're
off
extend
product
that
they're
looking
at
Pro
bot,
keen,
IO
and
collective
idea.
These
notions
that
well,
yes,
some
pro
bot
apps,
like
stale,
make
it
really
easy
to
manage
your
own
github
workflow
or
your
own
github
repository
and
organization.
A
It's
also
of
strong-enough
platform,
strong
and
a
framework
that
you
can
build
entire
apps
or
businesses
on
it
as
well.
We
talked
about
the
github
marketplace
and
how
that
makes
it
easy
to
sort
of
share.
Your
integrations
share
your
tools
out
to
the
get
up
community
I'm,
really
looking
forward
to
the
day
where
there
are
github
apps
in
the
marketplace,
build
entirely
on
pro
bot
because
it
makes
it
that
easy.
A
So,
specifically,
what
is
pro
bond
enable
right?
It
enables
web
hook
and
event
registration,
so
you
can
easily
handle
events
that
happen
on
github,
whether
by
human
via
by
code,
commit
by
issue
create
and
parse
them
and
manage
them
within
your
bot
within
your
app
it
handles
all
of
the
github
integration
and
authentication
for
you.
It
uses
github
apps
under
the
cover,
so
you
get
the
latest
security
models,
permissions
schemes
and
shacks
it
all
away.
A
You're
left
with
just
a
private
key
that
you
can
give
your
app
that
can
then
interact
directly
with
github,
and
it
simplifies
the
API
interaction
with
those
SDKs
for
you,
one
of
the
really
nice
things
that
is
doing
right
now.
It's
not
just
giving
you
access
to
the
SDKs.
Like
note
github,
it's
actually
adding
a
little
bit
more
syntactic
sugar
on
top
of
it.
A
As
well
so
Brandon
keepers
build
out
a
pagination
function
that
was
not
in
the
actual
node
github
node.js
module
and
add
in
the
Probot,
because
we
end
up
dealing
with
a
lot
of
long
issue,
threads
so
being
able
to
add
in
that
syntactic
sugar
at
the
pro
bot
level
makes
it
really
powerful
one
of
the
things
they're
looking
at
right
now
is
building
out
additional
web
UI
capabilities.
So
let
your
pro
bot
run
as
a
web
server
and
run
webpages.
A
Wouldn't
it
be
nice
if
there
were
pre-made
components
using
github
style,
guide,
its
primer
framework,
so
that
you
can
make
repo
names?
Look
like
repo
names
look
like
on
github.
Maybe
you
can
style
issue
comments
like
github
styles
them
on
github
comm
already
build
these
components,
so
you
can
easily
add
them
into
your
app.
So
you
get
a
near
native,
look
and
feel
or
native
look
and
feel
even
so
again.
Another
quote
this
is
from
zero.
A
Specifically,
the
author:
your
extend
team
who's
looking
at
Pro
bot
right
now,
one
of
the
coolest
things
is
to
have
an
instance
of
node
github
right
there,
since
most
of
my
web
hooks
for
interacting
with
github
anyway
right
there,
you
get
using
a
paradigm
where,
if
something
happens
on
github,
they
receive
the
web
hook
and
then
they
go
and
they
take
an
action
back
on
it,
whether
they
merge
a
pull
request,
whether
they
closed
something,
whether
they
spawn
off
something
entirely
different.
All
of
these
things
don't
happen
in
a
vacuum
right.
A
So
talking
about
that
earlier
slide,
where
I
showed
all
of
the
four
features
of
the
platform
side-by-side
they're
all
helpful
in
their
own
right,
but
you
really
need
to
integrate
them
together
and
that's
what
all
Xero
was
using
Pro
bot
for
so
what
does
it
look
like
to
build
a
pro
bot
app
right,
so
we've
talked
about
wipe,
robots,
important
what
it
can
do.
What
does
it
actually
look
like
to
put
hands
on
a
keyboard
and
build
one?
Well,
the
first
thing
you
do
is
you
stand
up
a
brand
new
github
app
right?
A
You
go
to
your
settings.
Page
go
to
get
up,
apps
click,
the
new
get
up
app
button,
give
it
a
name,
a
description.
You
can
give
it
a
nice
little
logo.
You
can
see
when
I'm
building
this
sort
of
mashups
or
these
Probot
apps
I
like
to
use
the
logos
of
the
different
tools
I'm
putting
together.
So
you
see
a
one:
I
did
with
red
hats,
OpenShift
product,
as
well
as
one
with
AWS
as
ec2
containers.
A
Next
go
ahead
locally
and
instantiate
your
pro
bot
app.
It's
really
just
a
node
project.
Right
now,
there's
there's
thoughts
long
term
about
whether
Probot
wants
to
be
supported
in
other
languages
as
well.
It
was
building
node
right
now,
just
for
simplicity
and
ability
to
ship
an
MVP.
But
what
does
it
look
like
long
term
again,
poll
requests
welcome
to
make
Probot
into
your
language
of
choice,
update
the
environment
variables.
A
So
again
I
mentioned
you
may
download
a
private
key
for
authentication
or
you
know
you
may
store
values
about
what
other
servers
you
want
to
hit,
go
ahead
and
update
that
in
your
dot,
E&V
file
and
finally
create
a
new
JSP
module.
That
will
be
your
pro
bot.
App
it
takes
in
a
robot
parameter;
it
does
something
with
it.
You
can
see
in
this
little
snippet
of
code,
I
have
right
there.
It
listens
to
the
issues,
opened,
webhook
event
and
then
just
logs
out
the
information
that
it
got
back
from
the
server.
A
That's
it
robot
on
you,
give
it
the
github,
webhook
name
and
you're
off
and
running
that
context.
Variable
has
both
the
payload
of
the
event
has
access
to
the
github
API
and
has
other
information
and
helper
methods
that
you
can
go
and
do
more
interesting
things.
So
this
is
what
it
looks
like
to
build
an
app
from
scratch.
This
is
as
simple
as
of
what
a
real
app
can
be.
This
is
four
lines
of
code.
A
You
still
have
the
repo
but
you're
not
actively
working
on
it
and
instead
of
getting
issues
from
all
of
people
in
the
community
who
are
like
hey,
can
you
upgrade
it
to
the
newest
version
of
this
refrigerator
or
hey?
Can
you
use
this
great
new
API
from
this
other
person?
Your
answer
is
like
look
I
appreciate
it
you're
welcome
to
do
it,
but
I'm
not
going
to
do
it
anymore.
The
autoresponder
app
is
a
great
way
that
you
can
set
up
robot
to
do
those
responses
for
you
so
again.
A
Looking
at
what
this
is,
it
listens
to
the
issues
opened
event.
It
goes
ahead
and
it
reads
an
issue
reply
template
from
your
github
repository.
It
reads
that
template
into
a
proper
string
and
then
it
goes
ahead
and
it
writes
it
back
to
your
github
repository
as
a
comment
following
on
to
that
original
issue.
That's
four
lines
of
code
and
you've.
Now
automated
your
interaction
for
this
closed-door
type
of
project
with
everyone
in
the
world
no
longer
dealing
with
notifications,
no
longer
dealing
with
the
guilt
of
having
to
tell
people.
A
No,
let
the
bot
do
it
for
you.
Let
the
app
do
it
for
you,
so
a
couple
of
gotchas,
as
you
start
thinking
about
your
own
robot
apps,
in
which
you
want
to
do
with
them
right
now,
since
we're
running
on
node
and
we're
using
some
of
the
latest
features
of
node,
it
does
require
a
relatively
new
version.
This
becomes
more
of
an
issue
when
you
want
to
deploy
it
to
certain
platforms
which
are
only
providing
access
to
the
long-term
releases
of
node
currently
for
I
know
the
end
of
this
month.
A
Node
jumps
up
to
the
next
long-term
release,
which
I
think
is
eight
if
I'm
correct.
So
this
should
hopefully
resolve
some
of
those
problems.
But,
as
you
know,
you
know
not
all
platforms,
not
all
services
will
update
that
fast
again.
I
do
a
lot
of
work
with
OpenShift.
As
of
late
I've
been
working
with
a
bunch
of
customers
there
and
their
platform
only
provides
a
node
6
container
to
use
and
I
can't.
Imagine
that's
going
to
be
updated
much
before
the
beginning
of
next
year.
A
So
just
keep
that
in
mind
as
a
gotcha
one
of
the
nice
things
about
pro
bot
is
we
give
you
a
local
development
environment
as
well
as
giving
you
an
easy
way
to
deploy
it
up
to
a
cloud
provider
as
well.
We
use
a
tool
called
local
tunnel
which
gives
you
a
sort
of
a
dynamic
DNS
route
to
your
own
local
system.
The
only
gotcha
I
would
say
here
is
make
sure
you
give
it
a
unique
name:
we've
had
developers
in
the
past
who
have
used.
A
You
know
Jamie's
Probot,
for
example,
as
all
of
their
DNS
names
and
what
they
won't
realize
that
app
a
is
sending
events
to
app
B
that
they're
currently
doing
and
testing
at
that
point
so
definitely
think
about
unique
names.
It's
also
something
that
needs
to
be
stored
in
the
github
app
config.
Don't
forget
to
download
the
get
a
bat
private
key
when
you
define
the
github
app.
The
private
key
is
not
something
that's
available
at
that
point.
A
It's
only
available
in
the
next
page,
so
there's
I
can
count
on
two
hands
the
amount
of
times
I
fire
up
an
app,
and
it's
can't
connect
to
github
can't
authenticate
like
what
is
going
on.
I
know.
I
said
I
could
check
my
github
app
configuration
I
checked
my
env
files.
Everything
looks
good
and
it's.
Oh
that's
right.
I
actually
forgot
to
pull
down
the
latest
private
key
for
this
app
NPM
install
early
and
often
like
any
good
open
source
project
under
active
development.
A
There
new
features
being
added
at
all
times
so
be
sure
to
pull
down
the
latest
updates
to
those
libraries
and
modules
you're
using
but
like
with
all
things
NPM.
Just
don't
do
it
on
an
airplane.
Don't
do
it
on
a
train?
Don't
do
it
anywhere
that
you're
not
really
comfortable
with
the
Wi-Fi
and
the
load
you're
about
the
stress
on
the
system.
A
couple
of
the
notes
when
deploying
to
a
pass
make
sure
that
it
can
start
before
the
web
request
times
out.
A
We've
had
users
playing
around
with
lambda
users
playing
around
with
other
sort
of
deployment
containers,
and
it
takes
the
container
itself
a
little
while
to
spin
up
so
imagine
you
have
a
web
request
that
times
out
in
ten
seconds
or
30
seconds.
Can
your
containers
spin
up
before
that
web
request
times
out
so
again,
gotchas
to
think
about
of
where,
where
you
deploy
these
applications
to
and
finally
get
about,
permissions
can
be
frustrating
understand
the
permission
scheme.
A
We
are
working
and
we're
actively
working
on
improving
the
layout
of
the
get
up,
apps
permission
scheme,
making
it
clearer
how
web
hooks
are
what
permissions
are
used
for.
So
it's
it's
a
got
to
that
even
I
run
into
I
was
talking
internally
to
our
platform,
support
team
which,
if
you
have
it
as
your
been
building,
apps
or
building,
integrations
that
get
up
if
you've
never
emailed
out
to
help
to
get
info
from
them.
They're
great,
but
even
I,
run
into
problems.
A
There
was
something
I
was
trying
to
do
with
pull
request
code
reviews
last
week
and
my
app
was
just
giving
me
unauthenticated
can't
make
this
change
after
talking
to
them.
It
was
clear,
I
just
wasn't,
including
the
right
permission
in
my
app,
so
go
ahead
and
do
that.
So,
if
those
are
the
gotchas,
let's
talk
about
some
best
practices
for
actually
building
apps
with
robot.
First,
how
you
split
up
configurations,
there's
three
distinct
ways
or
places
you
can
put
configurations
for
your
pro
bot
app
one
of
them
is
where
the
user
can
get
to
it.
A
We
saw
earlier
with
the
autoresponder
app
it
read
a
configuration
file
out
of
the
repo
that
autoresponder
was
installed
on
two
things
that
you
want
your
user
to
change.
You
want
your
user
to
customize.
You
want
your
user
to
manage,
make
them
readable
through
that
user.
Configuration
we've
actually
made
this
simpler
within
Pro
bot,
we've
added
a
helper
method,
config,
which
will
read
config
files
out
of
the
dot
github
directory
and
make
them
available
to
your
Probot
app.
A
So
again,
the
syntactic
sugar
that
Probot
allows
to
make
this
easier,
app
configuration
anything
that
you
want
to
just
configure
in
your
app
itself,
go
ahead
and
build
it
out
in
the
actual
code
why
this
is
important
to
build
it
in
config
files,
of
course,
rather
than
just
hard
code,
it
we
mentioned
that
you
do
app
a
little
while
ago
right
now
it
opens
issues.
Maybe
you
want
it
in
your
workflow
to
open
pull
requests,
that's
a
great
configuration
to
put
at
the
app
level.
So
when
you
deploy
this,
you
can
set
it.
A
However,
you
want
to
set
it
and
finally
defaults,
whether
you're
setting
things
up
for
user
configuration
or
app
configuration
use,
sensible
defaults
in
a
lot
of
ways.
These
configuration
files
are
the
guidance
to
everyone
using
your
app
or
building
on
top
of
your
app
of
what
you
expect
to
have
happen.
So
by
putting
in
sensible
defaults,
you
can
help
guide
them
in
creating
their
own
tools.
A
A
Rational
and
non
rational
database
back-end
to
Probot
for
the
most
part,
apps,
are
built
and
designed
to
run
stateless.
So
what
that
means
is
when
you,
when
you,
when
you
pull
up
your
app
when
your
app
first
loads,
it
should
be
able
to
log
into
the
github
repository
and
figure
out
the
state
of.
What's
going
on
like
the
reminders
app,
for
example,
it
should
search
through
all
of
the
issues
and
find
what
issues
it
currently
needs
to
be.
A
Managing
reminders
for
this
shouldn't
be
something
it
has
to
manage
in
a
back-end
data
store
or
something
of
that
nature.
This
gets
made
easier
a
little
bit
by
the
extensions
of
made
available
to
Probot,
so
like
any
good
modular
system
build
as
much
stuff
as
we
can
into
pro
bot
core,
but
then
make
it
extensible
provide
the
hooks
and
configurations
so
that
it
can
grow
and
provide
new
functionality
over
time.
One
of
those
extensions
is
metadata.
What
metadata
actually
does
it
lets?
You
store
data
configuration
information
inside
of
github
issues.
A
It
takes
advantage
that
get
up
issues
themselves
or
HTML
text.
So
whatever
we
render
inside
of
an
HTML
comment
doesn't
actually
appear
on
the
screen
to
the
user,
but
we
can
store
data
inside
that
HTML
comment
tag
and
then
use
that
to
manage
the
state
of
the
app
so
again
on
this
reminders
app.
We
just
talked
that
we've
been
talking
about
what
it
actually
does.
Is
it
stores
on
that
on
that
parent
issue,
when
the
reminders
should
pop
in
JavaScript
date
format
it
stores
what
user
it
should
actually
respond
to
once
that
reminder
pops.
A
So
when
it,
when
it
does
recover
its
state,
it
doesn't
have
to
parse
every
comment.
It
can
just
go
into
the
parent
comment
and
read
that
data
section,
so
the
metadata
plug-in
is
one
that
sort
of
simplified,
both
the
reading,
the
the
writing
and
the
reading
of
this
data.
Other
things
our
scheduler,
so
maybe
you're,
not
one
or
maybe
you
have
actions
that
are
not
triggered
by
a
web
hook.
You
want
to
run
every
day
every
hour
every
week
against
Dale
is
a
good
example.
It's
running
on
a
daily
or
weekly
basis.
A
It
abstract
all
the
key
pieces
for
that,
so
you
can
easily
build
commands
of
your
own,
maybe
my
favorite
and
something
that's
a
relatively
new
feature
to
Probot,
but
I've
use
credit
sencilla
is
test-driven
development,
so
of
course
everyone
loves
test-driven
development
until
they
have
to
do
it
and
then
they
kind
of
don't
really
do
it,
but
to
kind
of
write
your
test
beforehand
and
build
your
functionality
to
it.
So
this
is
an
example
of
what
a
test
looks
like
in
pro.
But
right
now
we
use
a
test
framework.
A
You
can
easily
say
what
this
type,
what
we're
testing!
I
used
custom
comments
because
I
wanted
to
test
a
lot
of
different
functionality,
so
I
had
previously
in
this
test,
read
the
big
jason
packet,
basically
of
a
web
hook
of
something
that
it
sent
to
my
app
at
one
point
and
then
programmatically.
I
change
different
different
variables.
In
this
case.
I
change
the
comment
itself
to
say:
no
action
required
I
can
then
trigger
Probot
to
receive
this
event
as
if
it
came
in
over
the
web,
that's
robot
receive
and
then
I
can
expect
things.
A
I
can
make
call
functions
with
my
app
to
make
sure
that
certain
things
happened
as
we
expected
them
to
so
again.
I
expect
a
get
up,
API
to
be
called
I,
expect
them
to
actually
reach
out
and
try
to
read
a
file
off
the
file
system
and
I
expected
them
to
read
the
pro
bot
news.
Yamo
configuration
file
so
I
not
only
mocked
the
response
of
that
file.
I
was
able
to
expect
and
require
that
it
get
called
with
those
proper
parameters.
Those
parameters,
of
course,
were
read
from
that
original
comment.
A
Payload
I
read
the
repo
I
read
the
owner
from
it.
So
this
was
a
way
I
could
exercise
my
app
where
I
use
this
more
recently
as
I
was
building
this
Probot
OpenShift
integration,
but
this
does
is
whenever
a
PR
gets
opened
in
github,
it
went
ahead
and
created
the
kubernetes
based
infrastructure
for
a
whole
new
environment
to
test
that
PR
independently,
so
PR
got
opened.
It
went
ahead
and
spun
off
a
bunch
of
read
the
configuration
files
because
they
were
doing
infrastructure
as
code
within
the
repositories
and
spun
up
those
containers
within
OpenShift.
A
Well,
this
isn't
something
I
wanted
to
test
all
the
time
and,
quite
frankly,
I
knew
that
my
pull
request
was
just
gonna,
be
pull
request
out,
open
I,
don't
even
care
what
the
contents
of
it
was.
So
I
use
test-driven
development
just
to
kick
off
this
flow
over
and
over
and
over
again,
as
I
worked
on
debugging
and
getting
the
right
syntax
of
working
with
openshift.
This,
let
me
take
the
github
piece
out
of
out
of
the
picture.
Maybe
this
is
more
sensitive
to
me
as
I.
A
Remember
the
early
days
of
pro
bot
when
I
was
testing
an
app
like
this
I
was
literally
opening.
Hundreds
of
comments,
testing
testing
again,
why
am
I
not
receiving
the
webhook?
Why
am
I
still
not
receiving
the
webhook
okay?
This
should
work.
Why
am
I
still
not
receiving
the
webhook
by
now,
using
the
test
framework
I'm
able
to
automat
all
of
that
interaction?
A
Also,
you
see
at
the
bottom,
some
water
test-driven
design,
but
one
of
the
things
we
like
to
suggest
is:
you
should
include
dry,
run
functionality
within
your
app
as
well,
especially
when
you're
doing
things
like
writing
comments
or
changing
files
on
the
gonna
get
up
file
system
or
within
a
repository
as
an
organization.
You
want
to
know
what
this
is
going
to
do
before
you
turn
it
on.
A
For
the
first
time,
we
have
a
lot
of
open
source
organizations
who
have
turned
on
stale,
because
it's
said
great,
we
want
to
use
this
to
help
manage
or
comments
and
our
interaction
with
the
community
without
thinking
well,
I've
been
an
open
source
project
for
four
and
a
half
years.
This
is
going
to
immediately
comment
on
900,
open
issues
and
close
them
all
out,
maybe
understanding
being
able
to
run
that
as
a
dry
run
functionality.
So
you
can
understand
okay,
this
is
what
I'm
about
to
comment
on.
A
This
is
what
it's
going
to
say
and
have
that
confidence
before
it
goes
and
in
bulk
changes.
Your
entire
repository
is
definitely
a
best
practice
and
finally,
issue
management.
So
there's
a
couple
of
different
things
that
fall
under
issue
management.
So,
as
I
mentioned
earlier
things
with
stateless,
these
are
sort
of
best
practices
for
pulling
back
information
on
issues
again.
I
prefer
to
use
labels
when
finding
issues
or
data
that
belongs
to
Probot.
So
for
reminder,
let's
say,
add
a
label
to
that
issue
called
reminder
that
way.
A
A
Well,
yes,
you
wrote
a
parser
to
read
that
comment
and
to
parse
out
the
information
you
could
do
that
parsing
again,
but
it's
expensive
right
go
ahead
and
store
that
data
in
in
as
metadata
one
of
the
nice
advantages
of
that
when
you
use
the
get
up
API
and
you
pull
back
all
of
your
issues.
One
of
the
things
that
comes
back
is
that
first
comment.
A
A
So
when
you,
when
I,
went
to
using
metadata
from
my
old
old
process,
I
went
from
making
hundreds
of
rest
calls
into
my
into
my
repository
when
starting
up
an
app
so
just
making
one
because
now
I
can
get
all
the
information
I
need
from
that
initial
list.
All
issues
call
which
is
a
good
point
at
the
bottom
understand
when
you
can
use
the
Search
API
and
the
different
modifiers
and
accessors
it
gives
you
and
when
you
can
use
things
like
get
all
or
list
all
four
issues
and
and
pull
requests.
A
They
operate
a
little
bit
differently.
They
give
you
a
little
bit
different
data
back
back
out.
Some
of
them
are
better
for
different
situations,
so
just
do
little
bit
of
reading
yourself
as
to
what
one
makes
sense
for
your
own
use
case,
but
keep
in
mind.
There
are
two
different
options
to
pull
back
all
of
the
data
and
finally,
as
I
mentioned,
pagination
has
been
added
into
Probot,
which
isn't
in
the
actual
node
J
S
or
node
github
SDK
itself.
A
So
when
you're
dealing
through
issues
with
with
a
lot
of
comments,
currently
I
think
the
library
defaults
to
100
comments
per
page
before
you
have
to
page
over,
keep
in
mind
that
pagination
is
available
and
as
your
friend,
it
makes
it
much
easier
than
doing
it
on
the
side.
So
at
this
point
you've
seen
the
basics
of
Probot.
Hopefully,
you
understand
why
it's
so
important
and
why
it's
so
great
and
why
it
answers
all
of
these
questions
of
building
apps
for
your
own
specific
workflows,
it's
open
source.
A
A
When
you
go
to
github,
slash,
Probot,
slash,
Probot
you'll,
see
their
names
and
faces
and
work
all
over
the
not
only
the
Corp
robot,
but
a
lot
of
the
different
plot,
apps
extensions
and
things
around,
but
there's
a
bunch
of
other
people
who
have
helped
that
as
well.
Some
of
these
are
from
github.
Some
of
these
are
from
the
community
I
think
currently
Probot
pro
bot
has
over
27
contributors.
A
I'll
be
around
for
QA
I,
have
stickers
and
magnets
if
anyone's
interested,
but
also
want
to
give
a
quick
point
out
of
where
you
can
interact
and
find
more
information
about
Probot
right.
So,
of
course,
github
comm
/
pro
bot
is
the
organization
where
all
of
this
libs
there's
actually
a
friction
repository
within
that.
A
There's
a
slack
team,
Probot,
talk.com
and,
of
course,
Probot
like
any
good
robots
on
twitter
pro
bot,
the
robot
will
be
happy
to
tweet
back
at
you
again,
I'm
Jamie.
You
can
find
me
on
the
social
medias
or
JV
Jen
senior
at
github,
comm
I,
look
forward
to
talking
to
you
more.
Thank
you
all
for
your
time.
Today.