►
From YouTube: Demo Days - How to build a business on GitHub
Description
Learn how to build a business on GitHub by utilizing our powerful ecosystem and global community. Thomas Hughes, Sr. DevOps Engineer, will walk you through the process, from ideation to integration, including thinking about social media as more than just a promotional medium. What can we learn from the successes of Pull Panda, Dependabot and Semmle?
Are you building a business that could be unlocked with GitHub? Contact us: https://github.co/twitch-contact-sales
A
Hello:
everyone,
my
name
is
thomas
hughes,
I'm
a
senior
devops
engineer
over
at
github.
So
thanks
everyone
for
coming
in
and
joining
just
watching
the
chat
here
I
saw
some
questions
coming
in
already
and
we
have
aj
in
the
chat
and
I
believe
liz
is
there
as
well
to
help
out
from
the
github
side
today
we're
talking
about
how
to
build
a
business
on
github.
So
yeah.
Thanks
for
the
nice
background
comments,
I
appreciate
it.
Yeah
our
marketing
team
is,
is
pretty
awesome,
so
zoom
virtual
backgrounds.
A
We
got
some
animated
ones
too
yeah,
so
today
we're
talking
about
how
to
build
a
business
on
github.
Basically,
I
wanted
to
cover
just
this
idea
of
you
know:
there's
this
huge
open
source
community
out
there
and
while
some
people
don't
like
to
talk
about
monetizing
different
aspects
of
it.
A
Obviously,
you
know
we
need
to
pay
our
bills
and
there's
there's
things
that
you
can
do
to
to
be
your
own
business
owner
and
you
know,
write
your
own
software,
so
we're
going
to
cover
a
few
different
areas
today
I'll
go
ahead
and
share
out
my
screen
now
and
I
have
a
short
little
slide
deck.
I
promise
it's
very
short
and
I'll
introduce
myself
at
the
same
time
here.
A
So
this
is
me
if
you
aren't
able
to
see
me
on
camera.
Necessarily
again,
I
am
huge
with
my
handle
at
github
thomas
used,
my
name
been
at
github
now
for
two
and
a
half
years,
almost
to
the
day.
Actually
I
started
off
on
our
professional
services
team,
so
I
reach
out
to
our
enterprise
customers
do
anything
from
trainings
to
devop
pipelines,
to
sys
admin,
work
and
admin,
automation,
there's
kind
of
a
whole
bag
of
tricks
that
we
we
get
ourselves
into.
A
I
moved
over
to
our
partner
engineering
team
for
a
while,
which
was
part
of
our
ecosystem
and
building
out
integrations
with
third
parties,
whether
it's
you
know
big
parties
like
google,
amazon
or
circle,
ci
travis,
and
then
also
the
smaller
ones
like
pullpanda,
who
we
want
up
acquiring
later.
So
we
do
a
lot
of
discussion
between
large
enterprises,
both
on
the
the
end
user
front
and
then
also
on
the
integration
front.
A
So
I
think
I
got
a
little
bit
of
a
background
in
in
all
those
areas
here
and
I
want
to
share
some
tips
out
there
that
I've
learned
over
the
over
the
couple
years
here
now,
I'm
a
devops
engineer,
as
I
mentioned,
with
the
professional
services
team,
so
I
work
on
some
of
our
open
source
projects.
I
work
with
our
enterprise
clients
to
help
them
with
automation,
tests
and
things
like
that
and
and
do
a
little
bit
of
everything.
So
it's
pretty
fun.
I
enjoy
it.
A
A
I
want
to
talk
just
briefly
about
you,
know,
kind
of
coming
up
with
an
idea
and
some
best
practices
around
that
how
you
can
get
your
user
base,
actually
building
the
integration
itself
and
then
some
common
pain
points
that
are
associated
there
too.
A
You
know
one
of
the
things
that
I
think
is
we've
covered
in
these
demo
days
here
if
you've
seen
some
of
the
other
ones,
things
like
github
actions
and
ci
cd
and
github
packages
and
all
these
great
pieces
of
the
ecosystem,
and
I
kind
of
wanted
to
talk
about
it
now,
on
the
business
side
of
things
and
how
you
know
you
can
really
build
something:
pretty
cool
with
their
platform.
A
So
let's
go
ahead
and
get
started
then
so
why
github?
So
I
probably
don't
have
to
tell
you
this
if
you're
here,
but
github
is
like
the
place
to
build
software
on
the
internet
right.
We
have
this
thing
called
the
state
of
the
octoverse
report.
A
You
can
google,
it
or
maybe
aj
or
liz
can
drop
it
in
chat
for
me
every
year
we
do
this,
the
state
of
our
octavers
or
you
know,
basically
our
ecosystem,
and
we
have
all
these
fun
numbers
on
there
really
cool
statistics
about
developing
countries
and
where
codes
being
contributed
from
user
base,
increases
enterprises
adopting
the
platform,
all
those
fun
things.
So
I
pulled
out
some
of
the
numbers
here,
so
this
is
for
2018
to
2019.
Our
our
new
report
should
be
out.
A
I
think
I
think
we
do
it
in
october,
every
year,
so
possibly
next
month,
we'll
have
the
2019
to
2020
numbers,
but
as
of
right
now,
though,
you
know
2018
to
2019
10
million
new
developers
created
accounts
on
github,
which
is
just
crazy.
I
mean
to
me,
I
think,
that
that's
pretty
insane
and
that
totaled
up
to
40
million
developers
as
of
2019
when
this
report
came
out
and
I've
heard
that
we've
added
around
10
million
more
so
far
this
year.
A
So
I
mean
it's
just
an
insane
amount
of
growth
and
you
know
definitely
pretty
crazy
to
to
be
part
of
github
both
before
microsoft.
After
the
acquisition,
all
that
fun
stuff,
so
we've
we've
grown
so
much.
I
won't
go
through
all
the
numbers
here.
A
Just
to
you
know
not
bore
you
from
from
reading
the
slides
themselves,
but
the
point
is:
is
that
github's
growing
like
crazy
and
it's
not
slowing
down
our
rate
of
our
rate
of
growth
is
increasing
even
more
so
as
you
build
software,
that's
supposed
to
work
with
other
platforms,
github's,
really
where
you
want
to
look
at
as
far
as
the
community
itself.
The
communities
here,
another
cool
call-out
that
I
wanted
to
make
is
the
amount
of
students
that
use
github.
A
So
if
anyone's
in
college-
or
you
know,
graduated
recently-
you
probably
know
this,
but
over
20
000
schools
use
github
in
their
curriculum
and
quite
a
few
of
those
are
through
github
education.
There's
things
like
the
student
developer
pack
and
you
know
a
lot
of
freebies
available
for
for
students
with
edu's,
but
you
know
with
that
being
said.
That
means
that
you
know
in
2018
and
2019,
1.7
million
students
learn
to
code
on
github
right,
and
I
mean
I'm
seeing
it.
Personally.
A
I
have
a
niece
and
nephew
that
are
five
and
seven
and
I
think
my
seven-year-old
nephew
was
telling
me
that
he
actually
did
something
on
github
in
his
class.
It's
like
a
super
basic.
It
might
have
been
scratch,
but
it
was
like
a
super
basic
thing.
I
can't
believe
they're
starting
that
young,
so
you
know
definitely
a
lot
of
opportunities
out
there.
It's
not
going
anywhere
anytime
soon.
So
this
is
all
just
to
say
that
our
community
is
huge
and
you
know
really.
A
This
is
where
you
get
your
your
reach
at.
So
thank
you
for
the
leak
to
the
education
pack.
There
I
appreciate
it
and
there
was
also
an
ask
aj
for
the
state
of
the
october,
so
you
got
that
too
cool
yeah
and
someone
mentioned
we,
we
copy
our
homework
off
github.
So
that's
also
totally
a
thing
that
I've
seen
before
so
no
comment
on.
A
If
I've
done
that
or
not
but
hey
that's
what
open
source
is
about
right
and
we
use
stack
overflow
for
our
questions
and
that's
that's
half
of
my
job
developing
so
yeah.
So
let's
go
ahead
and
move
forward
a
little
bit
here.
So,
if
I'm
talking
about
why
github
again
so
we've
talked
about
the
users,
we
all
know
the
community's
there.
We
have
a
backing
there,
but
we
also
have
a
really
robust
ecosystem.
That's
continuing
to
grow!
You've,
probably
heard
of
some
of
the
announcements
of
different
acquisitions.
A
We've
done
in
the
past,
I'm
going
to
talk
about
a
couple
of
them
just
to
mention
them,
since
I
kind
of
consider
them
success
stories
in
a
sense.
But
really
a
lot
of
this
is
through
just
a
really
robust
rest
api,
so
that's
kind
of
like
the
core
of
our
our
development.
In
my
opinion,
I
usually
tell
people
that
anything
you
can
do
through
the
ui
on
github,
with
a
few
caveats
can
be
done
in
the
rest
api.
A
So
it's
pretty
crazy.
You
know
anything
from
like
merging
pull
requests
to
committing
code
back
to
writing
comments
on
issues
to
you
know
getting
information
about
users,
getting
audit
reports
like
there's
so
much
you
can
do
through
it
and
so
many
different
options
out
there
that
I
really
think
that
it's
one
of
the
more
impressive
parts
for
me
at
least
with
github,
is
how
robust
that
api
is.
You
know
with
that.
We
do
have
a
graphql
api
as
well,
and
it
seems
like
people
aren't
as
familiar
with
graphql,
but
it's
really
efficient.
A
It's
a
query
language!
That's
what
the
ql
stands
for,
and
it
basically
allows
you
to
like
navigate
this
crazy
network
of
objects
in
the
github
database.
That
lets
you
get
exactly
what
you
need.
So
one
of
the
problems
with
rest
that
people
complain
about.
Is
you
get
this
giant
json
payload
and
you
don't
know
how
to
parse
through
everything
and
or
you
you
don't
want
to
parse
everything.
It's
just
a
lot
of
data
that
you
don't
need
for.
You
know
getting
this
single
thing
like
a
repository
name
so
with
graphql.
A
You
can
actually
filter
it
down
to
where
you
just
return.
The
repository
name
as
an
example
for
that
type
of
call,
so
it's
it's
pretty
cool.
I
use
it
in
conjunction
with
a
lot
of
other
scripts
and
everything
too,
and
especially
when
I'm
working
with
our
large
enterprises
and
we
want
to
reduce
the
amount
of
traffic
on
the
network
and
you
know,
reduce
the
amount
of
api
calls
and
everything.
So
I
wanted
to
point
that
out.
A
You
know
outside
of
the
apis,
though
we
also
have
a
pretty
robust,
app
ecosystem,
so
I
put
sas,
but
I
guess
this
could
be.
You
know
other
as
a
service
type
platforms,
but
we
have
both
github
and
oauth.
Apps
oauth's
been
around
for
quite
a
while
github
apps
are
around
for
a
while.
If
you've
heard
of
github
actions,
we
actually
github
actions
is
actually
a
github
app
in
the
background,
just
fun
fact
there.
So
it's
a
it's
an
app
that's
by
default,
installed
on
everyone's
github.com
accounts,
so
it's
pretty
cool.
A
You
know
we
got
quite
a
few
ways
to
integrate.
Of
course,
you've
probably
seen
some
information
about
github
actions.
Like
I
just
mentioned,
it's
kind
of
the
serverless
idea
where
you
know
we
can
respond
to
specific
events
and
then
take
action
on
github
or
through
third-party
apis
from
there,
which
is
pretty
cool.
There
are
some
questions
about
graphql
too.
A
So,
basically,
we
were
working
to
make
everything
in
rest
available
in
graphql,
but
there's
some
things
that
just
don't
work
well
in
a
graphql
sense
and
personally,
I
think,
there's
some
things
that
don't
work
well
in
rest
sense.
So
there's
a
few
things
like
the
audit
log
for
enterprise
cloud
organizations,
that's
available
through
get
our
graphql,
but
it's
not
available
through
rest.
A
It's
a
little
bit
too
much
data
if
we
just
try
to
return
everything
in
rest
and
then
there's
some
other
like
interesting
little
put
and
post
commands
as
far
as
making
edits
on
github
that
will
go
from
there
so
yeah.
Absolutely
so,
let's
see
I'm
gonna
go
ahead
and
take
another
question
here.
So
are
we
adding
additional
tin
spin
apps?
Are
we
adding
additional
optional
vat
to
the
sponsor
system,
making
it
possible
for
a
subscription
system
out
of
it?
That
is
a
good
question.
A
I
don't
know
if
aj
or
liz
can
look
that
up.
I
don't
know
off
the
top
of
my
head,
unfortunately,
but
let's
see
okay
yeah
yeah,
so
I
know
there's
been
some
discussion
about
github
labs
as
well
and
get
classroom
and
everything
too
yeah
we're
definitely
working
to
get
more
educators
using
git
classroom.
It's
a
probably
could
be
its
own
whole
talk
at
this
point,
but
github
education
program
is
really
cool.
A
In
my
opinion,
universities
get
to
use
github
enterprise
on-premises
that
you
get
to
turn
in
your
homework
that
way
and
how
professors
are
starting
to
use
github
actions
to
like
auto-grade
homework,
it's
kind
of
crazy,
so
yeah.
So
there
we
go
working
on
all
of
that,
though.
Let's
keep
talking
about
some
of
these
other
areas
here.
So
another
really
cool
thing
about
github.
In
my
opinion,
is
we
have
so
much
support
for
both
official
and
third-party
libraries
that
wrap
our
api
and
make
all
of
this
a
lot
easier.
A
So
I'm
going
to
talk
about
those
a
little
bit
later
too
and
then
finally,
you
know
the
last
thing
is
I'd,
be
remiss
if
I
didn't
mention
our
github
marketplace
and
some
people
really
like
it.
I
I
personally
think
we
can
do
some
improvements
still
there
and
I
hope
we
we
continue
to.
But
the
github
marketplace
is
like
a
public
listing,
that's
free
to
list
your
app
in
and
you
can
list
your
apps.
You
can
list
your
actions,
it's
through
the
app
process.
A
It's
like
you
know
two
or
three
clicks
to
install
an
application
off
the
marketplace.
There
is
some
payment
support
in
the
back
end
for
people
that
are
charging
subscriptions
for
various
reasons
on
their
apps
and
all
of
that
stuff.
So
it's
kind
of
cool.
So
I
want
to
make
sure
I
call
that
out
as
well
and
we'll
take
a
brief
look
at
that
a
little
bit
later
here,
too
so
cool
okay.
A
So,
let's
talk
about
like
all
right,
I
want
to
build
this
business
on
github.
I
want
to
form
some
type
of
idea
and
I
want
to
figure
out.
You
know
how
can
I
be
the
next
pull
panda,
for
example,
or
something
like
that,
so
some
of
these
things
that
I
I'm
talking
about,
I
actually
got
this
by
interviewing
pullpanda,
semel
and
dependabot
employees
to
talk
about.
A
You
know
like
hey,
like
what
were
some
of
your
early
pain
points
as
she
started
building
these
integrations
for
github,
and
I
wanted
to
share
some
of
that
stuff
too.
So
you
know
uniformly
between
all
of
them.
They
said
the
biggest
thing
for
them
was
solving
a
real
pain
point.
That's
in
the
community.
A
Everyone
can
create
a
great
project
on
mostly
anyone
can
create
a
great
product
and
great
software
out
there.
But
you
know,
if
you
don't,
have
the
community
backing
you
don't
have
a
user
base,
then
you
don't
have
anyone
to
like
sell
your
product
to
or
using
it.
You
don't
get
any
of
that
feedback.
So
solving
real
pain
points
is
really
like
the
key
to
success
here.
A
Doing
that
you
know
that
basically
allows
you
to
to
reach
out
to
those
customers.
So
let's
say
that
you're
following
a
hashtag
or
you're
following
github's
twitter
account,
and
you
see
a
bunch
of
people
complaining
about
like
oh
you
know.
I
really
wish
projects
was
more
robust,
like
I
don't
mind
using
other
systems,
but
jira
is
too
heavy
or
you
know
whatever
system
you're
using
and
issues
and
projects
just
don't
give
enough.
A
Well
now
we
know
that
hey,
there's
a
community
pain
point
out
there
and
we
can
reach
out
to
those
individuals
when
we
start
writing
our
product
and
get
some
validity
with
them
say:
hey
you
know.
Is
this
the
type
of
thing
that
would
help
you
and
your
company
some
of
those
people
that
that
put
out
these
pain
points
like
this.
You
know
they
actually
have
some
weight
within
the
company
that
they're
in
and
they
might
be
able
to
test
out
new
tools.
A
So
I
think
it's
a
good
way
to
again
gain
that
validity
from
the
community
itself
and
before
you
invest
too
much
into
your
own
idea.
You
know
you
kind
of
get
a
few
people
testing
it
out
already
too,
and
seeing
like,
is
this
a
practical
use
case?
Is
this
an
actual
solution
to
your
pain
point
all
of
that
fun
stuff?
A
So
you
know
another
thing
that
they
all
said
is
keeping
things
simple
and
doing
one
thing
really
well
before
expanding
into
too
many
other
areas,
and
I
think
this
applies
to
like
any
business
that
you're,
probably
gonna,
create
you
know,
and
it's
a
typical
like
programming
thing
too
right
is
to
keep
things
simple
separation
of
concerns
and
all
that
fun
stuff.
A
But
we
want
to
keep
things
simple
in
the
sense
of
I'm
going
to
keep
going
back
to
pole,
panda
panda's
original
app
was
called
pull
reminders
and
all
it
did
was
it
would
give
you
a
notification
slack
when
you
had
a
pull
request
that
was
going
stale.
Basically,
that
needed
to
be
reviewed-
and
you
know,
didn't-
have
a
review
on
it,
but
the
review
was
requested
a
week
ago.
So,
let's
ping
the
team
in
their
slack
channel.
A
Just
let
them
know
really
simple,
but
it
was
a
legitimate
community
pain
point
and
that
simple
product
wound
up
becoming
one
of
the
most
popular
apps
on
the
github
marketplace
and,
of
course,
led
to
eventually
being
acquired
by
github.
Now
it's
integrated
into
our
official
slack
app
and
all
that
fun
stuff,
but
they
started
with
just
such
a
simple
thing.
So
you
know
it's
it's
something
that
is
interesting
like
that.
You
can
make
a
very
complex
system,
but
sometimes
the
simple
solutions
is
so
much
better.
A
So
another
thing
that
they
all
said
is
to
get
that
feedback
as
early
as
possible.
A
I
kind
of
alluded
to
this
earlier,
but
you
know
when
you're
looking
at
investing
yourself
and
your
time
into
software,
so
many
of
us
have
probably
gone
down
that
route,
where
we've
continued
to
build
out
like
this
huge
product,
but
no
one
ever
actually
tested
as
an
end
user,
like
you
know
your
product
because
you're
the
one
building
it,
but
then,
when
a
user
finally
does
it
things,
maybe
just
don't
make
sense
and
they
tell
you
like
wait
a
second.
A
What
is
this
like
this
and
you
end
up
kind
of
backing
out
of
everything,
and
really
they
all
said
that
you
know
getting
that
feedback
early
on
was
key
for
pull
panda.
Specifically
they
mentioned
like
they.
They
gave
out
some
free
licenses
to
people
in
the
community
that
you
know
had
larger
user
bases
and
they
really
wanted
to
get
their
product
in
use.
A
So
yeah
there's
a
pain
point
being
said
right
here,
so
we
currently
have
a
pain
point
tracking,
the
npm
private
dependencies
for
an
enterprise
organization.
We
don't
have
accurate
data
on
the
dependency
graph.
It's
something
about
our
configuration
or
the
private
dependencies
aren't
tracked
so
yeah
there
you
go,
there's
there's
a
dependency
management
area
that
github
itself
is
trying
to
solve.
Right
now,
right
we've
been
doing
dependency
insights.
I
think
there
was
a,
I
think,
there's
a
demo
on
that
recently.
A
Actually,
so
you
know
we
are
increasing
our
own
posture
in
our
own
ecosystem,
but
there's
absolutely
room,
I
think,
for
third
parties
to
be
able
to
contribute-
and
that's
again
it
just
goes
into
like
our
api
and
our
partnerships
and
all
of
that
fun
stuff.
A
So,
as
far
as
like,
specifically
for
the
question
of,
if
private
dependencies
are
tracked
or
not,
hopefully,
aj
or
liz
can
maybe
check
with
our
packages
team
on
that,
and
especially
on
the
npm
side,
since
we
did
do
the
npm
acquisition
recently
as
well,
I
don't
have
it
off
the
top
of
my
head.
I
apologize.
A
So
cool,
okay,
yeah
just
checking
chat
too.
I
got
it
up
on
my
other
screen.
So
all
in
all
the
the
idea
here
is
that
we
want
to
keep
things
simple.
We
don't
want
to
over,
invest
ourselves,
whether
it's
time
or
money
as
well
into
a
product
that
maybe
isn't
actually
going
to
be
used
and
again.
I
think
this
is
true
for
for
any
business
or
any
product
you're
going
to
create
where
you
know
you
can
have
the
best
product
ever,
but
if
you
don't
have
a
user
base,
it
kind
of
doesn't
matter.
A
A
So
the
biggest
thing
that
I
heard
from
like
the
pole,
panda
team,
which,
by
the
way,
if
you
haven't,
heard
the
story,
it
was
pretty
much
one
developer.
I
think
all
the
way
up
till
near
the
end
of
poll
panda
when
they
were
finally
acquired
by
us.
So
what
they
did
is
they
watch
twitter
feeds.
They
watch
things
like
the
github.
You
know
handle
on
twitter
and
people
writing
to
github.
They
watch
the
community
forums.
A
Github
has
an
official
communities
forums
that
maybe
aj
can
drop
in
the
chat
for
us
here.
That'd
be
great,
there's
a
github
subreddit
if
you're
into
reddit
as
well.
I
don't
know
how
much
we
monitor
that
necessarily
as
github,
but
there's
a
lot
of
chatter
there
all
the
time
and
then,
of
course,
there's
all
the
things
like
you
know.
A
You
see
stack
overflow
stuff,
you
see
just
chat,
probably
within
your
own
company,
whether
it's
slack
or
teams,
or
you
know
anything
like
that,
but
the
social
media
part
of
it
is
your
user
base
right.
Those
are
the
end
users
that
are
like.
Oh,
I
just
wish
that
I
could
do
xyz
on
github
and
you
know
it's
it's
kind
of
a
pain
sometimes
to
find
that
information.
A
But
then,
once
you
start
following
like
certain
hashtags
and
things
like
that,
you
can
actually
find
some
pretty
good
ideas
and
and
then
also
reach
out
to
those
users
right.
So,
if
you've
solved
a
problem
using
my
earlier
example
of
you
know,
github
projects
isn't
super
robust
right
now.
As
an
example,
you
know
you
really
want
projects
to
do
a
little
bit
more
than
just
be
this
kind
of
like
kanban
swim,
lane
approach
type
thing.
A
So
why
don't
you
reach
out
to
the
user
when
you
build
a
better
product
for
that
or
when
you
build
an
integration,
say:
hey!
You
know
everyone!
That's
been
posting
about
this
on
this
hashtag
or
you
know
adding
github
or
whatever
it
is.
I
just
had
this
product
here,
I'm
willing
to
give
out
a
few
keys
and
let
you
try
it
get
some
feedback.
All
of
that
fun,
stuff,
r2r
world
just
said:
79
watching
really
yeah,
there's
80
now,
so
it's
definitely
a
pretty
good
turnout.
I
appreciate
everyone
coming
out
here
yeah.
A
So
all
of
this
is
just
to
say
that,
like
the
community's
there
on
github,
of
course
like
we
talked
about-
and
this
is
how
you
can
reach
out
to
like
user
bases
when
you
find
your
idea
of
like
who
should
I
talk
to
and
who
should
I
like
reach
out
to
proactively
and
say
you
know:
hey
yeah,
I
just
solved
your
pain
point
that
you
talked
about
for
a
while.
I
was
wondering
if
you
wanted
to
get
a
quick
demo
or,
like
here's,
a
youtube
video
that
shows
you
what
my
product
does.
A
Would
that
solve
your
pain
point
and
you
start
getting
user
adoption
that
way,
pretty
naturally
and
organically,
which
is
pretty
cool,
pull
panda.
Specifically
again,
they
grew
to
be
the
number
one
third-party
app
on
the
github
marketplace
and
I
believe
he
said
they
didn't
do
any
actual
marketing
at
all.
It
was
all
just
I
mean
no
like
paid
marketing.
I
should
say
I
would
imagine
that
social
media
posts
are
is
considered
marketing,
but
it's
just
pretty
crazy.
A
I
think
I
talked
about
that
one
enough,
so
I'll
go
ahead
and
move
on
to
the
next
step
here:
okay,
yeah.
So
basically
I
wanted
to
talk
about
like
how
do
we
build
this
integration
itself
and
just
kind
of
talk
high
level
about
some
of
these
things?
I
know
there's
been
other
demo
days
about
actions
and
apps
and
all
that
fun
stuff,
but
I
wanted
to
talk
at
least
some
high
level
and
then
show
you
where
you
would
actually
go
to
build
a
github
app
itself
too.
A
So
you
know
we
have
a
few
options
out
there.
Github
actions
is
the
new
thing
that
everyone's
loving
right
now,
it's
not
a
replacement
for
github
apps.
Necessarily.
However,
a
lot
of
things
that
were
github
apps
are
being
transitioned
to
github
actions.
Github
actions
is
a
serverless
model,
basically
response
to
webhook
events
on
github,
and
that
could
be
something
like
a
push
to
maine
or
to
a
development
branch.
It
could
be
a
comment
on
an
issue.
It
could
be
a
pull
request
that
got
reviewed.
A
It
could
be
that
someone
was
added
to
your
repository
as
an
outside
collaborator,
and
you
want
to
take
an
action
based
on
that.
It
could
be
that
we
just
release
new
code
and
I
want
to
call
the
domino's
api
and
order
a
pizza
right.
So
it's
pretty
cool
with
the
amount
of
stuff
that
you
can
do
there
with
actions.
I
wrote
one
for
fun
called
giffy
generator
that
lets
you
query
giphy
by
typing.
Slash,
commands
on
issue
comments.
A
So
it'll
just
pick
like
a
random
one
out
of
the
first
10
results,
and
you
know
repost
it
back
to
your
issue.
It's
dumb.
It's
not
super
useful.
It
doesn't
solve
a
pain
point,
but
it's
a
fun
thing.
You
know
it's
fun
for
the
community,
in
my
opinion,
oauth
and
github
apps,
so
oauth
apps
are
basically
anywhere.
You
see
like
log
in
with
github,
for
example
our
graphql
explorer.
A
If
you've
gone
through
that
in
the
gui
that
has
the
login
with
github
button,
which
basically
authenticates
as
you
as
a
user,
and
then
you
can
go
ahead
and
go
through
the
the
processes
there
of
you
know
taking
action
on
that
user.
Basically
and
then
github
apps,
so
these
are
more
of
like
first
class
users
on
github.
We
we
don't
take
up
license
seats
for
the
enterprise
products.
A
Super
linter
is
a
github
action
and
that's
completely
open
source
as
well,
so
there's
use
cases
for
both
they're
both
being
used
internally
as
my
point,
and
neither
of
those
are
going
to
be
going
away
anytime
soon.
So
there's
a
quick
question
here.
So
can
I
run
a
github
action
when
a
new
member
is
added
to
an
organization
so
organization
level?
Workflows
are
something
that
we've
been
talking
about.
A
I
don't
know
if
they
I'd
have
to
double
check
if
they
came
out
yet
I
think
we
might
have
a
private
beta
for
that
going
on
right
now,
I'll
have
to
look
into
the
specifics
for
it,
but
basically
that
is
something
that
is
perfect
for
actions.
So
the
example
here
is
that
I
want
to
add
a
new
user
to
a
team
when
they're
added
to
an
organization.
A
So
we
do
have
some
of
that
stuff
already
available
in
the
sense
of
you
know
through
the
api
you
can
make
calls
like,
adding
to
teams,
of
course,
and
you
can
get
the
web
hook
event
of
a
new
member
being
added.
I
just
need
to
double
check
if
it's
organization
level
workflow
is,
is
there
which
I
can
probably
find
out
here
in
a
moment.
A
But
that
said,
that
is
a
perfect
use
case
right
there
right
so
organizations
that
want
to
manage
their
users
and
let's
say
that
they
have
a
thousand
developers
on
github
enterprise
right
and
they
don't
want
to
have
to
say
every
time
they
onboard
a
new
person.
I
add
them
to
my
org
and
then
let
me
go
ahead
and
go
in
and
okay,
I
got
to
add
them
to
this
team,
this
team,
this
team.
Okay,
now
they
left
the
company.
I
need
to
off
board
them,
so
I
got
to
remove
them
from
all
these
teams.
A
I
got
to
remove
them
from
the
org
all
that
fun
stuff,
so,
okay,
cool
yeah.
I
just
got
the
the
confirmation
there.
The
org
level
actions
are
there
so
ord
level.
Workflows
are
a
thing
which
means
we
can
respond
to
those
org
level
events.
So
when
you
add
a
new
member,
yes,
you
could
have
an
action
execute.
That
would
then
go
ahead
and
add
that
member
to
various
teams
right,
so
it's
it's
pretty
cool.
A
A
I
mentioned
these
earlier
too,
I
talked
about
octa
kit
and
probot
a
little
bit
so
octahed
itself.
We
have
three
official
libraries
and
I'll.
Do
a
brief
overview
of
those
in
a
moment,
but
we
have
a
ruby,
node
and
a
a
go.
Is
it
go?
Oh
boy,
no
c-sharp,
sorry,
ruby,
node
and
c-sharp
official
libraries
from
octa-cut
that
wrap
our
api.
A
Pro
bot
itself
is
more
of
a
framework
for
building
github
apps
specifically
and
makes
it
a
little
bit
easier
on
like
handling
web
hooks,
and
things
like
that.
You
can
get
started
really
quickly
with
that.
That's
also
a
node
app,
so
it
uses
the
node
octa
kit
and
the
underlying
code.
A
But
the
other
cool
thing
is
there's
actually
like
third-party
libraries
that
cover
just
about
every
language
you
would
ever
want.
So
I
mentioned
go.
For
example,
there's
an
optica
go,
it's
just
not
made
by
github
it's
a
community
source
one
there
might
be
hubbers
that
contribute
to
it,
but
it
is,
you
know
technically,
not
owned
by
github.
There's
a
couple
python
ones
out
there.
Now,
for
example,
too
I've
seen
even
like
a
shell
wrapper
that
you
could
use.
A
So
if
you
wanted
to
make
api
calls
from
the
shell
now
we
have
github
command
line
coming
out,
and
everything
like
that.
Might
that
might
not
be
as
needed,
but
it's
just
the
point
is:
is
that
the
community
supports
the
ecosystem
in
the
api
and
for
any
language
that
you
probably
gonna
write.
Something
in
you
have
a
framework
for
which
is
pretty
cool.
A
A
A
Cool,
okay,
hey
marco,
so
let's
see
oh
and
corey
too
wow.
We
got
everyone
here.
So
this
is
a
test
organization
that
I
have
on
github.
I
wanted
to
go
ahead
and
show
where
we
would
create
a
github
app
right.
So
this
organization,
I'm
calling
it
the
bearded
tom,
my
name
is
thomas.
It
could
be.
You
know
the
poll
panda
organization
right,
the
github
organization
is
obviously
its
own
organization
as
well,
so
just
wanted
to
kind
of
call
those
out
here.
A
But
if
you
go
into
the
settings
of
an
organization
itself,
while
users
can
own
applications,
I
recommend
that
you
put
it
under
an
organization.
We
have
this
github
apps
button
down
here
in
your
developer
settings.
A
And
then
you
can
see,
I
have
a
little
test
app
here,
but
we
can
create
a
new
github
app
right
here,
which
is
pretty
cool,
so
it
does
ask
for
your
password
and
then
we
just
fill
in
some
fields,
and
I
want
to
show
the
power
of
github
apps
specifically,
and
maybe
I
can
bump
up
this
font
just
a
little
bit
too
just
to
be
safe,
but
here's
a
few
test
apps
here.
So
I'm
just
going
to
say
something
like
you
know:
twitch
streaming
fun
app,
because
that's
what
we're
doing
right
now.
A
You
know
maybe
a
short
description
here
too,
and
this
is
all
marked
out
supported,
so
I
can
say
something
like
twitch
streaming
fun
app
that
is
used
during
our
twitch
stream
and
I
didn't
capitalize
twitch.
My
apologies,
so
you
know
cool
things
here
right.
If
I
have
a
home
page
I
can.
I
can
put
in
the
home
page
there
that
could
be
like
where
my
app's
landing
page
is.
It
could
be
where
you
need
to
go
to
get
a
subscription
or
to
get
a
license
key.
A
A
A
few
other
options.
I
won't
go
into
all
the
depths
of
these
different
things
here.
Another
important
one
is
like
the
setup
url.
So
after
you
install
the
github
app.
This
will
allow
you
to
redirect
to
like
your
third-party
system
to
let
them
go
through
the
setup
steps
on
that
end
as
well
to
kind
of
complete
the
link
which
is
pretty
cool,
so
that's
there
and
then
web
hooks
as
well
right.
A
So
we've
talked
about
webhooks
a
few
times
here,
so
I'm
going
to
go
ahead
and
just
use
imuse.com
and
say
like
slash
events
or
something
like
that,
but
this
is
going
to
basically
allow
me
to
automatically
subscribe.
My
webhook
events,
so
it's
one
of
the
coolest
things
about
actions
in
my
opinion,
is
that,
like
these
web
hook,
events
get
fired
off
that
the
app
subscribes
to
and
the
end
user
doesn't
have
to
set
up
anything
at
all.
They
don't
have
to
set
up
any
web
hooks
or
anything
themselves.
A
They
don't
have
to
configure
like
url
parameters
to
say
you
know,
okay,
I
need
it
to
be
to
this
machine
specifically
in
aws
or
something
like
that.
Typically,
you
would
put
a
webhook
secret
as
well
to
secure
things.
A
This
is
just
a
quick
little
demo,
so
I
don't
think
I'm
gonna
worry
about
it
right
now
we
get
down
to
our
granular
permissions
now,
which
are
pretty
cool,
so
you
know
obviously
there's
things
for
actions
that
apps
can
interact
with
now,
but
one
of
the
things
we
talked
about
was
managing
teams
right.
We
had
that
question
in
chat,
so
I
need
read
and
write
access
to
administrate
the
items
on
an
organization,
basically
including
teams,
collaborators
etc.
So
if
I
was
going
to
add
members
to
teams,
this
would
be.
A
You
know
a
permission
that
I
need
you
know
and
then
maybe
I
need
a
few
other
things
like.
A
Maybe
I
need
access
to
our
github
projects
as
an
example,
but
I
only
need
read
access,
so
I'm
just
going
to
ask
for
that,
and
then
you
can
even
get
down
to
single
file
access
where
you
can
type
in
a
file
pass.
So
this
could
be
like
your
config.yml
right
and
I
don't
need
any
access
to
your
code
at
all,
which
is
a
best
practice,
I'm
going
to
talk
about
in
a
moment.
A
I
just
need
to
access
this
one
config
file
in
your
repository
and
that's
it
so
it's
kind
of
cool
how
specific
you
can
get
with
everything,
in
my
opinion,
at
least
now,
based
on
these
permissions
that
I
selected
when
we
scroll
down
a
little
bit
further
here,
let
me
go
ahead
and,
oh
more
we're
going
to
say,
read
access
to
members
on
orgs
as
well.
A
That
should
be
maybe
read
access
on
the
admin
for
the
org.
Okay.
So,
based
on
these
permissions
that
I
selected
further
down
here,
where
we
get
to
web
hooks,
these
web
hooks
are
actually
programmatically
displayed.
Based
on
what
permissions
you
have.
So
if
you
don't
have
the
right
permission,
you
don't
get
the
web
hook
event
for
it,
which
is
pretty
cool
as
a
sanity
check,
while
you're
creating
your
app.
So,
for
example,
I
want
to
know
when
organizations
have
a
member
invited
right
or
a
member's
added.
A
That
was
the
example
we
used
in
chat
earlier.
So
that's
one
of
the
events
that
I
want
to
listen
to
and
then
maybe
this
app
is
going
to
do
something
like
verify
that
they
were
added
to
the
team
properly.
So
we'll
also
make
sure
that
the
the
team
member
editions
and
then
like
any
teams
being
created
and
stuff
like
that,
it's
gets
sent
over
just
so
we
can
log
it
still
right.
A
There's
team
membership
here
so
cool,
and
then
this
last
one's
really
important.
In
my
opinion,
since
this
is
a
test
app,
I'm
only
going
to
allow
this
to
be
on
my
own
personal
account,
which
is
my
my
bearded
tom
enterprise
account
here.
Eventually,
if
I
was
going
to
open
this
app
up
for
the
marketplace
and
for
people
to
use,
you
would
click
this
other
any
account
button
and
that
just
lets
anyone
install
your
application,
which
is
pretty
cool.
A
Anyone
can
install
it
if
it
still
requires
things
like
tokens
or
license
keys
and
stuff,
like
that,
that's
where
you
get
into
the
payment
model
and
all
of
that
still
but
they'd
be
able
to
install
your
app,
which
is
pretty
cool.
So,
let's
create
it
and
see.
If
I
messed
up
any
of
these
fields
there
we
go,
I've
messed
up,
one
of
them.
A
Apparently
my
home
page
can't
be
blank
either.
So
that's
what
I
get
for
that
and
I
think
it's
going
to
be
fully
qualified.
So
let
me
do
that.
A
Live
demos
are
fun
and
fully
qualified
did.
I
did
I
not
do
that
just
now.
Thank
you.
Keyboard
for
working
and
underscore's
gone.
Okay.
I
think
I
got
everything
here
and
my
permissions
and
stuff
still
checked
cool.
That's
all
checked
good.
Only
this
account
create
cross.
Your
fingers
see
if
they
get
embarrassed
again
cool
all
right,
we're
good
to
go
so
now
I
have
my
app
right.
The
next
step
I'd
create
my
private
key.
If
I
was
going
to
start
taking
actions
on
things,
start
testing
things
out.
A
A
lot
of
the
app
endpoints
require
that
you
use
a
json
web
token,
and
then
you
use
that
json
web
token
to
create
an
installation
access
token
and
all
these
fun
little
steps
that
I
won't
worry
about
getting
into
the
specifics
of
for
this,
but
you'll
need
things
like
your
app
id
and
this
client
secret
thing
to
to
sign
specific
items
right
so
cool.
So
we
have
our
app
now
and
you
know
basically
at
this
point:
all
user
needs
to
do
is
install
my
application
and
they
can
start
using
my
product.
A
So
it's
that
simple!
You
know
once
this
is
available
on
like
for
public,
for
anyone
to
install
you
get
an
option
to
publish
the
marketplace
down
here
at
the
bottom
somewhere.
I
believe
so
you
know
you
can
do
that
too,
which
is
pretty
cool.
There
are
some
questions
about
enterprises
specifically
and
like
managing
that.
So
one
of
the
cool
things
about
enterprise
cloud
is,
you
can
do
things
like
set
up
an
ipl
list
as
an
organ
administrator.
This
is
a
beta
feature,
but
it's
something
that
we
we
have
available
on
enterprise
cloud.
A
So
if
your
app
needs
to
allow
specific
ips
through
to
get
to
your
service,
you
can
set
it
up
here
too,
which
is
pretty
cool,
so
it
allows
organizations
to
have
that
auto
subscribe.
They
don't
need
to
go
into
their
org
and
set
everything
up
themselves.
We
want
to
extract
that
away
and
make
it
as
painless
for
the
end
user
as
possible,
so
pretty
cool
stuff.
There
just
wanted
to
show
that
just
as
a
quick
little
ui
demo
and
then
I'm
gonna
go
through
some
of
these
other
taps
here.
A
So
I
mentioned
a
few
times
octicat.
So
this
is,
if
you
just
search
octokit
it'll,
be
there.
I
think
it's
octokid.github.io,
so
we
have
our
three
official
ones
right,
ruby.net
and
javascript.
Javascript
is
probably
the
most
actively
developed
one.
We
have
some
dedicated
people
for
that.net
gets
a
little
bit
of
love
as
well,
and
I
haven't
actually
used
the
ruby
one
for
a
while,
but
I
know
that's
obviously
up
to
date
as
well.
We
manage
all
of
these
and
then
I
talked
about
third
parties
right.
A
So
maybe
I
use
a
different
language
that
isn't
listed
here.
Well,
here's
our
go
one!
Here's
a
couple
options
for
java:
we
have
even
more
javascript
options.
We
have
perl
options
if
you
want
to
go
back
to
perl
or
php,
even
right,
python.
There's
quite
a
few
here.
There's
this
github
flask
thing
here
as
well.
So
if
you're
going
to
use
flask
for
your
web
apps,
then
you
can
do
that
in
python.
So
the
point
is
that
there's
loads
of
options
available
and
wrappers
for
api.
Here's
that
shell,
one
that
I
mentioned
as
well.
A
So
you
know
it's
it's
something
that
makes
it
really
accessible.
I
would
say
to
be
able
to
get
into
developing
and
working
with
the
ecosystem,
which
is
pretty
cool.
All
of
these
that
we
own
are
open
source.
You
can
contribute
to
them.
I
don't
know
if
necessarily
all
of
the
other
ones
are
open
source,
but
you
should
be
able
to
see
them
as
well,
which
is
pretty
cool
cool.
So,
let's
talk
about
probot,
real
quick.
I
mentioned
this
as
well.
A
It's
just
another
tool
in
your
toolbox
right,
so
probot
specifically,
is
for
github,
apps
and
specifically
for
node,
but
there
is
this
whole
listing
on
probot.github.io
that
has
all
these
really
cool
apps
that
people
have
created
one
of
the
most
popular
ones,
I
think,
is
the
stalebot
that
we
use
internally
at
github,
at
least,
which
allows
you
to
close
out
old
stale
issues
and
pull
requests
as
you'd
like
to
which
is
pretty
cool.
This
release.
Drafter
is
also
super
cool.
A
So
basically,
if
you
wanted
to
have,
if
you
had
proper
commit
messages
and
everything
you
could
have,
this
app
run
to
create
a
draft
release
for
you
and
it
generates
release
notes
automatically
based
on
the
changes
that
have
happened
since
your
previous
release,
pretty
cool,
a
lot
of
cool,
you
know
implications
here
and
everything
I
won't
go
through
all
of
them,
but
the
other
thing
I
wanted
to
show
is
specifically
their
documentation.
A
Probot
makes
it
super
easy
to
get
started.
Like
super
super
easy.
You
basically
run
this
command
create
probot
app.
It
walks
you
through
a
few
steps
similar
to
like
creating
your
first
node
app
in
general,
where
you
fill
in
things
like
you
know,
what's
the
the
name
of
this
application,
the
author,
the
purpose
repo,
you
know
just
a
few
things
like
that
and
you're
up
and
running
and
you'll
actually
have
like
a
hello
world
app
set
up
right
away.
There's
also
steps
for
even
just
running
this
locally,
which
is
pretty
cool.
A
You
know
using
something
like
nodemon
to
get
it
started
and
everything,
and
then
you
can
use
something
like
smee.io.
I
would
not
use
that
for
production,
but
you
can
use
smee.io
for
testing
purposes
and
that's
just
like
a
web
hook
listener
out
there.
That
can
give
you
a
gui
based
way
to
to
listen
to
events
again,
don't
use
it
for
production.
I
I
don't
know
if
it's
going
to
be
like
super
secure
necessarily,
so
I
wouldn't
say
that
the
purpose
was
for
testing,
so
I
wanted
to
call
that
cool.
A
So,
let's
see
what
else
do
we
have
in
this
page?
I
wanted
to
show
yeah,
I
think
in
general.
That's
that's
about
it
here,
but
probot
just
makes
it
easy
to
create
your
app
based
on
like
your
own
configuration
basically
like
I
said
so.
It's
pretty
cool
a
lot
of
documentation,
there's
like
plug-in
type
things
and
all
this
fun
stuff,
but
it
makes
handling
web
hooks
easier
for
your
apps
and
it's
just
like
a
wrapper
of
the
octa-kit
wrapper,
which
is
pretty
cool.
A
I
talked
about
the
github
marketplace,
so
you
know
when
you
go
to
github.com,
there's
that
marketplace
icon
at
the
bar
button
at
the
top,
and
we
have
a
couple
filters
on
the
left-hand
side
for
the
various
categories
and
then
there's
also
like
apps,
specifically
in
actions
and
then
there's
all
the
other
ones
that
are
in
here,
so
everything
from
learning
apps
to
scalability
monitoring
security,
apps,
all
that
fun
stuff.
We
talked
about
dependency
management
earlier
there
might
be
an
app
for
you
out
there
or
an
action
for
you
for
that.
A
So
you
know
that
all
being
said
you
know
just
as
an
example.
I
talked
about
the
slack
app
before
so
you
know:
here's
our
official
slack
and
github
app
right.
So
you
can
go
ahead
and
click
in
here
and
you
literally
would
just
hit
like
set
up
plan
and
you
go
through
the
installation
process
and
you
get
it
set
up.
So
it's
so
much
easier
as
an
end
user
for
me
to
just
consume
this,
and
I
get
to
see
like
oh
okay.
This
is
what
this
is
about.
A
A
So
if
I
go
into
our
actions,
real
quick
and
then
I
search
for,
for
example,
giffy
generator-
I
probably
should
do
super
linter
since
that's
a
little
bit
more
popular,
so
here's
our
super
linter
and
then
someone
actually
forked
it
and
made
super
duper
linter.
They
wanted
to
rewrite
it
in
powershell.
I
believe
we
did
it
in
shell
initially
but
yeah.
So
here's
our
super
linter
right
and
it's
a
github
action,
and
you
literally
can
click
use
latest
version
and
it
says
copy
this
to
a
yaml
file
done
end
user.
A
Super
easy
to
go
right,
see
a
few
other
people
joining
here,
so
hello
from
terese
and
jp
brep,
so
yeah
hello
thanks
for
joining
us,
so
cool
yeah
marketplace
listings
great
way
to
get
your
name
out
there
as
well
for
different
things
and,
of
course,
like,
as
things
become
popular
and
stuff
they
get
featured.
I
don't
know
what
the
full
like
rotation
is,
or
anything
for
this
stuff,
but
there's
trending
ones
and
all
those
cool
things
that
we
we
do
at
github
for
it,
which
is
pretty
neat.
A
So,
let's
see
what
else
did
I
want
to
show
here?
I
wanted
to
show
just
like
the
official
apps,
because
I
did
mention
those
as
well.
So
there's
the
github
slack
app.
I've
done
some
contributions
here,
you're
more
than
welcome
to
as
well.
It's
a
very
actively
developed
repo
as
far
as
like
issues
and
pull
requests
coming
in
and
taking
into
account
all
of
that
stuff.
A
So
all
of
this
is
open
source
and
you
can
see
exactly
how
we
built
a
product
that
is
used
by
so
many
enterprises,
so
many
organizations
so
many
users
to
have
their
slack
channels
updated
with
github
notifications,
and
you
can
literally
walk
through
the
entire
code
base
because
it's
all
open
source.
This
is
a
github
app,
there's
nothing
special
about
it,
nothing,
nothing
crazy.
We
have
it
hosted
somewhere
and
it's
basically
acting
as
middleware
between
slack
and
github.
A
So
you
can
read
about
it
more
here.
The
jira
app
is
another
one
that
was
a
pain
point
for
customers.
They
wanted
to
have
a
good
way
to
connect
their
github
issues
and
commits,
and
things
like
that
to
jira
cloud.
So
I'm
on
github.com
for
cloud.
I'm
on
jira
for
cloud.
I
want
to
connect
these
two.
How
do
I
do
it?
Well,
we
have
an
official
integration
for
that.
These
are
all
public
api
endpoints
that
we're
using
these
are
all
public
things.
We
aren't
doing
anything
specific
that
is
internal
to
github.
A
For
these
things
right,
that's
why
they're
open
source
even
too
so
anyone
else
could
have
made,
including
that
last
name
like
could
have
made
this
official
jira
app.
For
example,
someone
could
have
made
like
an
official
connector
that
goes
between
the
you
know,
github
project
board
and
jira
kanban
board,
or
something
like
that,
like
that's
all
possible
and
doable
just
through
the
api
endpoints.
A
So
I
just
wanted
to
kind
of
call
out
some
like
real
use
cases
and
problems
that
we
solved
ourselves
at
github
and
for
other
customers
as
well,
and
then,
finally,
this
last
one
here
I
mentioned
a
couple
times-
super
lenter,
so
this
is
a
github
action
instead,
so
just
to
show
that
piece
instead,
github
actions
is
awesome.
It's
a
serverless
thing.
Super
linter
is
a
beast.
I've
done
some
contributions
here
as
well.
A
I'm
right
here
on
this
list,
but
basically
what
this
one
was
solving
for
was
you
know:
hey
we
have
these
mono
repos
and
I
have
like
10
linters
set
up,
because
I
want
to
keep
my
markdown
consistent.
I
want
to
keep
my
emo
files
consistent,
but
I
also
have
html
and
css,
and
I
have
javascript-
and
you
know
occasionally,
there's
some
embedded
ruby
code.
So
it's
like
all
this
stuff
within
here
and
there's
no
consistency
because
setting
up
all
those
linters
is
such
a
pain.
A
Well,
this
is
a
ci
tool
that
will
actually
line
your
entire
code
base
using
a
whole
list
of
linters.
That
is
constantly
growing.
We
are
releasing
like
multiple
times
a
week
with
this
thing,
but
everything
from
ansible
files
to
you
know
azure
files,
aws
c-sharp,
just
got
added
recently.
I
was
helping
out
with
that
one
css
closure
coffeescript
right,
like
I
won't
read
through
all
of
them
here,
but
you
can
see
like
all
of
these
linters
are
built
in
and
as
an
end
user
for
that
pain.
Point
that
I'm
solving
using
superlengther.
A
It's
literally
just
like
click
that
button
that
says,
use
latest
version
copy
that
text
into
your
repo
you're
done.
That's
it
like
it's
so
simple
and
I
think
that's
one
of
the
great
things
about
our
integrations
in
general
is
how
easy
it
is
for
the
end
user
to
set
up
and
get
started
with
their
integration
and
then
as
an
app
developer
or
as
an
integrator
myself
like.
A
I
can
write
these
integrations
using
publicly
available
endpoints
with
plenty
of
open
source
projects
to
source
and
reference,
and
I
can
do
anything
I
want
with
apis
at
that
point,
which
is
pretty
cool
so
that
all
said,
let's
go
back
to
that
wonderful
slide
deck
real
quick!
I
got
a
couple
more.
I
want
to
finish
off
with.
A
So,
let's
see,
let's
talk
about
some
common
pain
points
now
and
when
I
say
this,
this
is
specifically
on,
like
the
integrator
side,
so
you're
building
a
product
again
right,
we're
talking
about
building
our
own
business
on
github
building,
something
that
can
be
used
by
the
github
community.
So
there's
a
few
pain
points
that
were
brought
up
by
the
various
people
that
I
talked
to
that
we've
gone
through
acquisitions
with
and
everything
so
I
do
want
to.
I
do
want
to
discuss
that
for
us.
A
So
first
thing:
first
payment
options
right,
so
it
is
highly
recommended
by
all
the
people
I
talked
to
to
have
multiple
payment
options
available,
while
github
marketplace
does
offer
a
payment
plan
of
some
sort.
A
lot
of
enterprises,
especially
they
have
like
purchase,
order,
requests
and
like
special
ways
that
things
need
to
be
done
to
acquire
software
so
having
an
extra
system,
whether
it's
stripe
or
you
know,
some
other
marketplace
type
system
is
pretty
important.
It's
it's
something
that
you
know
we
need
to.
A
We
need
to
take
into
consideration,
I
guess
and
even
within
github.
I
think
we
should
probably
consider
some
of
those
options
as
well
when
you
know
I
bought
a
github
license,
but
does
my
github
license
extend
to
the
marketplace?
I
don't
know.
I
need
approvals
for
this
change
management.
All
this
fun
stuff
right
so
having
some
other
system
can
help
out
with
that
which
is
pretty
nice.
In
addition
to
that,
maybe
other
marketplaces
as
well
just
off
the
top.
A
My
head,
I'm
kind
of
spitting
this
out,
but
it
would
be
something
like
you
know:
the
azure
marketplace
or
aws
marketplace.
Maybe
you
have
an
integration
that
works
with
aws
and
github,
so
you
put
it
in
the
aws
marketplace
and
maybe
that's
easier
for
your
users
to
install
from
there,
because
they
already
have
an
approval
for
a
po
with
aws
and
they
just
need
to
tack
on
another
app
to
it
right.
So
there's
there's
definitely
some
cool
things
there
permissions.
A
So
I
hit
on
this
a
little
bit,
but
I
really
want
to
hit
this
point
home
people
don't
like
giving
out
access
to
things
right,
especially
when
it
comes
to
their
private
code
bases
so
giving
code
access
and
saying
that
you
need
read
and
write,
especially
that's
that's
kind
of
scary
for
people
and
it's
a
blocker
and
people
won't
install
your
app
because
of
it.
So
just
the
the
point
of
this
is
just
make
sure
you
don't
require
more
permissions
than
you
need
right.
A
A
You
know
potentialities
on
like
data
records
and
getting
rid
of
that
stuff
and
all
that
fun
fun
thing
that
comes
along
with
that
and
we
have
gdpr
requirements,
and
you
know
all
those
fun
things
so
limiting
the
amount
of
permissions
limits,
the
data
that
you
have
access
to,
it
limits
the
data
that
you're
receiving
and
it's
better
for
your
users
because
they
feel
more
comfortable
knowing
like.
Oh,
this
is
only
needs
this
one
file
access.
It
doesn't
need
my
whole
repo.
It
just
needs
to
have
this
config
file.
That
makes
sense.
A
I
can
allow
that
another
important
thing
is
licensing
in
terms
of
service,
so
I
put
this
as
a
pain
point,
because
I
think
as
individuals,
if
we're
writing
software,
we
probably
just
find
a
template
for
licenses
or
for
terms
of
service
which
is
fine
to
get
started
with,
but
it's
recommended
that
you
probably
seek
some
sort
of
legal
help.
I'm
not
a
lawyer,
a
hashtag,
not
a
lawyer
right,
but
just
keep
that
in
mind.
A
You
know
as
you're
talking
about
like
terms
of
service,
especially
when
you
get
into
a
subscription
model
or
a
licensed
sale
model
where
you're
saying
like
you
get
access
to
my
software.
For
this
reason
you
wanna
have
some
specific
documentation
there
and
speaking
of
that
documentation,
you
want
to
have
your
own
clean
documentation
as
well
for
the
the
integration
itself.
So
I'm
going
to
go
ahead
and
pick
on
superlinter
again
just
real
quick
on
the
browser.
If
I
go
to
our
marketplace
listing
for
it,
which
here
it
is,
you
want
marketplace.
A
So
this
that
you're,
seeing
rendered
here
is
our
readme
right.
This
is
the
exact
same
content,
and
one
of
the
reasons
I
wanted
to
call
this
out
is
that
for
action.
Specifically,
we
recommend,
as
github
like
to
say,
if
you're
going
to
build
your
own
action,
you
should
put
an
example
workflow
inside
of
here,
so
we
have
like
how
to
use
right
and
here's
this
example
workflow.
That
tells
you
exactly
what
to
do.
A
You
could
literally
copy
paste
this
into
your
repository
and
it
would
start
working
right
away
like
this
github
token's
plugged
in
automatically
so
as
long
as
you're,
your
branch,
whether
it's
master,
main
or
or
dev,
or
release,
or
whatever
it
is
as
long
as
that's
set
up
right
like
this
copy
paste,
is
all
I
need
to
do
as
a
user
right
so
having
a
clean
documentation.
That
shows
exactly
what
the
prereqs
are
exactly
how
it's
supposed
to
be
used.
A
That
just
goes
so
far,
and
it's
one
of
those
things
that
we
forget
a
lot
as
developers,
especially
where
you
know
we
aren't
keeping
in
mind
all
the
time
that
there
are
external
parties
that
don't
know
all
the
intricacies
that
need
to
have
clean
documentation
of
how
things
work.
A
So
I
want
to
make
a
quick
call
out
for
that
and
then,
if
you
ever
like
open
source
and
stuff
too,
obviously
things
like
contributing
guides
or
even
things
like
support.md,
which
would
be
a
commonality
to
like
say.
This
is
how
you
request
support
on
our
application
right.
So
you
can
create
issues
and
things
like
that.
So.
A
Cool
so
general
best
practices,
and
I
think
this
is
probably
my
last
slide
and
I'll
have
a
little
bit
of
q
a
time
and
things
like
that
at
the
end
here
so
kind
of
recapping,
some
of
the
points
from
earlier
multiple
payment
options.
You
know
I've
talked
about
like
just
the
po
process.
The
purchase
order
process
of
going
through
and
using
like
github
marketplace
only
just
limits
your
customers
options
to
be
able
to
adopt
your
your
platform
or
your
software,
focusing
on
one
platform.
So
this
was
another
interesting
thing.
A
I
asked
paul
panda,
for
example
abby
from
pullpanda
who
went
through
the
acquisition
process
and
everything
I
said
you
know
how
come
you
pick
slacking
github
like?
Why
didn't
you
support
gitlab
and
bitbucket?
And
you
know,
maybe
even
other
products
like
subversion
and
stuff
like
that
right
or
clearcase
and
perforce
and
all
those
fun
things
and
he's
like
well.
Really,
you
know,
slack
is
like
the
number
one
thing
that
my
customers
that
were
complaining
about
things,
that's
what
they
were
using.
So
I
focused
on
slack
for
the
chat
side.
A
Instead
of
you
know,
microsoft
teams,
and
then
he
said
that
he
focused
on
github,
because
that's
where
his
users
were,
he
didn't
really
have
that
many
users
on
gitlab,
specifically
with
this
pain
point,
so
he
didn't
really
put
any
investment
into
it
and
decided
not
to
support
that,
and
that
was
you
know
way
before
they
got
acquired
or
anything.
A
It
was
just
a
decision
point
that
he
made
and
he
said
it
really
helped
him
because
it
made
it
again
going
back
to
that,
keep
it
simple
model
of
just
really
focusing
on
one
thing
and
doing
it
really.
Well,
I
talked
about
permissions.
You
know,
I
won't
hit
the
point
home
too
much
more
here,
but
just
limiting
that
being
mindful
of
what
you're
asking
for
and
how
that
impacts
a
user,
especially
a
security,
conscious
enterprise
right
we
have
highly
regulated
industries.
A
bank
system
maybe
doesn't
want
to
give
you
full
access
to
their
code.
A
That
type
of
thing
consider
a
lawyer
right.
So
again,
I'm
not
a
lawyer,
but
I
think
any
type
of
legal
documentation
around
user
agreements,
terms
of
service
contracts
for
licenses
and
all
that
fun
stuff
should
probably
go
through
a
lawyer
if
you're
going
to
make
this
a
real
business.
So
just
keep
that
in
mind.
Protect
yourself
protect
the
business
you
want
to.
You
know,
save
yourself
from
any
pain
points.
A
There
talk
about
keeping
things
simple
and
really
that
last
one
is
just
going
back
to
our
community
itself
and
just
validate
your
solution
and
the
customer
base
that
you
have
for
the
pain
point
that
you're
solving
before
you
put
too
much
investment
in
and
what
I
mean
by
that.
Isn't
just
that.
Maybe
you
have
a
bad
idea,
but
it's
more
of
like
you
know
this.
This
idea
is
going
to
take
let's
say
six
months
to
build
out.
A
Well,
can
I
get
something:
that's
a
working
model,
maybe
a
month
away,
and
then
I
can
start
handing
it
out
to
people
get
input,
get
that
feedback
figure
out
if
this
is
going
to
be
an
okay
solution
or
if
I
need
to
deviate
and
take
another
path
for
the
same
problem,
and
you
know
do
that
before
you're,
overly
investing
in
like
hosting
fees
with
heroku
or
aws
or
azure
or
wherever
it's
at
or
you're,
just
investing
a
lot
of
your
time,
developing
all
this
different
stuff
right.
A
So
that
said,
a
couple,
quick
success
stories
and
we'll
start
probably
wrapping
up
here
in
a
minute
pole,
panda.
I've
talked
about
quite
a
bit
here.
That
was
the
main
like
interview
that
I
did
internally
here
they
were
required.
A
I
think
at
the
end
of
2018,
or
sometime
in
2019,
semel
and
dependable,
were
both
last
year
for
us
increasing
our
security
posture
at
github,
and
you
know
I'm
not
saying
that
if
you
build
like
the
next
best
integration,
we're
going
to
acquire
you
at
github
or
anything
but
like
these
were
acquired
because
they
solve
real
pain,
points
and
areas
that
we're
concerned
about
and
the
community
is
concerned
about
and
that
we
want
to
be
able
to
enhance
and
make
better
right,
github's
a
great
platform,
but
it's
modular
with
the
api.
A
It
has
this
huge
ecosystem
around
it
and
that's
where
you
really
get
the
customization
in
my
opinion.
So
when
you
look
at
things
like
semel
and
dependabot
right,
we're
increasing
our
security
posture
in
that
sense
we're
doing
dependency
insights.
That
was
one
of
the
questions
earlier
today
in
the
chat,
dependency,
insights
and
dependency
management,
we're
investing
heavily
in
those
areas
and
why?
A
Because
the
community
is
asking
for
it,
so
we
find
these
community
pain
points
and
then
we
find
companies
that
are
are
building
up
stuff
like
that,
like
we
want
to
work
with
you
right,
we
want
to
have
those
integrations
available
for
it.
So
just
keep
that
in
mind
as
you're
you're
coming
out
with
your
products.
A
So
wrapping
everything
up
we
talked
about.
Why
github,
how
big
our
user
base
is?
Like
I
said
in
2018
to
2019,
we
grew
by
10
million
new
developers.
1.7
million
developers
were
students
that
were
learning
in
school
like
it's
just
crazy
amounts
of
numbers
and
the
new
numbers
for
2019
to
2020
should
be
coming
out,
probably
in
the
next
month,
or
so
it's
just
an
insane
amount.
You
know
when
you're
coming
up
with
an
idea,
look
for
the
pain
points
that
your
existing
community
are
asking
for.
It
could
be
co-workers.
A
It
could
be
that
you're
already
working
in
enterprise
and
you're
you're
a
developer,
and
you
want
to
have
a
little
side,
project
type
thing
and
you're
saying
hey.
You
know
I
could
probably
build
something
that
would
fix
this.
So
you
know
think
about
these
real
pain
points
right.
A
lot
of
people
say
like
well,
that's
all
great,
but
what
what's
the
product
I
build?
A
And
while
I
can't
tell
you
exactly
what
to
build
for
a
product,
I
can
tell
you
that
there
are
absolutely
pain,
points
that
exist
on
the
market
or
excuse
me
in
the
community
and
on
the
platform,
whether
it's
project
management,
it's
probably
a
big
one,
where
people
just
go
to
jira.
Usually
I
feel
like
or
other
project
management
platforms
and
jira
is
great
for
what
it
does.
It's
just
very
heavy-handed
for
a
lot
of
people.
You
know
some
people
use
tfs
for
microsoft,
for
like
burn
down
charts,
and
things
like
that.
A
So
you
know
maybe
doing
something
with
github's
projects
that
would
be.
You
know,
an
area
that
I
would
I
would
take.
A
look
at
the
point
is
to
find
excuse
me
find
the
conversations
that
are
already
happening.
A
Around
pain,
points
on
the
on
the
platform
itself
and
then
maybe
especially
like
looking
at
enterprise
pain
points
right,
because
that's
people
that
are
already
paying
for
the
product
who
want
to
use
it
even
better
and
they
have
the
big
concerns
and
the
bigger
budgets
and
things
like
that,
so
build
out
your
user
base
based
off
of
the
community
itself,
whether
it's
social
media
subreddits,
you
know
the
github
community
forums,
all
those
fun
things.
A
We
talked
about
quite
a
few
common
pain
points
that
happen
with
developers.
You
know
the
big
ones
that
I
like
to
call
out
is
again
ensuring
you
have
proper
licensing
and
documentation
from
probably
a
lawyer
for
things
like
terms
of
use
just
protecting
yourself.
There,
hello,
curious
elk,
appreciate
it.
So
you
know
that
that
common
pain
point
of
being
able
to
protect
yourself
as
an
individual
right.
A
You
don't
want
to
have
like
a
huge
enterprise,
that's
depending
on
your
application
and
then
you're
responsible
for
some
data
being
corrupted
or
something
like
that
right
and
not
have
any
documentation
or
legality
legal
shield.
I
should
say
to
protect
you.
Some
other
pain
points
have
been
around
like
payment
systems
right,
so
enterprises
often
have
like
very
strict
po
purchase
order
requirements
so
just
kind
of
being
mindful
of
that
and
offering
multiple
ways
to
pay
whether
it's
a
subscription-based
model,
maybe
they
pay
annually.
A
You
know,
that's
those
options
are
what
allow
customers
to
to
make
the
purchase.
Sometimes
it's
a
lot
easier
for
an
enterprise
to
pay
a
one-year
fee
every
year
than
trying
to
pay
every
single
month.
You
know
invoicing
them
for
the
year
is
a
little
bit
easier,
usually
best
practices
in
general
I
mean
I
just
covered
some
of
them,
but
you
know
just
remember
that
the
ecosystem's
there,
the
apis,
are
there
the
community's
there.
So
it's
really
just
a
matter
of
building
the
product
right,
so
that
all
said.
Thank
you,
everyone.
A
For
your
time.
I
got
a
couple
resources
here.
I
can
drop
these
links
in
the
chat
in
a
minute,
but
basically
our
developer.
Docs.
If
you
go
to
docs.github.com,
you
can
see
a
section
for
rest,
api
and
graphql.
There's
guides
there's
platform
samples
that
give
you
like
you
know:
code,
snippets
and
pocs
and
spikes
of
different
products.
Things
like
that,
there's
specifically
a
guide
if
you
look
through
our
docs
and
you
search
difference
between
oauth
and
github.
Apps
you'll
find
some
some
differences
there,
which
is
pretty
cool.
A
I
talked
about
those
octokit
libraries
at
octokit.github.io
and
this
last
one's
important.
I
want
to
call
it
partner
engineering,
so
this
is
a
group
that
I
used
to
work
with.
They're
part
of
our
business
development,
team
and
partner
engineering
is
the
way
to
go
if
you're,
building
an
integration
and
you're
starting
to
get
like
larger
adoption,
and
you
want
to
have
some
some
help
from
the
github
side
as
well.
Partner
engineering's,
who
you
want
to
reach
out
to
examples
of
this.
A
I've
worked
with
the
quite
a
few
of
the
integrators
in
the
marketplace,
but
we
had
like
encore.
For
example,
they
do
container
scanning
they
they
did
a
session
at
github
universe
and
that's
because
they
reached
out
to
partner
engineering
for
their
action
for
container
scanning.
So
you
know,
there's
just
a
lot
of
options
there
and
opportunities.
So
I
wanted
to
call
that
out
so
cpdos
says
how
many
private
repos
approximately
are
hosted
on
github.
I
don't
think
we
have
that
number
available.
A
Unfortunately,
publicly
I'd
have
to
check
that
octaverse
report,
but
I
believe
it
was
oh
boy
I'll.
Let
liz
tell
me
or
or
aj
I
don't
want
to
misquote
and
see
something
completely
wrong.
I
think
it's
like
50
million
or
more
it's
a
crazy
amount
of
public
repo,
so
I
don't
know
how
many
private,
even
myself,
even
working
at
github,
but
you
know
we
don't
really
get
access
to
see
all
that
stuff
right,
because
enterprises
are
on
there.
A
So
where
will
this
powerpoint
be
published,
great
question
liz
or
aj?
Have
we
been
pushing
or
publishing
anything
that
will
allow
us
to
link
out
to
this?
I
have.
I
can
make
this
into
a
pdf
for
sure
and
I'll
add
speaker
notes
in
just
so
everyone
has
a
copy
of
it.
Of
course
the
vod's
gonna
be
available
as
well.
So
you
know
you
can
check
that
out
too,
but
otherwise
I
might
do
my
own
little
write-up.
A
I
have
my
website
imuse.com
shameless
plug,
but
I
have
a
little
blog
there,
so
I
might
do
it
right
up
there
as
well
and
if
I
do
then
I'll
definitely
publish
slides
there
or
I'll
throw
them
on
speaker
deck
or
something
like
that.
So
maybe
I
don't
know
if
we
can
put
like
a
description
in
the
vod
later,
but
we
can
probably
do
that.
Oh
thanks,
my
websites
took
a
while
to
put
together.
I
I
appreciate
it,
but
you
know
it's
a
fun
blog.
A
I
mostly
talk
about
github
since
that's
what
I
do
on
a
day-to-day,
but
I
got
some
history
there
and
everything
too
so
cool.
Well,
thanks
everyone
for
coming
out.
I
really
appreciate
it
the
vods
so
aj
they're
available
here.
I
think
for
two
weeks
right
on
twitch
and
then
do
we
move
them
to
our
youtube
channel
or.
A
Also
correct
okay.
So
if
you
look
at
the
description
for
the
channel
where
it
says
like
about
github
enterprise,
there's
links
to
twitter,
linkedin
and
youtube
specifically,
so
I
highly
recommend
subscribe
to
the
youtube
channel.
It'll
be
posted
there
and
then
again,
two
weeks
on
twitch
itself,
so
the
vod
will
be
available
when
we're
not
live.
You'll
see
a
tab
for
videos,
I
believe
it's
called
and
then
you'll
go
there.
So.
A
Yeah
so
incades
asking
so
interested
in
applying
to
github
does
github
use
teams
so
you're
talking
about
microsoft
teams.
I
assume
we
have
some
use
there.
We
actually
use
slack
and
I'm
actually
on
a
macbook.
If
you
didn't
notice
too,
so
you
know
we
still
are
very
much
like
kind
of
an
independent
company
within
microsoft's
ecosystem.
A
So
you
know
that
that
said
we
have
our
own
practices
like
we're.
Using
slack,
we
probably
won't
be
going
away
from
slack
anytime
soon,
just
because
we've
used
it
for
so
long.
We
do
have
some
people
know
as
we
start
working
closer
with
microsoft
developers
specifically,
and
you
know,
github
actions.
A
lot
of
that
team
came
from
the
microsoft
side,
so
we
have
people
using
teams,
but
it's
not
super
common
just
yet
for
us
internally,
that
is
as
far
as
interest
in
applying
to
github
definitely
check
out
our
job
page.
A
I
know
there's
listings
there.
It
changes
pretty
regularly
and
there's
new
postings
fairly
regularly.
You
know
in
this
time,
especially
I
know
it's
hard
to
find
hard
to
find
work,
but
we
are
hiring
still
so.
Please
definitely
check
it
out.
Cpdos
no
problem
at
all,
I'm
glad
it
was
informational
and
you
enjoyed
it.
A
Cool
and
then
just
now
in
the
chat
we
just
put
the
the
playlist
link
as
well.
So
if
you
want
to
see
any
of
the
past
demo
days,
a
lot
of
my
coworkers
and
colleagues
have
done
pretty
awesome
demos
on
things
a
little
bit
more
on
the
technical
side
like
showing
actual
ci
cd
implications
packages
and
actions
and
all
that
fun,
fun
stuff.
So
yeah
hyperchain
labs,
no
problem
at
all.
I'm
glad
that
glad
you're
able
to
enjoy
it
and
get
something
out
of
it.
Hopefully,.
A
Cool
well,
let's
see
here,
I
don't
know
if
we
want
to
start
wrapping
up,
maybe
aj
and
liz.
I
that's
about
all
the
content
I
have,
but
I
have
no
problem
answering
questions.
I
got
a
free
schedule
after
this,
so
I
don't
mind
hanging
out
for
a
little
bit.
A
Yeah
good
point
there
too,
so
there
is
a
link
in
the
chat
right
now.
If
you
have
any
specific
problems
at
all,
you
can
hit
us
up
with
that
link.
So
thanks
for
putting
that
in
too.
A
Okay,
cool
yeah
so
I'll
be
in
the
chat
my
handle
that
org
that
I
was
using
the
bearded
tom
fun
fact.
I
used
to
do
like
youtube
and
streaming
and
all
that
stuff.
I
haven't
done
it
for
quite
a
while
now
a
couple
years,
but
you
can
find
me
the
bearded
tom
in
chats
I'll,
be
I'll,
be
talking
there
for
y'all
yeah
great
question
on
why
we're
not
partnered
we
should
probably
reach
out
to
twitch
about
that.
A
Be
fun.
Yeah
that'd,
be
that'd,
be
a
lot
of
fun.
So
there's
chatter,
basically
just
like
yeah.
We
should
talk
to
to
twitch
about
that.
So
anyway,
yeah
thanks
so
much
root.
I
appreciate
it
so
yeah.
Thank
you,
everyone
for
coming
out.
You
know
our
schedule's
posted
there
we're
doing
more
of
these
demo
days.
All
the
time
we
have
a
lot
of
cool
topics
coming
up.
I
might
come
back
as
a
guest
again
in
the
future.
Hopefully,
if
I'm
invited
so
we'll,
hopefully
see
some
of
you
all
next
time
as
well.