►
From YouTube: 20 Demo Days EMEA Collaborative Coding
Description
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
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
Well,
welcome
to
the
github
live
stream,
so
my
name
is
richard:
I'm
a
solutions
engineer
here
at
github,
based
in
the
uk,
looking
after
uk
customers,
currently
in
lockdown
2
in
the
southwest
of
england,
I'm
joined
today
on
biking
vocals,
my
colleague
sebas,
who
is
sitting
over
there
in
amsterdam
and
will
be
on
the
chat
for
us
today.
So
if
you've
got
any
questions
as
we
go
through
hit
us
up
in
the
chat
I'll
answer,
the
easy
ones
sebas
will
answer
the
the
difficult
ones.
It'll
be
it'll,
be
fun.
A
If
you
want
to
hit
us
up,
let
us
know
what
you're
kind
of
dialing
in
from
where
you're
watching
from
anything
you
want
to
see
in
particular,
today
we're
reasonably
flexible
and
what
we
can
we
can
talk
about.
We've
got
a
plan,
but
if
we
want
to
change
that,
then
absolutely
we
we
can
so
we're
going
to
cover
a
collaborative
coding
with
github
today
and
it's
kind
of
an
interesting
one.
A
Most
people
will
be
coming
out
of
university
or
college,
doing
a
computer
science
degree
or
software
engineering
and
almost
certainly
will
have
used
github,
for
course,
work
and
so
on.
But
some
of
the
times,
maybe
some
of
those
collaborative
features
working
in
a
team.
How
can
we
work
well
together,
working
on
open
source
projects?
A
Maybe
some
of
those
features
you're
not
quite
getting
getting
a
handle
on.
So
I
think
today,
what
we're
going
to
do
we're
going
to
cover
a
little
bit
of
the
that
functionality.
As
you
say
anything
you
want
to
see
anything.
You
want
to
talk
about,
here's
up
in
the
chat
and
we'll
we'll
absolutely
make
sure
we
follow
that
excellent.
Okay,
let
me
get
some
my
screen.
A
So
hopefully
well
people
may
have
seen
this
before.
This
is
what
we're
gonna
use
for
our
our
kind
of
walk
through
today,
my
autocad.
A
Now,
if
you've
gone
to
any
conferences
and
met
any
of
the
the
github
team,
you'll
know
that
we
love
stickers,
we
love
our
octocats
and
what
you
can
do
you
can
go
and
hit
my
octocat.com
and
you
can.
You
can
start
to
play
with
this
right
now,
so
it's
kind
of
fun.
So
again
you
can
dive
through.
We
can
design
our
own
octocat.
You
can
save
that
off.
Some
people
actually
have
them
print
it
into
into
stickers
as
well.
A
But
if
we
get
started
in
that
you
can,
you
can
start
to
build
up
your
your
own
autocad.
A
Let's
go
so
again,
you
can,
I
don't
go
and
change
the
the
face.
Color,
you
can
go
and
stick
some
eyes
in
there
get
some
facial
hair.
So
again
you
can
go
and
absolutely
have
a
little
play
with
that
and
build
up
your
own
one.
I
wish
twitch
allowed
us
to
post
pictures
in
the
chat,
otherwise
that
I'd
say
go
and
build
your
your
best
one
anyway,
so
we're
gonna
use
that
for
our
our
demo
today.
This
is
a
little
repository.
A
It's
sitting
in
our
demo
organization,
we've
called
octo
twitch
and
what's
interesting
about
this.
This
is
a
source
for
meyer
to
come,
so
you
can
again
go
and
start
changing
things
up
in
there.
But
what's
nice
with
this,
is
it's
also
set
up
using
github
pages?
A
So
if
you
were
to
hit
octodemo.github.io
up
to
twitch
you're,
actually
seeing
the
the
the
version
of
the
my
autocad,
that
is
in
my
repository,
so
what
we're
going
to
do
is
we're
going
to
make
some
changes
to
that
and
saying
we'll
work
with
sabas
on
on
on
making
some
changes
we'll
get
those
published
up
in
to
that.
So
we'll
be
able
to
see
those
changes
coming
in
there,
okay,
so
let's
kick
off
with
this.
A
We're
not
gonna
go
too
heavily
into
the
code,
that's
kind
of
not
really
what
we're
too
interested
in
today,
but
if
I
just
zoom
out
a
little
bit,
we
can
see
this
this
repository
and
again
it's
a
little
node
application,
not
too
important.
How
that's
that's,
working,
we'll
just
make
some
code
changes.
A
A
Now,
a
lot
of
you
who
may
be
working
in
teams
will
be
forced
into
using
whatever
the
company
is
using.
So
if
we're
tracking
work,
we
might
be
using
something
like
jira
as
your
boards
trello
might
be
in
an
excel
spreadsheet
or
if
you're
like
me,
it's
probably
scribbled
down
on
the
on
the
back
of
an
envelope
or
something
whatever
happens
to
be
on
your
desk.
A
But
if
you
want
within
github,
you
have
a
a
full
issue
tracking
system.
We
can
look
at
our
project
boards.
We
can
track
our
work
as
we
move
through
that.
So
what
I've
done
here
is
I've
got
a
project
board
and
if
I
wanted,
I
can
have
multiple
project
boards
so
absolutely
go
ahead.
You
can
hit
new
project.
A
We
can
give
that
a
name,
and
then
the
important
thing
here
is
the
template
that
we're
going
to
use.
So
you
can
see
there
are
a
number
of
these
that
you
can.
A
You
can
choose
from
so
we've
got
things
like
basic
kanban
if
anybody
loves
their
their
cam
and
really
simple
way
of
tracking
our
progress
making
sure
we
don't
have
too
much
work
in
progress
and
that
we're
concentrating
on
getting
things
completely
finished
rather
than
moving
on
to
the
to
the
next
thing,
and
of
course,
with
this,
we've
got
things
like
automated
kanban
bug,
triage
and
so
on.
A
So
we
can
choose
one
of
these
and
it
will
go
off
and
it
will
generate
a
board
that
we
can
then
customize
if
we,
if
we
want
so
I'm
just
going
to
go
back
to
the
the
board
that
I
I
created
here,
see
that
we're
going
to
title
we've
got
some
progress,
so
we've
got
a
couple
of
things
that
we've
done
a
couple
of
things
in
progress
and
a
few
things
that
still
have
to
be
completed.
A
So
when
we
dive
into
that,
you
can
see.
This
is,
if
I
remember
correctly,
is
using
the
kanban
with
automation.
It
gives
us
a
number
of
columns,
so
we've
got
to
do
in
progress,
review,
reviewer,
approved
and
done
so
each
of
these
things
we
can
customize.
If
we
wanted,
we
can
move
across
here
we
can
go
and
add
ourselves
a
column.
Let's
say
we
want
it.
Maybe
a
testing
column.
A
Absolutely
we
can
add
one
in
drag
it
in
and
move
our
work
through
that
each
of
these
things
that
we're
looking
at
here
are
typically
github
issues.
Now,
github
issues
very
simple:
oh
look
at
that
marvelous,
as
if
by
magic,
sebas
has
gone
and
added
us
a
little
note.
So
again,
any
of
these
things
in
a
column
are
typically
given
of
issues.
A
They
could
be
linked
to
pull
requests
we'll
look
at
later,
but
they
could
also
just
be
notes
almost
like
sticky
notes,
they're,
not
a
full
issue
in
there,
but
I
just
want
to
track
something.
So
I
could
take
an
issue
here.
I
can
move
that
to
in
progress
and
we
can
drag
it
across
so
again,
the
stuff
that
we
want
to
concentrate
on
so
be
interested
to
know
in
in
the
chat
if
what
other
people
are
using.
A
So
if,
if
you're
using
something
like
jira
your
boards,
whatever
it
might
be,
what
are
you
constantly?
What
are
you
currently
using?
So
again?
There
may
be
a
a
mix
of
integrating
github
issues
with
an
existing
system.
So
again,
you
might
find
that
the
the
business
are
using
jira,
they're
tracking,
all
that
work
there,
but
when
we
get
down
to
doing
something
in
the
dev
team,
you
know
we
don't
necessarily
need
something
that
heavyweight.
We
want
to
go
and
use
issues
and
we
have
options
to
integrate
those
we
can.
A
A
So
just
looking
and
then
hi
giselle
yeah,
absolutely
with
these
all
these
live
streams
are
going
to
be
available
later
on,
so
we're
gonna,
stick
those
on
to
onto
youtube,
so
absolutely
you'll
be
able
to
catch
this
later
on
we'll
link
it
up.
A
Okay,
so
looking
at
this,
we've
got
our
our
issues
here,
one
of
the
other
things
we
put
down
here
to
to
manage
this
this
column.
What
we're
thinking
of
doing
is
adding
some
automation
around
this.
So
when
we
create
a
new
issue
within
github,
then
we'll
enhance
here
say,
move
issues
here
when
it's
newly
added,
which
means
we
create
a
new
one.
It
turns
up
in
this
this
to
do
column,
as
you
might
expect,
and
then
all
the
other
columns.
A
For
instance,
if
we
go
to
in
progress
when
something
is
reopened,
it's
going
to
move
across
there
when
something
is
is
complete.
So
again,
if
we
move
right
across
we'll
manage
that
when
it's
closed,
of
course,
it
will
move
into
the
the
done
column.
So
again,
we
can
really
build
up
some
automation
around
this.
A
If
we
want,
you
can,
of
course,
filter
these
things,
so
I
might
say
something
like
I
just
want
to
say:
let's
do
a
tag
and
I
should
label
and
we'll
do
something
like
bug
and
again
just
show
me
all
the
bugs
on
the
board
at
the
time.
So
again
we
can
walk
through
and
have
a
look
at
that
the
menu
over
here.
If
we
want,
we
can
see
all
the
activity
so
anything
that
I
move
so
there's
the
piece
of
work
that
I
just
done
a
few
seconds
ago.
A
We
can
interact
with
that.
So
again,
if
you
are
maybe
off
of
the
day,
you
want
to
know
what
happened
in
the
project.
You
can
pop
over
to
the
project
board,
look
at
the
activity
and
see
what
people
have
been
working
on,
what's
been
completed,
and
so
on
so
again
really
really
useful
for
that.
Each
of
these
things
that
we
are
looking
at
on
the
board,
if
they're,
not
just
a
a
label
or
a
a
note,
then
it
will
actually
be
an
issue
on
each
of
those
issues.
We
can
get
a
little
preview
here.
A
We
can
see
who
has
been
assigned
to
who
created
any
other
information
in
there
and
we
can
obviously
go
to
the
the
full
issue
as
well.
Let
me
clear
my
little
filter
here
now.
The
one
that
we
want
to
work
on
today
is
we're
gonna.
Add
a
custom
welcome
sign,
so
we
saw
we
saw
that
my
autocad
and
we
want
to
go
and
add
a
nice
little
welcome
sign
to
it.
A
So
we're
gonna
go
and
do
that
now,
so
we're
gonna
set
that
to
be
in
progress,
we'll
stick
it
at
the
top
and
we'll
dive
into
that
that
issue.
So
again,
let's
go
and
view
the
full
issue,
and
we
can
see
all
the
information
that
we
need
about
that
we're
going
to
assign
ourselves
I'm
going
to
need
some
help
with
this.
So
of
course,
I'm
going
to
assign
my
good
buddy
sebas.
A
Let's
stick
him
in
as
well,
and
so
we're
adding
multiple
people
to
this
issue
so
we're
effectively
having
multiple
signees
because,
again
we're
gonna
we're
gonna
pair
in
this
we're
going
to
work
on
it
together
again
any
other
labels.
I
want
to
add
to
this.
This
is
actually
using
an
issue
template
so
again,
if
there's
something
like
say
a
bug
report
or
somebody
has
a
feature
request
for
the
project.
We
can
create
a
template
for
that
issue,
which
means
when
they
create
it.
A
It
has
a
form
for
them
to
fill
in
with
all
the
information
that
we
need.
So
again,
you
can
really
start
to
make
use
of
this
stuff.
Okay,
so
we've
now
we've
now
got
our
project
board
going.
A
We've
got
this
issue
that
we
need
to
to
start
working
on,
and
that's
that's
the
next
thing
we're
going
to
do
so
we're
going
to
flip
over
to
our
code
here
now
this
happens
to
be
a
again
a
node
application
and
yeah,
you
know,
maybe
maybe
my
machine
is,
is
nicely
set
up
to
go
and
work
with
this,
but
at
the
same
time
I
might
not
have
all
the
dependencies
and
I'm
gonna
have
to
go
start
installing
things
I
might
not
even
be
on
my
my
local
machine,
but
I
want
to
contribute.
A
A
So
if
you've
been
sort
of
looking
at
some
of
the
announcements
around
github
recently,
you
may
have
heard
of
github
code
spaces,
and
so
with
this
this
code.
Of
course,
I
can
clone
it
to
my
to
my
local
machine,
but
you
know
again,
maybe
I'm
not
ready
to
to
go
and
do
that.
So
what
we
have
here
is
the
option
to
open
up
this
in
a
codespace.
A
Now
codespace
is
effectively
a
completely
self-contained
container
image,
with
visual
studio
code,
all
the
dependencies
I
need
on
there
and
basically
ready
for
me
to
start
going
and
working
on
this
stuff.
Now
the
one
that
I've
got
here
if
I
go
and
just
click
on
that
to
open
up
what
we'll
see
is
it's
it's
something
spun
up
already
looks
a
bit
blank
at
the
minute,
but
it
is
effectively
showing
me
visual
studio
code
and
it's
set
up
for
me
to
go
and
work
on
this
this
project.
A
So
that's
going
off
and
loading
some
things
and
over
on
the
left
hand
side
here,
you
can
see
all
the
extensions
that
I
might
need
to
to
work
with.
So
we
can
see
things
like
docker.
We
can
see
the
github
extension
to
visual
studio
code,
obviously,
if
we've
got
gates
and
so
on
in
there,
if
you
want,
you
can
start
to
build
up
that
container
image
yourself.
So
what
does
this
look
like?
What
dependencies
do
we
need
on
there?
A
So
if
someone
is
in
the
company-
and
you
know-
maybe
it's
not
their
core
thing-
maybe
they
don't
work
on
this
project
all
the
time,
so
they
can
may
not
be
set
up
to
work
on.
So
you
can
now
build
a
code
space
which
effectively
allows
anybody
to
come
along
open
up,
essentially
a
an
image
that
would
allow
them
to
contribute
to
this
project.
So
again,
when
we're
thinking
about
really
trying
to
drive
that
open
source
culture
within
within
the
business,
then
cold
spaces
is,
is
really
going
to
help.
Actually
do
that?
A
Okay,
anybody
in
the
chat
anybody
has
anybody
had
a
little
play
around
with
code
spaces.
There's
been
a
few
sessions
recently
on
on
the
twitch
stream
on
on
codespaces.
Has
anybody
had
a
little
play
around
with
this
yet.
A
I'm
hoping
you
all
say
no,
because
then
I
can
show
you
some
of
the
cool
stuff
and
you
won't
have
seen
it
before
so
I'll.
Look
extra
extra,
good,
okay
right,
so
we
were
sitting
in
the
the
repository
we
fired
up
this
this
code
space
and
again
we're
looking
at
a
blank
page
right
now.
But
let's,
let's
look
at
what
we've
got
here
again.
Let
me
zoom
a
little
bit,
so
you
guys
can
see
that
better.
A
So,
as
I
mentioned
down
the
left-hand
side,
we
can
go
and
view
all
the
files.
So
look
we're
looking
at
this,
so
here's
my
index.html,
which
again
we're
just
looking
at
the
code
immediately.
I
can
start
working
with
this
and
again
because
it's
visual
studio
code,
I've
got
all
my
syntax
coloring.
A
I
can
start
to
to
work
with
this
really
really
easily.
I've
got
my
get
extension
here,
so
I
can
see
any
changes.
If
I'm
not
maybe
too
comfortable
with
get
from
the
command
line,
then
absolutely
you
can.
You
can
use
the
extension
again,
maybe
just
take
away
some
other
heavy
lifting.
If
you
want.
We've
also
got
the
the
github
extension
here.
So
again
we
can
start
to
look.
Oh
look
here.
We
go
straight
away.
I've
got
my
my
issue
that
was
assigned
to
me
to
add
the
custom
welcome
sign.
A
I
can
see
if
I
have
any
pull
requests
open
in
a
minute.
So
again,
I'm
interacting
with
github
directly
from
visual
studio
code.
Now,
if
you're
using
visual
studio
code
locally.
Of
course
you
can
do
all
this
as
well,
but
I'm
just
having
to
not
having
to
effectively
build
this
up
and
have
it
in
a
in
a
configure
it
so
that
it
works
with
this
project.
So
it's
all
set
up
ready
for
me
to
go.
A
But
again,
if,
if
you
want,
you
can
use
visual
studio
code
on
your
local
machine,
what
you
can
also
do
is
take
visual
studio
code
on
your
local
machine
and
connect
to
this
code
space.
So
again,
if
you
don't
have
everything
set
up
locally,
you
can
actually
go
and
connect
to
this,
but
still
work
on
your
your
local
vs
code.
A
Okay,
so
you
know
I
kind
of
suck
at
being
a
developer,
so
I'm
going
to
dig
sebastian.
Tell
me
much
better
than
me.
First
thing
I'm
going
to
do
is
say
I
could
go
and
create
a
branch
so,
but
I'm
just
going
to
quickly
create
one
of
those
from
the
terminal
here.
So
we'll
just
do
good
check
out
I'll
do,
b.
A
Meaningful
so
we're
going
to
switch
to
our
new
browser
so
now
we're
ready
to
go
and
start
working
on
this.
But
again
I
need
some
help
in
this.
So
let
me
flip
over
to
this,
which
is
totally
my
favorite
little
extension.
This
is
the
vs
code,
liveshare
again
totally
available
for
you
to
use
on
prem.
Now
I've
got
some
recent
contacts
in
here
and,
of
course,
sebas
and
I
were
working
together,
so
I
could
actually
go
and
start
a
little
chat
session
with
him.
A
So,
let's
see,
if
he's
around-
oh
there's
us
talking,
you
know
hey.
A
A
There
we
go
marvelous
so
sebas
is
in.
We
can
start
to
absolutely
enthusiastic
response.
So
what
we're
going
to
do
is
right
down
here,
so
we
could,
if
we
want,
go
and
effectively
send
an
email
or
a
message
to
sabbas.
I
could
copy
a
link
to
this.
What
I
can
I
can
do,
if
I
like
is
just
say,
yeah,
let's
go
and
invite
that
contact
to
to
join.
A
A
Now
we
just
see
if
has
joined
there,
we
go
says
joining,
might
actually
be
so
if
sebas
is
successfully
joined,
then
we
should
be
able
to
see
effectively
what
we're
doing
and
there
straight
away.
I
can
see
that
as
ambassador's
in
adding
some
code,
it's
marvelous,
so
I'm
not
having
to
do
anything.
He
can
go
and
add
this
and-
and
he
needs
to
get
his
angle
brackets
correct
on
that
marvelous
and-
and
so
that's
that's
great.
No,
we
could
absolutely
code
together
again.
A
This
is
like
you
know,
you're
putting
a
presentation
together
or
something
we
can
work
we
can.
We
can,
we
can
chat,
we
can
be
on
you,
know,
zoom
call
or
a
teams
call
and
and
discuss
this.
So
especially
in
today's
kind
of
logged
out
scenario.
A
We
need
to
be
able
to
work
better
together
and
again
as
much
as
people
probably
hate
pair
programming.
It
is
a
good
way
of
making
sure
that
you're
getting
some
quality
in
that
code.
Look
at
this
man
he's
he's
putting
divs
all
over
the
place
right.
So
again
we
can
do
that
uncle.
But
what
about
you
know?
We
don't
really
want
to
watch
people
code
here,
so
what
we
can
do
is
not
only
share
the
code,
but
I
can
share
my
my
terminal
with
them
as
well
down
here.
A
If
I
give
my
little
option
on
my
live
share,
I
can
also
say:
hey:
go
and
share
the
the
terminal
window.
So
I'm
going
to
do
that
and
we'll
do
it
read
write
so
that
this
mask
can
help
me
now.
What
will
happen?
Is
the
box
will
go
off,
he'll
get
a
request.
If
everything
goes
goes
well,
then
he's
going
to
be
able
to
effectively
run
commands
in
my
terminal.
Now,
if
that
was
my
local
machine,
let's
read
right:
there
we
go.
If
that
was
my
local
machine.
A
I
don't
think
I
want
some
last
running
running
commands
and
things
on
my
terminal,
but
as
it's
effectively
the
self-contained
image,
that's
fine.
You
can
go
ahead
and
run
those
now,
let's
see
if
we're
getting
things
in
is
sebas
successfully
connecting
right.
Try
that
again,
if
not.
A
Let's
say
that
he
is
in
so
we
got
a
shared
terminal
there
yeah,
let's
close
that
one
down.
Let's
do
that
we'll
show
that
terminal
again.
Let's
do
redirect.
A
Oh
that
looks
look
at
that
marvelous
second
time,
second
time
lucky
on
that,
so
we've
actually
showed
this
up.
Now,
as
we
say,
you
don't
want
to
watch
us
code
here.
So
what
we've
got
is
a
little
script
that
will
go
and
add
some
changes
to
this
and
effectively
add
us
a
nice
little
image
and
and
make
some
little
tweaks
to
that.
So
sebas
is
running.
That
he's
got
a
welcome,
sign,
that's
going
to
say,
twitch
he's
going
to
say
yeah!
A
I
don't
want
to
commit
those
those
changes
yet
and
he's
not
going
to
push
those
changes.
So
the
little
script
has
gone
off
and
it's
done
its
thing
now.
A
You
can
see
straight
away
over
here
on
the
only
the
get
extension
is
saying:
hey,
there's
a
couple
of
things
that
have
changed
and
in
fact
it's
gone,
yeah
co-authored
by
sebas
and
we've
added
that
in
and
of
course,
if
we
now
go
and
look
at
the
the
index,
we
can
see
that
it
said:
hey,
build
your
own
or
build
your
very
own
octocat.
So
it's
made
those
changes
so
now,
there's
there's
different
things
that
we
could
do
here.
A
Of
course,
I
could
just
add
the
the
commit
at
the
command
line.
I've
got
my.
If
I
do
my
command
shift
p
again,
you
can
do
git
commit
here
or
if
you
want,
you
can
just
simply
use
the
the
extension
for
that
as
well.
A
So
we'll
go
and
give
it
a
bit
of
that.
We'll
just
leave
the
messy.
Let's
add
in
something
so
we're
doing,
update.
A
Go
and
we'll
go
and
we
will
commit
that.
A
So
those
changes
have
been
made
in
my
local
branch.
Now
I
have
to
get
those
up,
obviously,
to
to
my
repository
and
again
there's
different
ways
that
we
could.
We
could
do
that
so
again.
Just
again,
we
could
do
it
from
the
command
line,
but
this
time
we'll
just
do
it
from
again
command
shift
p
will
get
our
commands
up
there
and
we'll
do
a
push,
and,
I
said:
hey
the
branch
had
welcome,
sign,
there's,
no
upstream
branch.
Would
you
like
to
publish
the
branch?
A
Excellent,
so
we
should
all
be,
should
be
good
there
now
again.
The
next
thing
that
I
want
to
do
so
we're
again:
we've
done
some
pair
programming.
We've
made
our
changes,
we're
happy
with
those,
but
we
need
to
get
some
more
eyes
on
this
and
it's
a
case
of
yeah.
You
know,
maybe
us
together
we're
fine,
but
let's
get
somebody
else
to
review
this.
Let's
make
sure
that
we're
running
some
automated
checks
to
make
sure
that
we
haven't
introduced
any
problems
in
our
change.
A
So
what
we're
going
to
do
is
we're
going
to
submit
a
pull
request
and
I'm
guessing
most
people
will
have
played
around
and
use
pull
requests,
but
we'll
we'll
take
a
look
at
some
of
the
things
that
you
may
or
may
not
have
done
so
again.
If
I
want
to
create
a
pull
request,
I
can
do
this
from
my
little
extension
down
here
or
I
can
do
my
command
shift
p.
In
fact,
there
we
go
create
pull
request
and
I
can
do
that
directly
from
vs
code.
A
A
There
we
go
some
two-factor
authentication
or
some
authentication
marvelous
right,
so
we
were
sitting
in
visual
studio
code
in
our
code
space
doing
all
our
work.
We
we
pushed
the
code
to
our
repository
and
straight
away.
Saying
hey,
add,
welcome,
sign,
has
had
some
recent
changes
and
it's
actually
saying
hey.
Would
you
like
to
compare
and
pull
request?
So
we'll
do
that
again?
Of
course
we
could.
Oh
wow,
I
had
a
an
update,
a
a
spelling
mistake
in
my
in
my
message.
A
There
commit
message,
but
not
to
worry
now,
there's
a
couple
things
you
might
want
to
do
here.
So
again
we
mentioned
we
mentioned
that
we
could
have
essentially
issue
templates
so
for
things
that
where
I
want
to
ensure
that
when
people
are
either
creating
an
issue
or
task
a
piece
of
work
or
they
are
submitting
a
defect
or
a
security
issue,
here
is
an
issue
with
all
the
information
that
I
want.
A
Well,
you
can
do
the
same
thing
for
a
pull
request,
who's
going
to
be
in
that
who's
going
to
be
reviewing
it,
and
you
can
see
here.
One
of
the
bits
down
at
the
bottom
is
saying:
hey
this
pull
request
fixes
number
whatever.
Now
that's
important
for
us.
If
I
flip
to
my
my
issues
here,
we
have
this.
This
issue
that
we
are
working
on
so
rather
add
custom.
Welcome!
Sign!
Now!
A
That's
issue
number
two:
if
we
dive
in
you
can
see
there
issue
number
two,
that's
what
we're
interested
in
and
what
we'll
do
is
we'll
stick
in
this
pull
request
fixes
number
two
and
the
reason
we're
doing.
That
is
the
automation
that
we
built
around
in
our
project
board
we're
actually
going
to
change
the
state
of
this
of
this
issue.
We're
going
to
move
it
across
the
board.
A
You
can.
You
can
just
associate
with
the
the
pull
request
if
you
want,
but
we're
going
to
add
a
little
verb
in
there
say,
fixes
and
again
that's
going
to
move,
hopefully
across
the
board,
into
the
done
column
when
we're
when
we're
ready.
So
I
really
should
add
some
information
in
here.
Let's
say:
welcome,
sign
and
changing.
A
I
don't
know
anyway
right.
My
colleagues
would
kill
me
for
having
such
a
terrible
documented
pull
request,
but
it's
gonna
be
fine.
Okay,
so
again
a
couple
of
things
you
might
want
to
do
here.
There's
a
ton
of
stuff
down
the
right
hand,
side
that
we
might
want
to
do.
You
know
we
could
ask
for
some
reviewers.
You
can
see
here
we're
going
to
look
at
this
in
a
little
bit.
A
It's
saying
at
least
one
person
must
review
this
pull
request
now
again,
that's
important
because
we
don't
want
sort
of
unchecked
code
going
into
our
main
branch
and
potentially
getting
released,
and
somebody
having
this
this
problem.
So
there's
a
bunch
of
things
we
can.
We
can
do
on
down
here,
adding
essentially
metadata
around
this
pull
request
now.
One
other
thing
I'm
going
to
go
and
create
this
pull
request,
but
I
also
have
the
option
to
create
a
draft
pull
request
and
you're
like
well.
What's
a
draft
pull
request?
Why
do
I
need
that?
A
If
I'm
working
on,
I
don't
know
a
little
proof
of
concept?
Maybe
a
demo,
maybe
just
a
spike
in
and
what
we're
doing
here,
we're
gonna,
say:
let's
go
off
and
try
this
thing:
we're
never
going
to
merge
this
code,
we're
never
going
to
put
this
code
and
release
it.
We
just
we're
doing
an
experiment
or
maybe
I'm
a
junior
developer.
A
A
So
what
I
can
do
is
I
can
generate
this
draft
pull
request
and
I
can
start
the
conversation
around
what
we're
working
on,
but
without
actually
making
it
a
full
pull
request
which
we're
going
to
merge
back
into
our
main
branch,
so
a
useful
tool
just
to
get
the
feedback
get
the
the
the
automated
checks
running
against
this
as
well.
You
can
then
convert
it
to
a
full
pool
request
later,
if
you
want,
but
I'm
just
going
to
say,
go
and
create
this
pull
request.
A
Now
it's
going
to
go
off
and
it's
do
a
thing.
It's
going
to
compare
the
update,
welcome
messy
brands
to
the
main
branch
and
and
again
I'm
just
looking
at
my
spelling
mistake
in
my
commit
message,
but
hey
it
doesn't
doesn't
matter
too
much
and
we've
got
a
co-author
now
couple
things
to
look
at
here.
Look
at
this.
We
have
a
a
reviewer.
Sebas
has
been
at
it
as
a
reviewer
and
of
course
that
could
be
anybody,
but
the
reason
he
has
been
added
automatically
is
because
we
have
a
code
owner's
file.
A
Look
at
that
in
a
second
but
effectively
allows
me
to
say.
If
somebody
changes,
I
don't
know
a
javascript
file,
a
c-sharp
file
or
somebody
edits
code
in
this
part
of
the
repository
this
full
or
this
folder
or
whatever.
Then
I
want
them
on
the
reviewers,
because
they
are
the
experts
for
that
area
of
the
project,
they're
the
experts
for
that
language.
A
I
want
them
on
review
my
pull
request,
so
I
can
add
that
code
owners
and
I
can
request
that
a
code
owner
must
review
my
pull
request
so
been
automatically
added
as
a
reviewer.
It's
great.
We
can
see
down
here
that
there
are
some
things
that
are
going
on
and
we're
saying
we
have
some
automated
checks
and
it's
saying:
okay:
we've
got
some
automated
checks
which
have
all
passed.
I
can
see
that
I
have
five
things
that
are
successful,
but
merging
is
still
blocked,
wait
a
minute.
A
Why
is
this
and,
of
course
it's
saying
the
code
owner
must
review
this
code.
Otherwise,
then
it
can
be
happening
now
if
you're
paying
attention
you'll
see
that
it
was
just
a
little
change
that
just
happened.
A
We
had
a
change
requested
now
what's
happened,
there
is
sebas
has
been
notified
that
we
have
some
some
code
that
we've
been
working
on,
he'd
been
notified,
that
a
pull
request
is
requiring
his
review
and
so
as
a
as
a
as
a
good
dev
lead,
he's
gone
off
and
he's
had
a
look
and
he's
not
quite
so
sure,
even
though
he
made
the
changes,
he's
not
sure
about
those,
and
actually
he's
got
some
suggestions
for
me.
Now.
Look
at
that
in
a
second
you
can
see
here.
What's
really
nice
about
this.
A
Is
that
he's
made
here's
my
code
change
and
what
he's
done
is
he
said.
Actually
it
would
be
cool
if
it
had
the
word
awesome
in
there.
Instead,
so
he's
made
this
suggestion,
but
you
can
see
here,
I
can
go
and
commit
that
suggestion
as
well.
So
how
did?
How
did
we
get
there?
What
we'll
do
is
we'll
look
here
at
the
commits
we
can
see.
We've
got
the
misspell
update.
Welcome
message
commit
that
we
just
did.
We
pushed
that
to
generate
this.
This
pull
request.
A
A
So
these
things
are
running
as
part
of
my
pull
request
process
and
we're
going
to
look
at
that
in
just
a
second
and
then,
of
course,
I
can
see
my
files
changed
so
again,
if
I
load
the
diff
on
this,
this
is
an
svg
file
and
what
I
can
do
is
I
can
see
that
things
have
changed
and
I
can
do
oh
well.
Okay,
it's
difficult
to
you
know
when
I
look
at
this.
It
doesn't
really
help
me
too
much.
A
How
do
I
review
what's
changed,
but
here
we
can
get
a
rich
diff
and
I
can
see
oh
cool
we've
changed
some
things.
We
can
change
it
to
a
swipe
view,
so
again,
very
cool.
I
can
go.
Oh
okay,
that's
what
it
was
before
and
as
I
move
that
across
I
can
see,
that's
what
it's
become
is
looking
pretty
good.
So
again,
even
though
we're
effectively
merging
an
svg
file
here,
it's
allowing
me
to
to
almost
do
a
different
on
that
now
down
here.
We've
got
those
those
code
changes
and
again.
A
This
is
like
it's
such
a
simple
feature,
but
it's
really
useful.
You
can
see
here
that
it's
showing
me
in
index.html
those
little
changes
that
were
made
and
you
can
see
this
little
blue
plus.
That's
that's
essentially
showing
up
beside
the
the
code.
Now
what's
happened
is
sebas
has
looked
at
this
and
said
yep.
This
is
cool,
but
maybe
it
could
be
even
cooler
and
he's
made
this
this
suggestion
for
me-
and
I
could
you
know
if
I'm
doing
I
could
say
we're
getting
a
bit
of
a
conversation
going.
A
You
know
you
sure,
and
I
can
I
can
add,
a
single
comment
in
there.
If
I
want
and
and
effectively
what
we
can
do
is
either
commit
those
suggestions
or
I
could
ignore
them.
If
I
want
and
then,
if
I
wanted,
if
somebody
said
what's
the
best
effect
we
did
there
is
he
grabs
this
to
add
a
comment,
but
if
you
click
and
drag
you
can
effectively
comment
or
make
suggestions
on
multiple
lines.
A
So
again,
it
just
allows
you
to
say:
look
this
block
of
code,
this
method
yeah,
I'm
not
so
sure
about
it.
I
do
something
slightly
different.
Add
that
in
again
and
again
we're
getting
a
conversation
going.
So
you
know
a
pull
request,
isn't
necessarily
about
just
reviewing
your
work.
It's
a
conversation.
We
can
have
a
back
and
forth
and
we
can
track
all
of
that,
so
anybody
else
who's.
Looking
at
this
one.
Well,
why
did
you
do
it
that
way?
A
They
can
look,
they
can
see
the
conversation
and
the
and
the
decision
process
that
was
that
was
made.
Now,
let's
look
back
to
the
conversation
view
and
again,
I'm
I'm
pretty
he's
very
sure.
So
I'm
happy
with
that.
So
what
we're
going
to
do
is
I'm
going
to
commit
those.
Those
suggestions
commit
those
changes
and
again
that's
gone
in
there.
We'll
do
the
other
one
as
well
commit
that
or
we
can
have
it
as
a
single
batch.
It
doesn't
really
matter,
and
so
those
things
have
gone
off
and
effectively
added
additional
commits.
A
So
you'll
see
this
in
here.
If
I
go
back
to
my
commits
where
we
had
one
before,
we
now
have
three
commits,
because
I
effectively
committed
those
two
other
changes
now,
because
we
made
those
changes,
it
means
that
our
automated
checks
have
to
run
again
because
well
that
wouldn't
be
right.
If
we
could
make
the
changes
in
here
and
not
have
them
rerun
those
checks,
we
could,
in
theory
have
introduced
a
problem.
It
also
will
invalidate
or
could
invalidate
anybody
who
has
already
reviewed
the
the
pull
request.
A
Because
again
the
code
has
now
changed.
So
you
can
see
all
that's
happened.
Sebas
will
be
required
to
review
again.
We
can
see
that
he
has
now
approved
this
and
we've
got
these
things
running
so
code
scanning,
building,
published
docker
image
and
so
on.
Now
we'll
take
a
look
at
these.
Why?
Why
are
they
running
and
you
know
why
are
they
stopping
me
from
from
actually
going
and
merging
them?
So
if
we
go
back
to
our
repository-
and
we
look
here
at
the
settings.
A
What
we
can
we
can
do
is
effectively
go
and
look
at
the
branches
that
we
have
so
branches
here.
Our
default
branches
is
main
and
we've
got
some
branch
protection
rules
set
up
on
it.
So
if
I
click
on
edit,
we
can
see
what
what
might
we
want
to
do
here
now
protecting
these
matching
branches,
we're
going
to
require
a
pull
request,
reviewed
before
merging
and
we've
said.
Look.
We
only
require
one
review.
Otherwise,
I'd
have
to
pull
somebody
else
into
into
this
demo,
but
so
we
have
one
so
it
is
required.
A
We
cannot
merge
the
code
unless
somebody
reviews
it
which
sebas
has
just
done
for
us.
We
also
here
say
require
a
view
from
a
code
owner
and
that's
that
code
owner's
file,
that's
sitting
in
a
repository
saying
if
it's
this
type
of
file,
if
it's
in
this
area
of
the
project,
these
people
have
to
go
and
review
it.
So
again
you
can
add
that
in
to
your
your
ripple,
then
we
can
say
require
some
status
checks
to
pass.
A
Now
you
can
see
here,
we
don't
have
any
required
status
checks,
but
we
have
some
checks
that
are
running,
but
we
can
choose
in
this
case,
in
this
case
to
say:
yeah.
You
know
we're
just
going
to
merge
it
anyway.
What
we
might
want
to
do
is
add
that
in
and
we
can
see
that
there's
a
bunch
of
these
things
now
these
happen
to
be
github
actions,
workflows,
which
we're
going
to
look
at
just
now,
but
they
could
also
be
as
your
pipelines.
A
It
could
be
jenkins
bills,
they
could
be
well
whatever
you
want
really
and
we
can
add
those
in
and
make
them
make
them
required.
So
we
cannot
merge
this
code
unless
we've
run
our
you
know.
Our
security
analysis
run
our
unit
tests
against
it
and
again
trying
to
put
that
quality
gate
on
the
main
branch
to
make
sure
that
we're
not
going
to
essentially
release
anything.
That
is
somewhat
suspect.
A
A
If
we
make
additional
commits
and
there's
a
bunch
of
things
in
there,
so
really
helpful
to
add
that
on
again
you
can
make
that
as
complex
and
it's
difficult
to
merge
that
code
or
you
can
make
it
super
easy
and
you
know
just
run-
run
a
few
unit
tests,
if
you,
if
you
like
so
we've
added
that
in
and
of
course
now
what
we
can
do
is
we
can
flip
back
to
our
pull
request
and
where's.
A
My
welcome
message
here
and
we
can
see
that
the
code
is
now
ready
for
merging.
So
one
of
our
our
scans
we're
doing
a
container
scan
here
with
a
third-party
container
scanning
tool
and
core,
but
everything
else
was
passed.
So
I'm
pretty
sure
that
I'm
happy
that
the
code
scanning
is
completed.
The
build
and
publish
is
completed.
A
We're
happy
with
that.
So
I
could
now
go
and
hit
merge
on
that.
A
couple
of
things
we'll
do
before
we
hit
that
which
is
kind
of
our
our
finale.
We
can
see
these
things
are
running
right.
So
these
are
our
checks,
and
I
mentioned
that
they
are
github
actions.
Now,
if
you
have
used
github
actions,
it's
very
cool.
A
If
you
haven't
used
it,
then
you
may
already
be
using
some
form
of
ci
cd
tools,
so
you
might
be
using,
I
don't
know
jenkins
or
team
city
or
travis
or
circle
or
incredibild
or
I
don't
know,
is
your
pipelines.
There
are
a
million
of
them
out
there
and
you
know
people
are
using
anything
and
everything.
When
I
look
at
github
actions,
I
think
it's
it's
kind
of
got
two
two.
I
think
two
things
that
really
set
it
apart.
A
One
is
that
it's
not
just
about
building
and
deploying
that
code,
and
it's
really
about
automating
our
devops
process.
So
even
if
you
are
using
another
tool
to
go
and
do
builds
and
so
on,
fine,
that's
absolutely
cool.
You
can
continue
to
do
that,
but
there
will
be
scenarios
where
you
think.
Actually
I
could
automate
something
around
well,
the
pull
request
process
or
somebody
editing
the
wiki
for
this,
this
repo
or
something
happening
in
a
third-party
tool.
A
I
don't
know
somebody
approving
something
in
servicenow
and
I
want
to
kick
off
some
form
of
automation
or
workflow.
So
github
actions
is
really
really
great
for
that.
The
other
thing
that
sets
it
apart
a
little
bit
if
I
go
to
the
marketplace
here,
is
the
github
marketplace
and
we
can
look
at
actions
and
we'll
see
in
here
that
there
are
nearly
6
000
github
actions
that
I
can
use
within
my
my
workflows
and
that's
that's
fantastic.
It's
again,
there's
tons
of
things
that
I
might
want
to
do
so
almost
anything
I
can
think
of.
A
I
can
go
and
search
for
it
and
almost
certainly
somebody
has
created
this
this
component
that
I
can
use
in
my
workflow
we're
going
to
use
one
of
those
in
a
second,
but
what's
also
really
cool
about
this
is
when
we
look
at
who
is
writing
these
actions
who's.
Writing
these
components.
I
can
look
at
this
and
go
oh
wait.
A
minute.
There's
courtesy,
there's
atlassian
fortify
aws,
we'll
see
all
the
azure
microsoft
actions
sonar
source.
A
You
know
jfrog
for
all
my
atlassian
work
encore
for
the
container
scanning
we
mentioned
before
so
the
devops
vendors
devops
tool
inventors
are
building
these
actions
and
making
it
really
super
easy
for
me
to
interact
with
their
with
their
tools.
Now
we
want
to
use
a
little
scenario
here,
let's
say
again
we're
building
code
with
something
else,
and
that's
that's
absolutely
fine,
but
we
are
using.
We
are
using
github
issues
and
what
we
want
to
do
is
add
a
little
little
tweak
to
this.
A
So
what
I'm
going
to
do
is,
if
I
flip
to
my
issues
you
can
see
here
we
have
a
number
of
issues
and
I
want
to
go
and
add
a
label
to
that
issue
and
when
that
label
happens,
I
want
to
notify
my
team
now
again.
The
scenario
is
we
have
this.
I
don't
know
bug
report
come
in
and
I
want
to
say
well,
I've
reviewed
it.
We've
triaged
it.
Oh,
my
goodness.
This
is
really
serious.
We
need
to
get
the
on-call
developer
to
get
out
of
bed
and
come
in
and
fix
it.
A
Something
like
that.
So
we
want
to
send
a
push
notification
to
their
mobile,
which
hopefully
is
going
to
wake
them
up
and
they
can
go
and
do
that.
So
if
we
look
to
our
actions,
then
what
we'll
do
is
we've
got.
Let's
see,
alert
team
on
specific
label
looks
kind
of
useful.
Now
this
is
really
simply
set
up.
If
I
go
and
look
at
my
workflow
file
here
so
again,
this
is
just
a
yaml
file.
A
It's
sitting
in
my
my
repository
in
this
kind
of
hidden,
folder,
dot,
github,
slash
workflows
and
it's
called
labelalert.yaml
and
again
what
this
is
saying
is
okay.
This
is
again
the
slight
difference
when
we
think
about
github
actions,
it's
got
to
trigger
now
it
could
be
on
on
pull
request.
It
could
be
on
you
know
again.
I
mentioned
somebody
pushing
some
code.
It
could
be
somebody
editing
the
wiki
file.
It
could
be.
I
don't
know
somebody
creating
a
deployment
or
whatever
you
can
almost
anything
that
happens
in
github.
A
A
It
would
go
off
and
run
this
this
workflow,
but
in
this
scenario
we're
saying,
okay.
Well,
let's
restrict
it
a
little
bit
further.
We
we
can
now
we
can
change
it
to
be
maybe
a
pull
request
to
a
specific
branch,
so
maybe
the
the
main
branch
in
this
case,
or
in
this
scenario
we're
saying
if
it's
a
pull
request
it's
created
and
it's
labeled
or
it's
an
issue-
that's
created
and
it's
labeled
then
run
this
workflow.
Let's
go
and
create
this
thing.
A
A
Then
I
want
you
to
go
and
run
the
workflow
and
we've
got
one
step
in
here.
It's
really
simple
and
we're
using
an
action
from
the
marketplace.
It's
a
federal
free
action
which
allows
us
to
send
a
push
notification
to
our
mobile.
A
Then
we
need
to
give
an
api
key,
which
tells
it
where
to
send
that
that
notification
and
we've
got
a
message
in
here
to
say:
hey,
go
and
check
out
the
latest
issue
in
our
our
octo
twitch
repository.
They
need
your
attention,
but,
of
course
we
can
add
more
additional
information,
give
them
links
whatever
we
need
to
do
so
we
really
simple
way
here.
So
let
me
flip
back
to
my
issue,
which
one
will
be
on.
A
We
want
number
two
we'll
go
and
we'll
add
ourselves
a
label,
so
we'll
just
do
that
so
alert
the
team.
Now
what
should
be
happening
is
we
should
be
able
to
click
into
our
actions
and
see
that
yep.
Something
is
running,
so
I'm
just
going
to
fire
up
my
my
phone
and
I'm
going
to
remove
anything
that
might
be
incriminating,
so
we'll
get
rid
of
all
those
whatsapp
messages
that
are
showing
up
on
my
on
phone
and
with
a
bit
of
luck.
A
In
oh,
it
was
just
a
beep.
Let's
make
sure
that
that's
what
I
think
it
is
yes,
it
is,
and
so
let
me
see
if
I
can
get
that
up
to
my
camera.
You
can
see
it.
So
we've
got
a
little
github
notification
back
on
the
black
there.
We
let's
try
one
more
time
there
we
go.
A
I
think
that
I
probably
yeah
yeah.
Hopefully
you
can
see
here
but
afraid
to
be.
I've
got
a
push
notification,
that's
saying
hey!
You
need
to
go
and
check
this
thing
out
and
of
course,
I
can
now
go
and
use
the
the
github
mobile
app
to
effectively
go
and
check
that
out
check
out
the
issue
or
or
whatever
we
need
cool.
So,
let's,
let's
finish
this
up
then
so
we've
got
our
automation
in
there.
A
Let's
do
one
last
thing
we'll
do
our
pull
request
and
then
what
we're
going
to
do
is
wrong
bit.
Let's
call
my
pull
request.
Let's
go
to
update,
welcome
message:
let's
go
back
in
here.
Everything
is
completed.
We've
had
our
alerts,
we're
going
to
merge
that
pull
request.
Yep
we're
happy
with
that,
and
now
we
can
close
that
pull
request
as
well.
Everything
is
successfully
merged
and
closed
again.
A
I
can
delete
that
branch.
If
I
want
now
two
things
to
look
at
because
we've
merged
that
change
to
our
main
branch,
it
should
be
going
off
and
going
okay.
Now
I'm
going
to
update
my
my
github
pages
view.
We
can
also
go
back
to
our
project
and
we
can
dive
into
that
and
hopefully
make
sure
it's
in
the
right
spot.
Where
are
we
there?
We
go
add
custom,
welcome,
sign,
there's
my
tags,
alert,
team
and
enhancement.
A
I've
got
my
link
pull
request
because
I
added
that
little
number
into
the
pull
request
body
and
it's
moved
it
to
the
done
column.
So
again,
it's
just
about
making
this
super
easy.
We've
we've
reviewed
the
code,
we've
we've
merged
it.
That
piece
of
work
is
now
done.
Let's
go
back
to
the
to-do
column
and
figure
out
what
else
we
need
to
do.
I
think
I'll
leave
the
error
stack
traces,
sometimes
in
to
sebas,
so
really
simple.
To
do
that
now,
again,
the
literally
the
money
shot
here.
A
Is
we
just
popped
to
our
where's,
my
build
my
cat,
so
that
is
okay.
A
With
luck,
damn
the
movie
hasn't
completed
yet
we
haven't
got
in
there.
I
was
hoping
for
the
the
the
big
the
big
reveal,
but
obviously
hasn't
finished,
building
and
publishing
that
that
new
version
yet
gonna
get
it
yeah.
Not
quite
oh,
damn,
anyway,
what
a
disappointment
for
me,
but
it
absolutely
will
work.
A
A
Hopefully
maybe
it's
still
doing
its
thing,
but
I'm
trying
one
more
time.
A
Damn
it
didn't
get
it
oh
wait!
We're
not
gonna
worry
too
much
about
it.
So
we
can
see
that
that
has
that's
completed
so
again.
The
reveal
is
not
part
of
the
demo
cool.
Okay,
that's
all
I
had
to
show
you
guys
today.
What
we
can
do
is
is
absolutely
happy
to
hang
around
answer
questions
on
the
chat.
If
there's
anything
you
want
to
discuss,
hopefully,
sebas
has
been
hitting
you
up
with
some
nice
links
and
answering
any
of
your
questions
as
I've
been
going
through.
A
Oh
yeah,
so
just
one
of
the
questions
there,
obviously
around
using
github
action
flows
for
other
purposes
within
the
source
code,
create
flows
to
businesses,
processes
absolutely
so
effectively.
A
You
have
a
trigger
and
that
trigger
could
be
almost
anything
on
that
github
repository
and
when
that
that
trigger
is
well
triggered,
then
that
workflow
will
go
off
and
run
and
again
the
the
workflow
that's
running
doesn't
have
to
be
anything
to
do
with
the
code.
It
doesn't
have
to
be
hey,
I'm
building
something
or
I'm
running
static
code,
analysis
or
whatever
it
can
literally
go
and
do
anything.
A
So
one
of
the
things
that
we
we
use
internally
quite
a
bit
is
one
of
our
very
very
smart
colleagues
has
created
a
workflow
where
effectively
you
will
go
into
a
github
repository,
create
an
issue,
and
when
that
issue
is
created
with
certain
information
in
it,
it
will
suck
the
information
out
and
go
off
and
provision
effectively
a
whole
demo
environment
using
the
terraform
provider
for
github.
It
uses,
I
think,
there's
some
ansible
in
there.
It
will
go
off
and
create
deployment
environments,
and
it's
all
built
off.
A
You
create
that
issue
and
then
all
these
wonderful
workflows
go
off
and
run
so
it's
very,
very
cool
the
approval
process
for
for
deployments
and
running
workflows.
Absolutely
you
can
do
it
it's
a
little
bit.
It's
a
little
bit
more
effort
involved
right
now,
so
you
could
say
hey
if
let's
say
I
requested
this
this
this
workflow
to
run
or
this
workflow
executing,
then
you
could
go
and
check
for
certain
things.
A
You
could
check
for
well,
one
of
the
repo
owners
or
repo
administrators
has,
I
don't
know,
labelled
labeled
the
the
pull
request
or
something
like
that.
So
you
think
we're
building
in
an
approval
process
into
something
else.
So
an
issue
has
been
created
or
it
was
a
certain
person
that
requested
this
or
a
certain
label
who's
been
at
it.
So
you
can
absolutely
do
that,
but
the
one
of
the
things
to
check
out.
So
if
I
was
to
do
guitar.
A
So
this
is
a
public
roadmap
and
if
you
were
to
go
and
check
this
out
so
just
github.com
github
slash
roadmap,
go
and
check
out
the
project
board
and
one
of
the
things
you
can
you
can
have
a
look
at
is.
If
I
let
me
go
here,
we
get
what
I
want.
A
I
was
looking
for
fine,
let's
do
this.
Let's
see
in
here.
Oh
look
at
that.
So
again,
downloading
the
project
board,
demoing
the
filter
and
again,
if
you
were
to
perhaps
look
at
any
big
conferences
coming
up
in
that
time
frame,
then
well
keep
an
eye
on
that
stuff.
So
yeah,
absolutely
it's
it's
it's
imminent,
but
it's
certainly
possible
right
now,
cool!
So
that's
all
I've
got
to
show
for
you.
So
I
think
we'll
do
we'll
stop
the
live
stream.
A
There
sebas
and
I
will
hang
around
for
kind
of
as
long
as
you
guys
need
we'll
answer.
Some
questions.
Do
it
in
the
chat
and
then
yeah,
hopefully,
you'll
find
that
useful
and
yeah.
Hopefully
you
can
get
stuck
into
some
of
that
fun
stuff
with
collaborative
coding.