►
From YouTube: Demo Days - Driving collaborative development
Description
Natalie Bradley (Field Architect), Eric Johnson (Solutions Engineer) and Dean Stravopoulos (Solutions Engineer) talk about how you can use GitHub to drive collaboration at work. They walk through both maintainer and contributor perspectives all while demonstrating the GitHub Flow.
Learn more about DevOps here: https://github.com/learn/devops
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
Google+: http://google.com/+github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
All
right-
hey
everybody
great
to
be
here,
super
excited
that
you
all
dialed
in
and
are
joining
us.
I'm
natalie
bradley,
I'm
a
field
architect
with
github.
I've
been
here
for
about
two
years
now,
and
I
help
our
enterprise
customers
with
github
implementation
in
creating
a
more
collaborative
culture
and
enterprise,
and
I'm
joined
here
with
two
others
that
are
going
to
introduce
themselves
as
well.
C
Hey
folks,
dean
staropolis
also
from
the
solutions
engineering
team
at
github
good
to
meet
you
folks,
yeah,
so
for
today's
session,
I'm
going
to
look
to
moderate
the
chat.
So
let's
continue
on
this
theme
of
collaborative
development
feel
free
to
ask
any
questions.
I'm
also
going
to
look
to
ask
a
couple
of
questions
and
let's
have
some
fun
back
back
to
you.
Folks.
A
A
That
all
right,
so
we've
got
people
using
it.
Both
that's
awesome,
github
lots
of
bolts,
cool,
yay,
awesome,
okay,
cool,
so
we've
got
some
a
lot
of
both
so
super
excited
about
that,
because
our
content
works
either
way.
It's
just
super
helpful
to
figure
out
how
to
collaborate
at
work.
So
we
wanna
make
sure
that
we're
sharing
that
info
with
you
today,
so
we're
gonna
talk
highlight
what
collaboration
is
and
how
you
do
that
at
work.
A
We're
not
gonna
deep
dive
too
much
into
any
one
thing,
but
we
totally
can
so
just
shoot
a
note
over
in
the
chat
and
dean
will.
Let
us
know
if
we
need
to
slow
down
or
deep
dive
on
anything.
The
cool
thing
about
collaboration.
Is
it's
two-sided
so
for
today's
demo
we're
gonna
be
two-sided
right,
so
I'm
a
maintainer
of
a
repository
and
eric
is
gonna,
be
a
contributor
looking
to
help
on
something
cool
for
the
purposes
of
this
demo.
A
A
How
to
find
things
that
aren't
related
to
your
direct
work,
but
maybe
it's
something
you're
interested
in
or
somebody
else
needs
help
we're
going
to
talk
a
little
bit
about
actions
what
they
are
and
how
you
can
use
those
in
your
projects
to
do,
builds
and
then
we're
going
to
explain
the
github
flow
and
actually
demo
it
so
you're,
going
to
see
both
sides
of
the
github
flow,
how
to
contribute
something:
how
to
review
and
approve
something
and
ultimately
how
to
collaborate.
So,
hopefully,
you'll
learn
some
new
cool
things
to
take
advantage
of.
A
So
with
that
we
will
get
started.
Let
me
share
my
screen
here
and
show
you
a
repository
that
this
project
is
actually
a
project
we
use
at
github.
For
the
purposes
of
today,
we've
moved
it
to
a
different
organization
called
universal
exports,
and
we
did
that
so
that
we
don't
mess
up
anybody's
who's
actually
working
today
and
get
some
cool
things
done,
but
slide
heroes.
So
here's
the
repository
slide
heroes
is
actually
just
a
group
of
us
that
knew
we
needed
to
get
something
done,
that
our
company
hasn't
totally
resourced.
A
So,
there's
about
five
of
us
that
are
maintainers
on
this
repository
we
index
and
cultivate
a
bunch
of
slide
decks
and
briefings
that
solutions
engineers
within
our
companies
use
we
tag
it.
We
help
them
sort
it
and
find
it
so
they
know
what's
relevant,
what's
useful,
all
this
kind
of
stuff.
It's
a
super
helpful
repository
in
our
organization
that
we've
turned
into
a
github
page,
get
a
page
if
you're
not
familiar,
is
a
static
website
and
lets.
You
display
really
cool
information
internally
to
your
fellow
organization,
people
or
externally
to
the
world
wide
web.
A
So
here
is
a
the
actual
page
for
slide
heroes.
You
can
see
slidex
who
created
them
a
little
bit
about
them
and
the
date
so
again
super
helpful
content
for
our
community
that
it's
not
a
dedicated
project
in
github.
So
as
a
maintainer,
I
am
always
looking
for
people
to
help
whether
it's
help
with
issues
help
with
feature
requests,
help
fix
bugs
all
that
kind
of
stuff.
So
from
there
I'm
going
to
turn
it
over.
A
B
Well-
and
I
don't
know
about
you
all,
but
when
I'm
new
on
the
job,
I
I
worry
about
a
couple
of
things-
one
I
worry
about:
where
is
a
decent
place
to
have
lunch,
and
I
also
worry
about
okay.
Can
I
can
I
do
something?
What
can
I
do?
That's
going
to
impress
my
boss
soon
after
I've
just
joined
this
job,
because
well
because,
obviously,
why?
Because
we
want
to
impress
our
bosses,
especially
when
we're
new
at
the
job
and
the
other
thing
that
I
really
worry
about
is.
B
Can
I
find
something
to
do?
That's
gonna
impress
my
boss
without
bugging
my
boss
too
much
right
that
isn't
gonna
be
too
hard
because
I
don't
know
about
you,
but
I
want
to
like
look
kind
of
smart
and
clever
and
eager
and
all
that
good
stuff.
So
let's
see
how
how
we
can
do
about
this,
let
me
share
my
screen
now
I
will
say
I
do
know
a
bit
about
github
because
you
know
like
like
you
guys.
I've
used
it
personally.
B
I've
used
it
other
jobs.
I've
used
a
lot
of
different
places,
so
I
know
a
little
bit
about
that.
I
don't
know
a
lot
about
universal
exports,
though
other
than
it
seems
like
a
really
really
great
place
to
work,
so
I'm
gonna
start
here
now,
you'll
see
here
on
my
screen,
we're
starting
out
just
at
the
the
organization
page
here
for
for
universal
exports,
and
you
may
you
may
be
familiar
with
this,
but
there's
a
couple
of
superpowers
here
that
you
may
not
know
first
off
what
this
is
showing.
B
B
That
means
anybody
here
at
universal
exports
could
access
that
kind
of
thing
and
then
the
other
thing
that's
interesting
here
is
this
view
is
going
to
be
sorted
by
most
recent
action
so
stuff
that
that
I
can
access
that's
been
hot
or
popular
recently
is
going
to
be
more
at
the
top
of
this
list.
So
right
away,
I
can
kind
of
see
you
know
a
little
bit
what's
going
on.
I
see
some
people
have
used
topics
to
identify.
B
You
know,
maybe
the
technologies
or
what's
what's
going
on
here
with
various
repositories.
So
even
just
at
first
glance.
Let
me
go
in
deep,
I
I
don't
know
you
know
what
does
universal
exports
do?
Hopefully
I
answer
that
ask
that
in
my
interview,
but
I
can
tell,
from
a
code
perspective
a
little
bit
about
about,
what's
going
on,
I'm
going
to
use,
get
observed
just
across
the
back
off
the
back
here
to
see
a
couple
of
things.
First
off.
B
B
Help
wanted
okay,
now,
first
of
all,
there's
a
couple.
Let
me
just
go
back
here
for
a
minute.
Let
me
do
that
in
a
little
in
in
slow
motion
here
for
now
just
come
on
back
to
our
org
page.
There
we
go
perfect,
okay,
so
org
page
here
all
right
again.
This
is
the
just
the
main
search
box
right
up
in
the
top
of
the
black
banner
there
right
on
top
of
github,
and
if
you
put
anything
in
here
by
default
here,
I
got
a
couple
of
options
here
where
to
search
okay.
B
Now,
if
you're
using
github
work,
you're
gonna
have
help
wanted
a
way
to
search
in
this
organization.
In
this
case,
this
means
I'm
searching
only
in
universal
exports.
If
you're
using
github
for
on
your
own
you're,
not
going
to
have
that
option,
probably
right,
you
are
going
to
have
the
option
of
searching
all
of
github.
I
am
sure
that
there
are
open
source
projects
on
all
of
github
here
who
have
helped
wanted,
are
going
to
want
my
help.
B
I
am
sure
that
they
may
be
even
more
deserving
than
whatever
I'm
going
to
find
to
do
on.
My
first
day
here
at
universal
exports,
but
I
think
I'm
going
to
stick
with
something
that
I
can
show
my
boss
and
you
know,
keep
up
the
excitement
about
me
being
here
on.
So
I'm
going
to
search
in
this
organization.
B
Okay,
and
I'm
going
to
see
a
couple
things
first
off
one.
There
is
not
a
repository
in
the
organization
named
health
wanted
or
with
help
wanted
in
the
name
that
makes
sense
commits
okay.
I
do
see
a
little
bit
of
code.
So
let's
look
at
those
code
results
here
and-
and
I
guess
what
I'm
seeing
here
are
some
snapshots
some
markdown
files
here.
You
know
how
to
contribute
here
in
a
couple
of
different
repositories,
but
what
these
are
pointing
out
are
health
wanted
issues
just
some
text
talking
about
that
and
here's
a
secret.
B
B
The
idea
being
if
somebody
like
in
natalie's
situation
has
got
a
project
that
could
use
some
additional
help.
That
is
an
obvious
way
to
label
those.
Now
your
org
may
have
a
different
convention.
You
may
use
a
different
set
of
labels
at
work.
You
may
be
involved
in
projects
that
set
their
own
set
of
standards.
So
I
would
you
know,
encourage
you
to
kind
of
look
around
at
the
issue
list
and
those
list
of
labels
to
kind
of
see
what
what
the
rules
are.
B
But
if
you
don't
know
and
you're
trying
to
impress
your
boss
and
it's
your
first
day
searching
for
help
wanted
is
a
pretty
cool
thing
to
do
now.
The
text
files,
the
markdown
files
here,
where
I'm
seeing
this
aren't
going
to
help
us
very
much
so
I'm
gonna
do
another
thing.
I'm
gonna
do
a
little
refinement
here
to
to
this
search,
and
that
is
oops.
I
need
some
quotes
around
it
because
help
one
it
has
got,
got
a
space
in
the
middle.
B
I
gotta
put
some
quotes
around
this,
so
I'm
gonna
refine.
This
search
and
search
for
the
label
help
wanted
not
just
text,
not
free
text,
but
the
label
itself,
I'm
still
working
just
in
my
organization
again,
if
you
search
github
wide
for
that
string,
you're
going
to
find
a
ton
of
issues
because
that's
one
of
our
default
labels,
a
lot
of
projects
use
that
but
notice
in
this
case
here
I've
got
a
couple
of
issues
here
that
come
up.
B
B
I
was
supposed
to
hear
that
okay,
this
looks
like
you
know,
kind
of
a
feature
request
right
like
okay,
let's
add
some
tags
and
blog
posts
whatever
I
don't
know,
it
seems
a
little
complicated
for
my
first
day.
I
think
I'm
going
to
do
something
small.
I
don't
want
to
impress
my
boss
that
much
so
let
me
do
something
a
little
smaller.
Let's
go
back
and
look
at
that
other
one
here.
Let's
look
at
this
one.
B
Broken
build
again,
this
is
in
slide
heroes
and
okay,
it
looks
like
we've
got
somehow
some
build
action
here
fails.
This
is
our
a
little
get
up
page.
This
is
a
a
little
button
here
for
github
actions
that
can
show
status
where
they
pass
where
they
fail.
Let's
go
over
there
and
take
a
look
and
see
if
we
can
see
this
live
all
right
and-
and
it
looks
like
I've-
got
a
link
here
to
to
something
here-
let's
go
over
and
take
a
look
at
that.
C
B
Okay,
let
me
detour
for
a
second,
so
I
love
github
pages
because
it's
like
bam
web
hosting
at
super
scale,
without
a
lot
of
super
muscle,
busts
get
up
pages
using
and
even
this
screen
is,
is
showing
us
here.
Get
up
pages
use
something
called
jekyll
behind
the
scenes.
It's
a
ruby
based,
templating
library,
it's
pretty
good!
It's
pretty
cool!
B
I
will
say
that
there
are.
There
are
a
raft
of
other
solutions
for
that
kind
of
stuff
as
well,
and
a
lot
of
stuff
jekyll
itself
has
been
around
for
a
good
little.
While
there
are
a
bunch
of
javascript
based
la
opera
languages
that
do
the
same
sort
of
thing
again:
markdown
files,
some
sort
of
templating
language
and
then
generate
the
output.
Here
you
can
publish,
even
if
you
want
to
use
jekyll
like
we
have.
B
If
you
want
to
use
any
of
the
others,
you
can
publish
those
to
get
on
pages
pretty
straightforwardly
as
well.
So
the
scale
of
pages-
but
if
you
want
to
use
the
stuff
that's
built
in
jekyll,
is,
is
the
way
to
go,
and
it's
got
its
own
set
like
liquid,
formatting
and
temple
language
and
that
kind
of
stuff
pretty
cool.
It's
not
too
hard,
but
there
have
been
other.
There
are
other
approaches
to
that.
You
know
as
well.
B
What
I'm
looking
at
right
here?
What
that
that
bug
report
that
natalie
filed
is
looking
at
is
to
an
action,
so
there
must
be
something
a
little
fancier
going
on.
I
see
jekyll,
I
think
jekyll
is
what
we're
using,
but
it
must
be
that
there's
something
a
little
bit
fancy
that
we
have
to
do
an
explicit,
build
action
here
and
I'm
just
gonna
take
a
guess
at
it.
I
I
bet
if
I
poked
around
the
readme
here
this
repository,
I
would
learn
a
little
more.
B
Let's
go,
actually
you
know
go
and
we
can
go
ahead
and
do
that,
but
I'm
gonna
guess
usually,
when
you
see
a
build
action
like
this
for
jekyll
itself,
it
means
get
a
page
that
supports
a
certain
set
of
jekyll
plugins
kind
of
a
pretty
tame
set.
My
guess
is
whatever
we're
doing
here.
It
needs
some
additional
plugins
that
github
doesn't
come
with
out
of
the
box.
B
Okay,
but
maybe
if
I
get
rid
of
this
red
x,
my
boss
will
like
think
they
that
they
hired
the
right
guy
and
they'll,
keep
me
around
a
little
longer
right,
so
maybe,
okay,
all
right
exactly
so
maybe
red
x's
aren't
all
bad,
but
hopefully
this
will
be
an
easy
red
x.
Okay,
all
right
all!
I
know
here
again
looking
at
this
and,
let's
kind
of
take,
you
know,
take
kind
of
a
hop
right
up.
B
I'm
going
to
go
up
here
to
to
to
the
code
here
in
that
that
we're
looking
at
so
let's
come
on
up
to
the
slide
heroes
repository
and
let's
take
a
look-
and
I
see
okay,
that
bug
report-
that's
in
the
build
is
failing.
What's
going
on,
we
saw
here
in
the
issue
over
here.
Let
me
pop
this
in
another
tab.
B
B
What
is
that?
What
is
that
action
trying
to
do,
and
let's
kind
of
get
in
the
ballpark
there
around
that
and
I'm
hoping
because
one
it's
friday
and
you
know,
and
those
red
x's
aren't
good,
let's
see
when
you
and
get
rid
of
that
red
x,
but
also
and
clear
up,
natalie's
issue
here,
but
also,
let's
see
if
we
can't
do
that
with
a
let's
see.
If
we
can
do
this
with
a
modest
amount
of
effort,
because
it
is
just
first
day
on
the
job.
B
Okay.
So
again,
if
we
take
a
look
here,
github
actions,
the
the
kind
of
the
workflow
that
actually
builds
here
or
all
in
a
github
folder
in
a
folder
under
that
called
workflows
and
what's
very
lucky
for
us,
is
there's
one
workflow
in
this
folder.
So
we
can
guess
pretty
quickly
that
this
might
be
part
of
what's
going
on.
If
we
go
look
at
the
other
side
of
this
thing,
that
is
when
it
last
ran
and
what
happens,
we're
running
an
action
here
called
publish
to
get
up
pages.
B
B
Okay
and
I
notice
one
other
thing,
two
other
things
here
that
we
were
gonna
need
to
know.
So
in
an
action,
this
keyword
uses
means
this
step
of
the
action
uses
somebody
else's
code,
hilally's
code.
It
looks
like
at
this
point.
This
is
running
a
pre-packaged
action
step.
I
know
nothing
about
this,
but
but
what
I
do
know
about
github
actions
is
that
when
it
said
that
line
says
uses-
and
I
see
the
name
of
something-
that's
actually
the
name
of
a
github
repository.
B
B
B
A
B
B
Okay,
let's
come
on
over
here
and
again
we're
going
to
use
the
search
bar
like
once
again
could
not
find
bundle
a
little
a
copy
and
piece
of
error,
but
in
this
case
I'm
not
going
to
search
all
of
github,
I'm
sure
someone
on
all
github
can't
find
bundler.
I
don't
even
want
to
know
what
bundler
is.
I
don't
want
to
know
those
results
I
do
want
to
know.
Did
anybody
have
that
problem
here
in
this
code
base?
B
That
there
is-
and
this
looks
very
suspiciously
exactly
like
that
error
message
here-
that
we're
having
now
notice
a
couple
of
things
I
see
a
couple
could
not
find
bundler
here.
So
this
is
an
issue.
Here.
That's
been
closed.
I
guess
fixed.
I
don't
know
this
is
a
pull
request
here
and
this
pull
request
is
still
open,
so
somebody
has
suggested
some
code
changes
mention
bumbler
somewhere
in
this
in
the
comments
or
discussion
around
this,
but
that's
still
open.
B
It
hasn't
been
accepted
here,
and
this
is
an
error
message
here.
That's
over
sorry,
an
issue
here,
that's
open.
So,
let's
dive
into
this
issue
to
start
with
to
see
you
know
if
we
can
find
out
what's
going
on
all
right
and
dean,
while
I'm
looking
at
this-
oh
boy,
okay,
so
we've
got
an
issue,
it's
talking
about
bundler
and
that
that
happens
to
be
that
I
think
that
version
number's
over
an
error
message.
So
that's
probably
good
yeah
172.
So
that's
probably
good.
B
C
No
questions
a
lot
of
a
lot
of
great
talk
on
the
chat
here,
but
what
it
sounds
like
is,
it
looks
like
we
have
a
error
right,
you're
trying
to
leverage,
maybe
folks
on
your
team,
to
find
you
know
how
you
can
fix
that
you
went
on
the
search
you
found
some.
You
know
you
found
a
resource
here
and
you're
gonna,
look
to
leverage
that
resource
and
maybe
plug
that
in.
Does
that
sound
about
correct
that.
B
B
This
is
not
universal
exports
code.
I
mean
it
could
be
right
if
we
if
this
was
something,
but
this
is
actually
you
know,
github
wide
and
likewise
I'm
in
searching
for
the
this.
This
problem,
you
know,
if
you
will
the
bug
the
issue
here,
I
find
somebody
talking
about
a
problem
might
be
caused
by
the
same
thing.
Might
not,
I
don't
know,
but
I'm
guessing
that
it's
going
to
be
pretty
similar,
and
I
don't
even
I
mean
I
don't
know
anybody
in
these
folks.
B
B
B
This
is
this
marketplace
list
right
at
the
top
here.
Get
up
takes
you
to
this
page
and
if
you
wanna,
look
through
actions,
there's
a
little
category
here,
there's
a
lot
of
them
4
400
at
this
point,
but
these
are
components
that
can
be
mixed
and
matched
into
actions
to
accomplish
various
stuff
that
we
need
to
I'm
just
searching
here
through
jekyll,
and
it
looks
like
there's
a
lot
of
different
ones
here.
B
B
But
what
what
I'm
going
to
say
here
is
to
summarize-
because
I
have
read
this
before
so-
I
won't
bore
you
here
with
reading
it.
This
is
here
it's
available
if
you
want
to
check
it
out.
This
is
the
fabulous
here
bug
number
16
over
there
in
halal's
repository
issues,
but
I
see
in
this
case
here
somebody
me
as
it
happens
right
as
a
in
prep
to
this.
B
B
B
B
Okay,
now
that
pull
request
over
in
you
know,
this
project
hasn't
been
accepted,
so
it's
just
code
kind
of
out
there
on
offer
and
if
we
come
back
here,
there's
come
back
here,
whoops
back
there's
still,
you
know
some
kind
of
conversation
here
around
is
this
like
the
best
way
to
go
to
solve
this,
and
this
code
fix
has
not
been
put
in
place.
There's
still,
some
debate,
you
know
is
really
michael's
got
a
different
idea.
That
makes
a
lot
of
sense.
B
B
You
know
in
pull
request
form
with
a
pull
request
that
says
to
do
it,
but
it
really
is
just
an
updated
version
of
this
code.
So
what
I
want
to
do
is:
let's
give
this
a
try,
okay,
and
by
giving
this
a
try,
we're
going
to
come
on
over
we're
on
our
sort
of
broken,
build
version.
This
file
we're
going
to
work
in
the
web
browser
today,
because
why
not
hitler
point
out
so
dean?
You
had
mentioned
like
hey.
B
How
do
we
find
other
actions-
and
I
kind
of
showed
you
that
marketplace
thing
notice,
I'm
editing
an
action
here
and
notice
on
that
right.
Sidebar.
I've
got
some
suggestions
of
of
common
actions
here
you
know
to
be
used
and
this
casting
action
is
a
great
one.
We've
actually
got
that
plugged
in
here
it's
my
first
day
on
the
job.
So
I
don't
know
what
it
does,
but
it's
got
to
be
good.
More
caching
is
good
right,
always.
B
This
sort
of
a
copy
of
that
url
of
that
pull
request
where
l
studio
had
gone,
and
you
know
kind
of
changed
that
code,
okay,
and
what
I'm
going
to
do.
Yeah.
Let's
give
me
some
errors
here,
because
our
our
our
syntax
isn't
quite
right.
What
I'm
going
to
do
is
replace
the
line
right
up
above
I'm
going
to
do
this,
so
you
can
see
the
contents
of
both
here
the
thing
to
know
about
an
action
itself
when
you're
using
somebody
else's
action.
B
So
in
the
kind
of
pull
request
version
we
were
working
off
of
a
branch
over
there
called
25
ruby
2.6
again
I
got
to
change
that
syntax.
A
little
bit
get
rid
of
the
you
know,
part
of
that
url
put
an
ad
sign
in
there,
but
now
we
have
basically
got
a
pointer
here
over
to
not
the
original
version.
Here.
B
That
that
hilali
was
talking
about,
but
our
updated
version,
this
forked
pull
request
version
that
l
studio
put
together.
I'm
gonna
go
ahead
and
get
rid
of
the
previous
line
up
there,
because
github
is
gonna.
We're
gonna
have
to
commit
this
put
in
a
pull
request
and
all
that
kind
of
stuff.
So
we'll
have
that
previous
version.
There's
no
need
to
save
that.
You
know
for
posterity
to
go
back
to
it
here,
but
that
then
well,
let's
see
what
this
is
going
to
do
right.
B
C
C
B
It's
pretty
easy
and
I
would
say
it
even
a
little
bit
a
little
bit
sketchier
than
that.
I've
got
an
action
that
that
somebody
has
doctored
up
and
thinks
will
work.
I
don't
know
it's
gonna
work
yet
right,
so
so
we're
gonna
plug
it
in
there
we're
gonna
see
you
know.
If
this
build
will
succeed-
and
you
know
I
kind
of
go
from
there
and
troubleshoot
this
week
accordingly.
B
But
yes-
and
I
think
the
important
piece
of
this
thing
is-
I
mean
we're
looking
at
actions
because
it's
quick
to
work
with
and
quick
to
kind
of
switch
stuff
out,
but
the
same
sort
of
techniques.
So
I've
got
some
kind
of
error.
In
my
code,
it's
using
a
library
out
there
we're
using
an
action.
Just
it's
easy
to
see
the
components
and
see
what's
in
there
and
you
don't
know
a
lot
of
fancy
languages
here,
but
that's
true
of
any
third
party
open
source
code.
B
B
C
B
No,
I
don't
know
so.
My
guess
is
all
this.
So
all
of
this
action-
I
I
will
tell
you
a
couple
things
about
this,
so
this
is.
This
is
kind
of
a
workflow.
My
guess
is
that
whoever
put
this
slide
heroes
repository
together
did
this.
You
know.
Did
this
initially,
my
guess
is:
they
must
be
using
some
fancy,
jekyll
plug-in
and
doesn't
have
to
be
too
fancy
just
a
plug-in
to
do
like
tags.
Github,
standard,
jekyll
stuff
doesn't
support
tags
in
an
easy
way.
B
There's
a
lot
of
yucky
work
around
stuff,
but
there
are
jekyll
plugins
that
can
do
tags.
If
you
want
to
do
it,
you
got
to
kind
of
build
yourself,
so
my
guess
is
slide.
Heroes
wanted
tags
used
a
plugin
built
a
little
action
here.
That
would
actually
go
ahead
and
run
jekyll
independently
and
then
do
the
upload
to
get
on
pages
that
hilally's
action
does
both
of
those
things
at
one
time.
I
know
that
from
looking
into
it
earlier,
so
it
does
the
jekyll
build
pushes
to
get
on
pages.
B
B
Yeah
all
right:
okay,
jekyll
action,
ruby,
2.6,
okay,
great,
so
I've
typed
some
stuff
in
a
web
browser.
Let's
save
our
changes
and
you
know
in
the
world
of
github
we
are
going
to
start
a
commit
for
this.
Okay.
Now
we're
going
to
see
more
of
this
in
a
second.
But
I'm
going
to
put
a
comment
in
here,
which
is
yeah
sure
we
updated
jekyll,
but
try
to
fix
the
build.
B
I
don't
know
if
anybody
remembers.
This
whole
started
with
an
issue
that
we
were
tracking
down
way
back
when
whenever
I
want
to
refer
to
an
issue,
you
know
you
type
the
pound
sign
and
then
we've
got
some
help
to
figure
out
what
other
issues
are
there?
How
to
get
up?
I
just
type
pound.
I
see
12
bug
broken
build
if
I
remember
correctly,
and
I'm
sure
I've
got
it
open
in
the
tab
here.
That
was
the
bug
that
we
were
really
working
on.
B
A
B
B
But
when
I
go
ahead
and
make
a
you
know,
code
change
at
this
point
I
may
or
may
not
have
the
ability
to
kind
of
write
to
this
repository.
I
do
because
I'm
in
universal
exports,
first
down
the
job
and
all
that
stuff.
If
I
didn't,
I
would
have
to
fork
and
make
a
copy
of
this
to
be
able
to
go
in
and
save
it
either
way.
B
And
a
couple
of
things
here
should
happen
here
in
a
minute,
so
one
is
perfect.
Okay,
so
I've
saved
that
and
that's
all
great,
and
since
I
have
right
access
to
repository,
I
can
do
that,
but
that
that's
not
really
going
to
be
ideal.
I'm
off
on
this
broken
build
task
itself.
What
I'm
going
to
actually
want
to
do
here
is
put
a
pull
request
in
place,
so
let
me
go
ahead
and
hit
this
compare
and
pull
request,
and
then
let
me
talk
about
what
this
different
branch
thing
is
here
for
a
minute.
B
B
B
B
If
I
was
working
out
with
halali's
action
or
repository,
I
don't
have
access
to.
I
would
fork
to
get
a
copy
of
that
code
base
that
I
can
work
with,
and
you've
probably
seen
that
button
over
on
the
top
right
and
a
fork.
This
gives
me
a
copy
of
that
repository
then
that
I
can
that
I
can
work
with
directly
to
go
ahead
and
get
started
and
make
those
changes.
B
We
want
to
go
ahead
and
create
a
branch,
and
in
this
case
this
is
exactly
what
we've
done,
and
I
did
that
actually,
before
we
hopped
on,
I
created
a
branch
here
called
12
broken
build
that
allows
that
keeps
what
I'm
doing
separate
from
master
separate
from
potential
breaking
changes
or
anything
like
that.
That's
happening
out
there
against
my
own
set
of
of
what's
going
on.
B
I
can
mess
stuff
up
here
at
will,
to
some
degree,
okay,
or
I
should
say
I
can
mess
stuff
up
without
messing
up
stuff
for
everybody
else,
so
I've
done
that
add
some
commits
I've
done.
I've
done
that
right.
We
went
ahead
and
sat
there
found
that
other
action
over
there
saved.
That
said,
okay,
let's
try,
this
action
see
how
it's
going
to
work
and
now
we're
here.
B
This
is
the
part
of
the
picture
where
natalie
learns
of
my
existence
and
learns
that
I've
been
working
to
help
out
with
this
project.
Okay,
the
pull
request
here
is
a
piece
where
it's
like.
Hey
I've
made
some
changes
to
the
code.
I
think
they're
gonna
be
okay.
Let
me
tell
you
what
I
did.
Let
me
tell
you
why
I
did
and
then
that
pull
request
goes
back
up
to
the
repository
where
she
can
get
into
the
picture
where
she
can
see.
B
What
that
looks
like
here
is
you
know
this?
I
hit
that
button
earlier,
let's
open
a
pull
request,
I'm
going
to
go
ahead
and
type
some
comments
in
here,
because
it's
hard
for
me
to
type
and
talk
at
the
same
time,
I'm
actually
going
to
paste
some
comments
in
here,
but
this
pull
request.
Fixes
number
12.,
you'll,
remember
number
12..
Let's
give
this
a
better,
a
better
title
here,
which
is.
B
Okay,
yeah,
that's
a
so-so
title
for
your
pull
request,
but
that
I
think,
will
will
get
us
in
the
picture
notice.
A
couple
of
things
features
of
this
of
this
pull
request.
One
is
I
go
ahead
and
link
it
out
to
that
issue
to
number
12
itself
notice?
Secondly,
I
am
using
one
of
these
superpower.
Keywords
fixes
will
mean
if
this
code
gets
accepted.
B
Secondly,
these
two
are
going
to
be
linked
when
I
submit
this,
so
there'll
be
a
record
from
the
issue
to
the
pull
request
and
the
code
that
changed.
That's
pretty
great
for
traceability
perspective.
That's
pretty
great!
You
know
for
future,
you
who
will
forget
what
past
you
has
done.
Believe
me,
it's
pretty
pretty
handy.
The
other
thing
here
is
that
I
will
say-
and
again
I
just
pasted
this
in
I
went
in
for
kicks.
B
I
really
wanted
to
say:
hey
here's
where
we're
getting
this
code,
because
it
is
somebody
else's
code
and
do
we
have
policy
around
that?
I
don't
know
my
boss
should
have
told
me,
maybe
there's
something
I
should
have
read
that
I
haven't
read
yet,
because
I'm
trying
to
dive
in
and
add
some
value
and
fix
the
problem
right
away
that
will
at
least
allow
natalie
or
anybody
reviewing
this
code
to
have
some
idea
of
kind
of
what's
going
on
okay,
so
I
will
go
ahead
and
create
this
pull
request.
B
And
we
have
a
pull
request,
which
is
pretty
exciting,
and
I
will
mention
just
one
other
thing
here
that
I
have
not
done
here
is
not
a
bad
idea
in
the
world
of
a
pull
request.
So
I
I
don't
know
how
this
repository
is
set
up.
I
don't
know
if
natalie
would
be
notified
automatically
about
this.
I
think
she's
going
to
tell
us
that
in
a
sec,
but
if
I
knew
here
somebody
on
the
team
who
would
be
a
good
person
to
review
that,
I
can
choose
somebody
here.
B
Natalie,
if
I
knew
her
or
whatever
that
that
would
go
ahead
and
be
alerted
that
this
pull
request
exists
because
I'm
new
guy
on
the
team-
I
don't
know
anybody,
I'm
not
gonna
do
that,
but
in
many
work
type
situations
that
would
be
a
pretty
good
move
and
the
other
thing
I'll
say
is
that
github,
when
it
can,
we
can
suggest
suggested
reviewers.
So
if
it's
a
code
base,
that's
got
kind
of
long
experience.
B
B
I've
kind
of
done
something
and
I've
pushed
some
code
up
there
and
it's
my
first
day
of
work
and
I
haven't
really
read
the
like
the
policy
manual
about
code,
and
so
I
kind
of
hope
I
do
the
right
thing
and
even
more
importantly,
I
hope
somebody's
gonna
like
see
my
code
and
use
it.
So
I'm
kind
of
waiting
like
this.
A
Okay,
so
I
am
thank
you
eric
for
that.
I'm
hanging
out
at
my
desk,
I'm
like
doing
real
work
and
because
I'm
a
maintainer
of
that
repository
and
I
do
have-
I
am
watching
it-
I
do
get
notifications
and
boom.
I
got
a
notification
that
says
I've
got
a
pull
request
in
my
slide
heroes
repository
now.
Hopefully
you
guys
can
see
my
screen.
A
I
realize
I'm
on
the
wrong
branch
here
for
this
okay,
so
awesome.
Yes,
I
have
a
pull
request.
I
go
to
that
tab
and
check
it
out
and
sure
enough.
It's
a
pull
request
submitted
by
someone,
I'm
not
familiar
with
that
is
requiring
my
review,
but
it
is
to
update
our
build
action
to
avoid
a
avoid
failing,
so
I'm
gonna
open
that
pull
request
up
and
when
you
open
a
pull
request.
It
takes
you
to
the
conversation,
which
is
where
someone
says
hey.
I
think
I've
done
a
cool
thing.
A
This
is
what
I've
done.
It
starts
the
conversation
that
you
can
have
back
and
forth
with
this
person
around
those
commits.
So
I've
got
it
fixes
number
12,
which
I
recall
is
the
failed.
The
failed,
build
and
he's
taking
a
new
dependency
from
here,
which
we'll
see
more
information
about
and
yay.
He
seems
pretty
excited
about
it.
So
I
too,
I'm
excited
right
now.
B
B
A
So
a
review
is
quote
required,
but,
as
eric
noted,
all
the
checks
have
passed.
It's
just
the
merging
is
blocked
because
I've
got
to
do
a
review.
So
I'm
going
to
go
back
up
here
and
look
at
files
change
files
changed
is
taking
that
conversation
of
what
he
did
and
allowing
me
to
see
it
in
the
actual
code.
So
this
is
a
split
screen
that
shows
on
the
left
side
what
the
code
was
and
on
the
right
side
what
it
is
now
so
it'll
show
the
things
that
he
has
fixed.
A
What
we've
got
here,
though,
is
why
am
I
not
seeing
where
your
file
is?
It's
not
rolling,
okay.
Well,
I
saw
that
the
fix
that
the
build
worked.
So
I
am
going
to
trust
my
intuition.
I
am
going
to
approve
this
and
submit
the
review
once
that
goes
through.
It
takes
me
back
to
the
conversation
page
and
again
it
says
the
changes
were
approved.
A
All
the
checks
were
passed,
there's
no
conflicts,
so
I'm
going
to
merge
the
pull
request
again.
It
gives
me
a
little
note
that
says
this
is
what's
going
on
and
I'm
going
to
confirm
that
at
this
time
I'm
actually
going
to
go
back
to
the
actions
page
and
watch
the
build,
so
red
x's
are
bad.
Green
checks
are
good,
yellow
means
things
are
happening,
so
I
am
going
to
wait
for
this
to
go
through
to
confirm
that
everything's
awesome.
A
While
this
is
building
worth
noting
to
everybody.
The
value
of
what
you're
kind
of
seeing
here
is
I'm
getting
work
done
on
my
behalf
from
brain
power
outside
of
my
small
little
project
team.
Working
on
this
eric
is
also
testing
out
skills
he's
trying
something
new
meeting
new
people
which
you'll
kind
of
get
a
sense
of
as
this
completes,
but
it's
really
building
a
collaborative
environment
within
your
organization
or
even
just
in
open
source
repositories.
A
C
Can
I
ask
you
a
quick
question
here,
so
it
seems
like
you
know,
a
lot
of
folks
have
been
doing
the
same
thing
within
their
code
base
right,
so
they'll
leverage
open
source
code.
Are
you
saying
that
I
can
leverage
people's
code
for
not
only
my
code
but
for
the
building
and
the
testing
processes?
Basically,
for
my
ca,
cicd
process.
A
Absolutely
it's
the
the
joy
of
open
source
right.
It's
leveraging
what
exists,
what
works
and
bringing
that
into
the
fold.
I
will
say,
though,
if
you're
using
something
open
source
and
bringing
it
internally,
you
just
want
to
verify
what
your
organizational
policies
are.
If
it's,
if
you're
allowed
to
use
it,
if
it's
not
vulnerable,
who
manages
it
and
maintains
it
securely,
but
absolutely
so,
okay,
so
the
real
test.
Now
we
saw
the
pull
request
is
merged.
We've
got
a
green
check,
which
is
awesome.
A
I'm
going
to
go
back
to
my
actual
code
page
and
look
and
see
sure
enough.
The
batch
has
changed.
It's
now
passing
I'm
going
to
go
to
my
issues
and
I'm
going
to
the
issue's,
not
even
there,
because
eric
look
he
closed
it
issue
12
moved
automatically
to
close
he's
doing
cleanup
for
me
on
my
behalf.
This
is
super
awesome,
so
I
might
as
a
separate
note,
I
might
now
send
erica
slack.
A
B
Well,
I
gotta
say
this:
I
mean
first
day
pull
request,
accepted,
look
at
that,
it's
been
merged.
Can
you
see
it?
Do
you
see
the
purple
on
there?
It's
been
merged.
This
is.
This
is
great.
This
is
just
terrific
and
you
know,
and
again
in
in
particular,
here:
okay,
so,
oh
okay,
so
natalie
approve
these
changes.
Great
again,
we
can
see
the
changes
here.
Details
notice
here
that
there's
a
place
for
sort
of
common
conversations,
so
natalie
was
showing
around
okay
want
to
prove
the
code
or
not
or
put
line.
B
You
know
specific
comments
on
specific
lines
of
code
in
there
if
you
need
to,
but
there's
also
an
opportunity
here
just
to
talk
about
the
pull
request
generally,
and
that
can
sometimes
be
very,
very
helpful,
particularly.
You
know
in
the
case
of
this
one
natalie,
you
mentioned
organizational
priorities
here
and
and
policy,
and
that
kind
of
thing
like
is
it
okay
to
just
pull
in
l
studios
action
you
know:
do
we
need
to
instead
fork
that
action
make
that
change
into
something
here?
B
That
belongs
to
belongs
to
it's
still
a
public
repository,
but
it's
just
a
fork
here
in
universal
exports.
That's
the
kind
of
stuff
that
you
can
talk
about
in
a
code
record.
You
know
in
a
pull
request
and
a
code
review,
or
you
can
talk
about
it.
You
know
right
here,
but
I
gotta
say
I
am
just
you
know
thrilled
here
that
this
you
know
that
that
that
that
my
that
the
thing
that
I
did
here
on
my
first
day
made
it
into
the
code
base
that
is
really
really
really
cool.
B
Again
kind
of
you
know
big
picture
where,
where
we
left
off
with
me,
I
just
put
that
pull
request
in
okay.
Again,
what's
a
pull
request,
it's
a
bunch
of
changes
on
a
branch.
You
know
on
that
feature:
branch.
A
bunch
of
code
changes
an
explanation
of
what
I
was
doing
conversation
around
it
conversation
around
it
right
so
so
had
natalie
had
code
review
comments.
B
Had
there
sort
of
been
general
comments
here,
we
can
have
that
kind
of
discussion
and
then,
ultimately,
here
an
approval
which,
in
our
case
with
github
actions,
goes
on
and
once
that's
merged
because
of
the
way
our
actions
are
set
up.
That
will
go
ahead
and
deploy
and,
in
this
case,
update
our
github
pages
website.
B
A
A
We
plan
to
talk
about
small
features
and
things
like
discussions
when
to
use
a
discussion
instead
of
an
issue
or
when
to
use
a
discussion
instead
of
an
issue
and
a
slack
thread,
those
kind
of
things
to
really
make
your
collaboration
more
effective
and
your
experience
with
github
even
more
awesome.
So
unless
there's
anything
left
in
the
chat,
there
is
a
link
below.
A
I
believe
it's
not
what
you're
supposed
to
do
other
thing:
there's
a
link
below
for
the
actual
next
demo
info
or
to
subscribe,
so
awesome
anything
left
in
the
chat
before
we
hang
up
or
does
anybody
have
any
other
random
questions
where
you
got
three
experts
here,
we're
happy
to
answer
anything.
While
we
have
a
few
minutes.