►
Description
Recording of the Open Source Friday stream with Bdougie and MishManners.
Stream occurred on 26-02-2021, 1pm AEDT.
Thanks everyone for joining the stream. We hope you enjoyed it.
Here’s some of the links we mentioned:
Git Twitch repo: https://github.com/bdougie/git-twitch
Bey bot repo: https://github.com/open-sauced/beybot 💅🏾
Smee: https://smee.io/N6AHydhyYp4ee7
GitHub Meetup group: https://www.meetup.com/en-AU/pro/github-virtual-meetup#events
Octokit webhooks: https://www.npmjs.com/package/@octokit/webhooks
Working with JSON files: https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Objects/JSON
JSON stringify: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify
Nodemon: https://www.npmjs.com/package/nodemon
Flexbox CSS: https://css-tricks.com/snippets/css/a-guide-to-flexbox/
0:00 - Start
3:09 - What are they working on?
42:42 - Project setup
1:12:19 - Working with GitHub webhooks
1:53:00 - Managing webhooks
2:40:18 - Styling the alerts
Hope to see you at the next Open Source Friday stream.
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
A
Good
old
obs
doesn't
want
to
record
today
that's
okay,
the
good
thing
about
obs
and
twitch,
as
we
can
get
the
download
afterwards.
How
good
is
that,
good
morning,
everyone
windows
noises.
I
know
that
windows
noise
was
telling
me
that
no
recording
for
you
today
I
was
like
what
minor
recording
for
me.
Whatever's
we've
got
bjergy
here,
we've
got
maple
leaf
here,
we've
got
quintastic
here,
we've
got
slow
here.
A
A
A
It's
actually
kind
of
cold,
which
is
why
I
got
a
hoodie
on
yeah,
it's
supposed
to
be
summer
like,
but
you
know
I'm
in
melbourne,
I'm
in
australia,
like
people
just
think
australia
is
just
warm
hot
dry
place
all
the
time
and
it's
like
no,
no,
no!
No!
No!
No!
It's
like
I'm
in
melbourne,
which
means
four
seasons
in
one
day
like
it'll,
be
41
degrees,
which
is
the
equivalent
of
your
106.
A
So
for
those
of
you
who
missed
the
last
amazing
session
with
me
and
b
doggy,
you
can
have
a
look
at
it
there
in
the
chat.
So
we
on
the
last
session,
which
was
nearly
three
weeks
ago
now,
which
is
probably
more
than
three
weeks
ago
about
a
month
ago,
we
started
creating
a
github
chatbot
for
the
twitch
channel.
So
today
we
are
going
to
continue
that
clean
it
up
tidy.
It
up,
show
you
some
more
fun
things
on
the
way,
but
there
is
the
last
stream
for
reference.
B
A
A
A
Oh
look.
This
looks
like
inception,
so
that's
the
last
one,
that's
the
last
one.
You
can
see
I'm
wearing
something
different,
so
that
was
the
last
stream
and
now
we're
back
to
here.
So
brian,
would
you
like
to
talk
us
through
a
little
bit,
just
those
who
weren't
here?
Would
you
like
to
do
a
quick
recap
of
our
chat
thought
that
we
did
from
last
time.
B
Yeah
yeah
folks
we
and
we
have
a
chat
integration
called
get
twitch
and
it's
aptly
named
it's
a
integration
to
connect
github
the
api
into
twitch
interactions
on
twitch.
So
last
week
we,
if
you,
if
you
want
to
get
the
tl
dr
the
cliff
notes
of
the
video
we
got
to
the
point
where
we
integrated
this
into
or
the
stream
that
we're
on
right
now
and
every
time
you
start
this
repo
that
you're
looking
at
it
will
actually
do
a
couple
things.
B
A
B
A
All
righty,
well,
I
think
the
first
thing
we
need
to
do
so
b.
Doug,
you've
done
a
lot
of
work
on
git
twitch
since
the
last
time
we
had
a
session
like
this,
and
so
I
was
like
well,
I
obviously
coined
the
repo
last
time
or
I
fought
the
repo.
So
if
I
go
to
mine,
I
reckon
mine
is
going
to
be
quite
a
lot
of
commits
behind
yours.
So
that's
probably
the
first
thing
we
need
to
do
is
get
yours
here
we
go
so
here's
my
fork.
A
B
Yeah
yeah,
I
think
so
this
is
actually.
I
was
in
a
twitter
conversation
with
someone
on
twitter
about
the
this
practice
of
updating
your
forks
and
keeping
them
up
to
date.
So
there's
some
things
that
I
honestly,
I
don't
know
if
we
are
going
to
come
into
some
problems
because
I
think
were
you
working
on
the
main
branch,
or
did
you
create
a
new
branch
for
her.
B
B
B
B
A
B
Yeah,
we're
gonna
need
a
terminal,
I
think
the
cleanest
way.
Now
you
might,
you
might
have
a
better
way
through
desktop.
I
know
I
talk
about
this
all
the
time
I
don't
use
github
desktop,
so
I
don't
have
the
the
intuitiveness
to
be
able
to
do
this
locally
in
desktop,
but
for
it
looks
like
someone's
saying
that
my
mic
could
be
turned
up.
A
B
B
We've
got
two
different
versions:
we've
got
the
upstream,
which
is
mine,
so
that's
the
buggy
slice
get
twitch
and
then
we've
got
the
fork
which
is
mish
manor,
slash
get
twitch,
so
we
we
need
to
actually
make
sure
we're
pulling
from
the
upstream
onto
the
main
branch
and
that's
something
that
I
don't
unders.
I
don't
quite
have
in
my
github
desktop
knowledge,
but
I
could
do
this
like
a
wizard
on
the
terminal.
A
No
so
we're
looking
at
desktop
at
the
moment.
We
can
see
all
the
things
that
have
hap
changes,
so
the
greens
obviously
additions
and
the
writer's
deletions.
So
now
we
can
see
like
these
ones
are
mine.
It's
a
little
image
here
of
me,
so
they're
my
additions
and
deletions,
and
then
we've
got
brian's
here
as
well
b
doggies.
So
that
looks
like
he
fixed
up
a
few
typos
and
a
few
things.
So
if
we
have
a
look
at
the
actual
changes,
it
says
no
local
changes.
B
B
B
B
B
A
B
A
B
A
B
And
that's
fair
to
to
also
mention
too,
like
we.
We
did
a
lot
of
readme
updates
because
of
my
unfortunate
not
having
good
standards
and
practices
for
teaching
you
how
to
do
this
during
the
readme.
So
there's
some
clear,
clearly
missing
components
and,
as
we
were
discovering
this,
so
luckily
everybody
who
missed
last
week
now
gets
a
nice
clean
step.
Five
step
process
to
you
set
up
their
own
git
twitch.
A
B
A
B
Yeah,
so
with
that,
we
should
be
able
to
back
out
of
this
and
resolve
those
conflicts
similar
to
the
way
we
do
it.
It's
in
the
desktop
ui
or
sorry
the
github.com
ui
resolve
using
theirs,
which
is,
is
that
what
that
said?
It
was
actually
kind
of
small
for
me.
So
I
don't
know.
If
that's
what
it
said
on
the
screen,
I
didn't
write
it
all
right.
You.
B
A
B
A
B
B
Yeah,
so
that's
going
to
be
the
start
of
some
changes
and
then,
if
you
scroll
down
to
the
the
next
set
of
arrows,
this
is
going
to
be
a
block
of
changes
that
I
have
okay
and
then
the
next
section
of
the
arrows
pointing
the
other
direction.
These
are
gonna,
be
the
changes
that
you
have
okay,
so
the
easiest
thing
to
do
is
probably
just
go
ahead
and
obliterate
yours,
so
everything
from
yeah,
because
I
mean
can
I
just.
A
A
A
A
Don't
know
I
thought
so,
for
everyone
who
doesn't
know
like
obviously
create
space
is
a
new
thing
too,
and
our
boss,
martin's,
always
like
you,
kids
these
days,
you
have
no
idea
how
easy
you've
got
it
back.
In
my
day,
we
had
to
like
wait
like
500
years
to
get
a
dev
machine
that
works
and
now
you're
opening
up
for
code
space,
and
it
takes
10
seconds.
I'm
like.
B
It
is
remarkable
how
advanced
the
developer
tool
space
has
been
and
like
even
in
the
last
five
years.
I
think
like
vs
code
is
really
well
not
like
there's
jet
brains,
there's
vs
code
atom
is
what
we
just
saw
sublime.
I
was
actually
originally
a
sublime
user,
so
that's
where
I
got
I
sort
of
cut
my
teeth
on
developer
tools,
but
or
ids
rather,
but
I'm
actually
a
vim
user.
A
A
B
B
B
A
B
B
A
A
Yeah
easy
and
eager
yes,
but
I
mean
like
it's
showing
you
a
lot
of
like,
I
think
most
of
the
ways
I've
found
how
to
do
stuff
is
like
like
right
now,
it's
like
good
there's,
a
blue
button.
That
says,
would
you
like
to
push
to
origin?
It's
like
cool,
like
it's,
it's
kind
of
guiding
you
in
the
ways
that
you
kind
of
need
to
go.
The
other
thing,
that's
what
I
like
about
this
stuff
is
like.
Oh
look.
It's
now
done
now,
there's
no
other
big
blue
button.
So
it's
like
oh
cool.
B
A
B
A
B
A
B
B
And
there's
going
to
be
some
changes
because
you
have
hard-coded
some
of
the
code
from
like
mitch
manners.
I
probably
don't
want
everybody
to
clone
this
and
get
miss
maynard
so
for
the
state
in
case
people
do
want
to
fork
this
and
they're
confused
on
who
miss
manners.
Is
I'm
switching
that
back
to
b-duggy
nice,
but
but
everything
else
I
think,
will
keep,
as
is
because
I
think
those
are
all
great
changes
that
we
actually
got
during
the
stream
last
time.
So
I.
B
Actually,
if
you
go
to
because
I
did
suggested
changes,
I
suggested
directly
the
pr
that
you
could
actually
change
this
from
mitch
manners
to
b
dougie.
You
can
go
to
that
drop
down
where
it
says,
commit
yeah,
and
then
that's
actually
going
to
create
a
commit
directly
on
the
repo
or
sorry
on
the
your
branch.
A
B
B
Wanted
to
save
it,
save
it
for
the
all
the
content
on
stream,
so
I'm
gonna
merge
this
into
now.
The
one
thing
I'm
gonna
do
is
I'm
gonna
squash
and
merge,
because
you've
got
a
lot
of
commits
that
that
are
quite
different,
but
I'm
gonna
call
these
michelle
streaming
updates,
and
this
is
something
that
not
a
lot
of
people
have
a
lot
of
strong
opinions
about.
I'm
just
kidding,
developers
have
opinions,
the
difference
between
squashing
emerge
and
merge,
commits
and
rebasin
merging.
B
A
B
B
That's
going
to
have
say
basically
michelle
streaming
update,
readme.md,
because
I
just
renamed
it
just
now
that
is
going
to
add
a
commit,
and
then
it's
going
to
take
your
eight
commits.
Actually,
at
this
point,
it's
11
commits
and
it's
going
to
shove,
those
into
the
main.
So
I'm
going
to
have
now
nine
commits,
and
then
this
merge
commit
that
I
can't
do
anything
with.
I
personally
don't
like
that.
B
I'm
sorry,
I'm
gonna
tell
you
my
opinions,
because
I'm
talking,
no,
I'm
just
kidding
no,
but
I
I
don't
like
the
merchant
commits,
because
they're
very
challenging
to
work
with.
If
you
have
to
revert
history,
so
I
always
avoid
those.
The
other
two
options
is
rebase,
which
rebase
will
take
those
11
commits
and
and
incept
them
directly
into
the
history
the
way
and
makes
it
fit
perfect
perfectly.
B
That's
also
challenging
and
something
that
has
a
caveat
with,
because
if
you
want
to
revert
back
to
like
the
last
three
commits
the
last
two
commits
can
be
two
of
mine
and
one
of
yours
or
five
of
yours
and
one
of
mine.
It
won't
be
as
clean
and
then
so
what
I
would
normally
do
for
prs,
because
I
force
everybody
to
do
prs
for
all
my
projects,
even
open
source
ones-
and
I
do
this
myself-
is
I
squash
and
merge?
B
So
not
only
do
I
get
one
merge
commit,
I
get
only
one
commit
from
michelle's
changes,
so
I'm
gonna
do
that
and
that's
my
preference.
I
am
not
right
by
all
means
like
this
is
not
the
best
way
to
do
everything,
but
after
the
years
of
programming
that
I've
done,
I've
just
discovered
that
this
is
the
the
easiest
way
for
me
to
sort
of
manage
projects
in
the
open
in
open
source.
B
B
B
B
B
Sorry,
I'm
just
figuring
a
name
on
the
fly.
Rebasing
does
make
the
history
really
clean
and
clear,
and
there
are
certain
projects
that
I've
talked
to
as
a
github
open
source
projects
that
love
the
rebase,
because
you
do
have
a
consistent
history
and
as
long
as
the
whole
team
and
contributors
are
very
clear
about
how
they
they
write.
Their
commits
in
the
history
so
like,
even
like
your
commits,
like
fix
encryption,
remove
flex,
remove
flex
fix
css
like
there's
a
couple
of
fixed
css.
B
Those
could
be
confusing
to
manage
if
you
have
wildly
different
names.
So
what
the
best
thing
to
do
is
probably
have
a
contributing,
md
and
have
context
there
of
how
you
expect
your
contributors
and
your
team
members
to
write
their
commit
messages
and
whether
you
prefer
rebasing
or
squashing,
because
if
you
do
want
to,
if
you
do
one
of
each,
it's
just
going
to
be
wildly
hard
to
manage.
So.
B
Yeah,
so
I've
been
on
teams
that
have
done
all
all
of
the
above
and
for
all
different
types
of
reasons,
and
usually
it
you
just
do
the
thing
that
the
the
person
has
been
there.
The
longest
has
decided
or
has
still
around,
to
convince
the
rest
of
the
team.
To
do
I
like
that,
but
to
be
quite
honest,
there
are
so
many
github
integrations
like
github
apps,
as
well
as
actions
that
can
enforce
and
lynch
your
commits
as
well.
B
So
at
the
end
of
the
day
like
having
this
conversation,
is
probably
should
be
a
done
conversation.
You
should
just
install
a
github
repo
integration
and
then
you're
you're
convinced
that
this
is
now
the
way
to
go
moving
forward,
and
some
of
the
popular
ones
are
like
semantic
release
is
one
of
them.
It's
a
github
project
that
enforces
the
the
pr
structure.
So
that
way,
the
commits
show
up
really
nice
in
your
sort
of
release,
documentation.
B
Yeah
yeah,
so
the
the
hope
is
that
you
can
re.
You
can
revert
an
entire
pr
merge.
So
if
you
cut
a
release,
the
hope
is
that
you
can
actually
revert
back
and
make
that
not
as
a
pain,
because
you
only
have
to
revert
one
commit
if
you
want
to
revert
one
commit
that
was
squashed,
a
bunch
of
like
ten
different
commits,
I
would
say,
there's
like
no
judgment
here
but
like
I
think
there
might
be
a
code
smell
of,
like
maybe
the
best
practices
that
you're
using
for
your
team.
B
Perhaps
there's
like
some
sort
of
linting
or
integration
or
qa
testing
that
can
prevent
that
in
the
future
because,
like
if
you're,
if
you're
fixing
things
in
production
all
the
time,
it's
probably
not
going
to
be
a
nice
ergonomic
coding
experience
moving
forward.
So
I
would,
I
would
recommend
figure
how
to
make
that
more
ergonomic
and
easier
to
work
with.
So
that
way
you
don't
have
to
do
that
ever.
B
Why
you,
sometimes
you
just
have
to
defer
the
people
who've
been
on
the
team
the
longest,
because
they've
seen
like
I've
been
in
the
in
the
room
where,
like
someone
mentioned
bisecting
where
someone
deleted,
like
a
wall
of
code
like
that,
was
actually
legitimate
needed
to
be
in
in
the
the
project
and
like
everybody,
moves
like
back
in
the
day
when
we're
all
in
the
office,
everybody
goes
to
the
one
person's
desk.
They
pull
out
the
get
bisect.
They
start
writing
down
on
the
whiteboard
like
here's,
the
commit
of
this
happening.
B
Here's
a
commitment
to
that
happening
like
and
you
get
like
the
it's
like
that,
one
meme
of
charlie
day
from
always
sunny
in
philadelphia
where
he
has
like
the
red
strings
between
the
pictures
and
like
it's
just
him
like
okay.
This
is
what
happened
like
the
the
the
crazed
dev
just
trying
to
figure
out.
You
know:
okay,
it
was
this
commit.
If
we
go
down
to
this
commit
we
can
squash
here
and
yeah.
So
we
don't
want
to
get
to
that
situation.
B
I
think
what
you
probably
want
to
do
is
probably
start
again
with
a
full,
a
fresh
pool
because
we're
probably
getting
some
like
really
weird
get
history
issues,
because
the
fix
you
fix
was
a
fix
that
was
already
on
main
that's
now
in
maine.
We
can
also
do
some
other
like
force
pulling
where
it
actually
rewrites
your
history.
For
you,
oh
you
know
what
actually
what's
better?
B
C
B
A
B
A
A
B
A
B
B
A
A
B
B
And
now
you
should
be
able
to
get
check
out
maine,
and
what
fetch
upstream
does.
Is
this
actually
fetches
all
the
the
content
but
stores
it
in
memory?
And
what
is
this?
You
have
a
remote
tracking
origin
if
you'd
like
to
always
have
so.
This
is
basically,
if
you'd
like
to
make
origin
your
default.
Okay,.
A
A
B
B
A
B
Yeah,
I
think
I
think
we'll
be
best
to
we
could
probably
so
we
won't
lose
any
context
if
we-
and
this
is
what
I've
always
tried
to
avoid.
This
is
actually
deleting
the
fork,
because
all
the
history
and
your
your
thoughts
and
process
are
still
there
and
the
fork,
but
I'm
not
quite
understanding
why
the
the
the
branch
itself
is
not
not
liking.
What
we're
doing?
B
B
A
A
B
B
B
This
is
like
this
is
not
really
the
best
practice.
This
is
something
I
was
having
a
conversation
with
on
twitter
that
to
keep
your
fork
up
to
date,
you
can
get
in
some
pretty
hairy.
Messes
like
we
just
gotten
to
and
like
deleting
the
fork,
should
not
be
the
solution,
but
it's
the
solution,
most
people
use.
B
A
A
B
A
B
B
Yeah
and
I
think
what
the
the
value
here
to
kind
of
learn
from
too
as
well,
is
like
as
a
contributor
to
an
open
source
project.
You
never
want
to
use
the
default
branch,
even
though
it's
the
easiest
thing
to
do,
if
you
ever
want
to,
if
you
ever
ever,
want
to
contribute
again,
you're
always
going
to
be
in
a
really
weird
spot
that
we
got
into
so
in
the
future.
B
We're
always
creating
a
new
branch
and
my
best
practice,
and
what
I
recommend
most
of
my
projects
is
create
a
branch
describing
the
change
you
want
to
make.
So
today
we
could
actually
create
a
new
branch
from
the
a
new
fork
and
call
it
updated
style,
and
then,
at
that
point
we
can
update
the
style
and
focus
on
that
and
then
once
we've
completed,
that
we'll
do
a
pr
and
then
we
can
move
on
to
the
next
feature.
A
B
Excellent
and
then
we
have
some
setup
that
we
need
to
do
too
as
well.
So
I
don't
know
if
you
still
have
a
smee
site
up
and
running
you
probably
have
you
should
have
a
the
thing.
Is
we
had
to
click?
We
had
to
delete
the
branch.
Sorry,
the
fork
itself,
so
you
probably
have
to
create
a
new
smee
client,
which
is
probably
good
updates,
are
sorry
good
context
for
folks
who
weren't
here
last
time.
B
Yep
yeah
and
while
you're
doing
that,
all
this
exploit
for
folks,
you
just
showed
we're
actually
building
a
github
integration
into
twitch,
the
twitch
stream
that
we
have
going
right
now.
So
michelle
is
actually
creating
a
sme
that
I
o
link.
Smee
is
an
internal
tool
that
github
employees
built
it's
basically
a
web
hook,
receiver
or
aggregator.
B
So
that's
what
that
is,
and
it's
probably
why
you
haven't
heard
of
it,
because
it's
a
tool
that
we
use
internally,
that's
open
sourced,
yeah,
there's
there's!
I
was
surprised
on
how
many
open
source
projects
github
has
that
most
people
have
probably
never
heard
of,
and
I
think
that's
just
kind
of
how
open
source
works.
Even
github
has
projects.
A
A
B
Yeah,
you
can
add
a
web
hood
secret
and
then
go
ahead
and
create
that
and
then
the
one
thing
else
that
you
want
to
keep
in
mind.
Is
you
want
to
track
stars
not
all
pushes
by
default
when
you
create
a
web
hook
on
github
repos,
it
tracks
all
push
pushes
to
the
or
commits
to
the
project
and
for
the
sake
of
not
having
such
a
noisy
bot,
we're
just
gonna
track
stars.
A
A
B
A
B
A
B
This
repo
stars,
that's
only
going
to
update
every
time
you
hit
the
api.
Github
itself
has
a
rate
limit
of
unauthenticated.
Requests
are
like
40
per
hour.
Authenticated
requests
are,
I
think,
like
a
couple
hundred
so
with
the
web
hooks
every
time,
there's
a
star
we're
going
to
be
notified
through
this
integration.
So
that's
basically
the
sort
of
yeah
you
probably
I
know
I
kept.
I
kept
the
explanation,
even
though
you
said
you
got
it,
but
in
case
other
people
were
not
informed.
I
just
kept
going
through
yeah,
okay,
so.
A
Why
you
did
that?
I
coined
the
repo.
Don't
forget:
repo
clone
is
not
a
git
commander
to
github
command,
so
gh
repo
clone
and
then
obviously
you
don't
need
github.com,
because
you're
already
on
github
and
then
just
the
path
of
the
repo
you
want
to
clone
and
then
that
clones
it
into
whatever
this
directory
you've
put
in
here.
A
B
Accidentally-
and
I
I
realized
for
the
sake
of
daryl,
who
asked
a
question
earlier-
how
we
got
so
messed
up,
the
cli
actually
does
the
upstream
for
us
which
in
history,
when
you
do
the
git
clone
from
github,
you
don't
get
the
upstream
setup.
So
you
would
have
to
manually
set
up
my
my
upstream,
which
is
buggy.
B
Oh
yeah,
so
basically
this
what
I
was
getting
at,
I
dropped
a
link
to
the
cli
in
the
chat,
because
the
cli
connects
the
fork
and
the
the
main
upstream.
So
my
project
and
then
michelle's
fork
of
my
project
are
now
connected
to
the
same
clone
because
of
the
github
right.
That's
not
normal.
It
just
happens
to
be
a
nice
syntactical
sugar
that
has
been
added
to
the
cli
tool.
A
B
A
A
A
B
A
A
B
A
B
And
make
sure
you
do
it
so
make
sure
you
also
rename
it
to
emv
as
the
name
of
the
file,
but
so
we
we
went
pretty
quick
because
we
did
do
this
last
week.
But
folks,
if
you're
just
joining
us,
we
do
have
a
repo
which
is
vw,
get
twitch.
This
is
our
twitch
integration
that
we're
gonna
add
in
a
moment
to
to
our
twitch.
The
actual
show
we're
on
it's
sort
of
like
learning
how
to
fly
a
plane
while
building
it
at
the
same
time.
B
We're
gonna
share
that
in
a
second.
But
the
the
trick
of
this
is
that
we're
watching
stars.
We
set
up
our
web
hooks.
We
set
up
our
smee
to
actually
receive
the
web
hooks
and
then
we're
going
to
set
up
a
local
server
on
localhost
3000,
I
think,
is
the
default
one
and
we're
going
to
add
that
to
obs
and
then
every
time
you
star
the
git
twitch
repo,
then
we're
going
to
have
some
sort
of
integration
happen
on
the
screen
or
in
our
ears.
A
B
B
A
A
Right
come
along
and
have
a
workshop
with
us
yay.
Oh
sorry
code,
you
you
got,
you
got
dolly.
Let
me
let
me
fix
that.
Unban
you
yeah,
so
smee
looks
exactly
what
you've
been
looking
for,
so
happy
yay,
so
yeah
we've
removed
urls
in
the
chat,
because
you
know
people
like
to
post
some
really
weird
urls.
So.
A
B
A
B
B
B
B
B
C
C
A
B
Is
mainly
because
the
way
we
wrote
this
code?
Oh
sorry,
the
way
we
were
so
I
ended
up.
Writing
all
this.
A
lot
of
this
code.
The
way
I'm
receiving
the
json
started
receiving
the
the
web
hook.
Event
is,
I'm
I'm
expecting
json,
but
it
was
actually
url
encoded
information
which
is
gonna.
Give
us
like
a
kind
of
like
an
html
file
that
I'm
not
gonna,
explain
that.
Well,
because
I
don't
use
that
I
use
json
in
most
of
my
projects,
so
we
just
had
to
switch
that.
B
A
B
A
A
B
B
A
B
B
A
B
B
B
B
A
B
B
B
A
B
B
A
B
A
A
A
B
Yeah
copy
the
mvnv
you'll
need
to
run
smee,
and
then
you
also
run
the
localhost,
but
the
only
difference
is,
we
won't
add
it
to
to
the
browser
source
in
obs,
so
yeah,
while
you're
doing
that.
I'm
actually
going
to
repeat
the
same
steps
just
to
confirm
that
I
can
do
the
same
thing
that
you're
doing
and
then
we'll
jump
into
the
code
space.
Once
you
get
all
that
set
up
and
then
I
can
help
jump
around
and.
A
A
B
A
A
B
A
B
A
B
A
A
A
B
Yeah
and
the
thing
about
starring
is
something
that
I,
it
was
a
conversation
that
came
up
because
I
was
looking
for.
I
was
googling
yelp
for
open
source
projects
when
I
was
streaming
actually
on
tuesday
and
stars
are
really
meant
for
saving
projects
for
later
star's,
not
really
a
metric
to
identify
the
top
projects
on
github
or
how
well
you're
doing
as
a
maintainer
stars
are
really
just
for
how
many
people
want
to
save
your
project.
B
A
B
A
B
A
B
So
and
the
beauty
of
this
is
like
you
went
to
stream
elements
or
stream
labs
and
built.
Your
own
chat
integrations
like
this
is
the
backbone
of
how
you
would
start
that
now,
because
we're
the
way
the
code
is
written,
it
just
puts
the
chat
into
the
console,
but
we
could
actually
create
some
css
and
put
it
on
screen
if
we
really
wanted
to
so.
B
A
B
A
B
Okay,
so
yeah
so
line
one
through
three.
That's
us,
including
a
couple
things.m,
is
for
a
secret
websocket
ws.
That's
the
thing
that
we've
been
handling
receiving
the
events
the
web
hooks.
Really,
the
websocket
is
actually
how
you
receive
the
web
hooks
and
then
express
is
what
actually
puts
stuff
on
the
screen.
So
that's
how
you're
seeing
the
image
it's
actually
powering
a
web
server
line.
Six
is
actually
octokit
webhooks.
It's
a
it's
a
great
tool
actually
tomorrow,
right
here
on
github
folks
are
asking.
B
If
github
has
been
streaming,
we've
been
streaming
since,
I
think
may
of
last
year
and
we've
been
doing
open
source
fridays.
We
don't
do
every
friday.
We
try
to
do
as
many
fridays
as
we
can
get
guests,
but
tomorrow,
friday
tomorrow,
as
in
the
american
time
zone
tomorrow,
we
will
have
the
creator
of
octokit
webhooks,
actually
on
stream
with
me
chatting
about
a
new
tool
he
built
so
just
want
to
give
a
shout
out
because
it
just
felt
like
it
fit
line
9
through
11.
B
B
B
B
So
that's
that's
the
answer
which
I
can.
I
can
translate
that
for
you,
but
just
real
quick.
I
wanted
to
point
out
that
it's
not
the
same
thing.
It's
a
stack
trace,
so
the
stack
trace
is
actually
pointing
us
to
file
line
numbers
of
where
the
problem
is.
So.
If
we
looked
at
that
stack,
trace,
we'd
eventually
find
out
what
line
number
is
broken
and
it
really
just
comes
down
to
the
signature.
B
B
B
B
A
B
A
B
I
used
to
do
a
lot
of
work
on
back
when
I
first
joined
github
when
I
say
work,
I
didn't
actually
contribute
a
lot
of
code
to
it,
but
I
did
create
some
videos
and
some
courses
and
stuff
like
that
for
it
and
it's
it's
kind
of
the
predecessor
to
github
actions,
github
actions
being
the
sort
of
tool
to
do
ci,
cd,
but
also
repo
automation,
probot
was
really
100.
Repo
automation,
well,
I
say
was
it
still?
A
B
B
B
B
B
A
B
Yeah,
I'm
not
sure
where
everybody's
at
with
the,
if
how
much
context
you
have,
because
I
know
people
jump
in
and
out
of
this
thing,
we
now
have
a
working
product
which
I'm
super
excited
about.
We
now
every
time
you
start
that
repo,
the
dapp
punctuation
will
come
up.
So
I
think
something
we
should
be
doing
is
one.
We
should
probably
say
who
who
is
starring
the
repo
see
if
we
can
get
that
context
on
the
screen
and
then
the
other
thing
is
probably
add
some
css
to
that
name.
B
B
Okay,
so
now
here's
going
to
be
the
fun
part
if
we
go
to,
if
we're
going,
to
need
to
read
the
payload
to
understand
what
context
we're
going
to
get
so
that
way,
we're
not
we're
not
shooting
blind
from
the
hip,
and
I
think
the
best
way
to
do
this
is
going
into
actually,
if
you
went
back
to
your
local
host,
if
you
scrolled
up
localhost
in
the
server
accepted
false,
these
error
messages.
That's
fine!
If
you
go
back
to
the
smee.
C
B
Into
put
it
onto
the
screen,
so
this
might
take
a
little
a
little
bit
of
work
and
it
might
actually,
let's
let's
take
a
step
because
we're
going
to
need
to
do
some
architecture
and
planning.
So
we
have
two
different
things:
we're
going
to
do.
We
originally
came
here
that
we're
going
to
edit
some
css,
that's
gonna,
be
something
we
could
do
or
we
can
get
names
on
the
screen.
A
B
A
B
B
Able
to
so
what
we're
doing
is
we're
getting
a
payload
directly
from
the
web
hook
event
and
then
we're
console
logging
that
directly
to
the
console
that
we're
I
mean
this
might
be
obvious,
but
I'm
not
sure
where
everybody's
coming
from,
but
everybody
loves,
js,
apparently
use
js
to
mod
css,
js
and
css
that
they
don't
they
don't
mix.
Well,
they
do
mix
well,
I'm
just
kidding,
but
we
need
to
be
able
to
get
this
payload
sender
to
our
localhost
server.
B
A
B
B
Yeah
yeah,
but
but
that's
also,
I
did
see
it,
but
it's
also
completely
different
yeah,
so
basically
daryl's
kind
of
explaining
it
like
where
right
now
we're
looking
at
the
server
context
and
that's
saying
names
in
the
client
which
is
our
html
page.
It's
saying
something
completely
different.
It
doesn't
say
anybody
who
who
started
the
repo.
B
So
what
what
we
need
to
do
is
actually
pass
in
the
data
from
who
starred
the
repo
to
the
front
end
client,
basically,
and
this
this
app
is
pretty
simplistic
we're
on
line
13,
we're
actually
grabbing
that
data.
We're
constantly
logging,
but
we're
not
actually
doing
anything
on
line
21
to
do
the.
What
am
I
trying
to
say
the
wss
client.
B
It
so
let
me
see
we're
going
to
the
app
express
sorry:
it's
been
a
while,
since
I
actually
wrote
this
code
october
15
2020
was
the
last
time
I,
which
I
just
looked
at
the
last,
commit
history,
so
I
think
we're
we're
passing
it
to
the
client,
but
we're
not
actually
passing
it
to
okay.
The
client
itself
on
line
13
is
actually
what
our
server
is
yeah,
but
we
need
to
get
it.
B
A
A
C
B
A
B
Yeah,
sorry,
I'm
I'm
watching
daryl
and
planner
go
back
back
and
forth
on
this.
So
I
think
the
the
the
best
course
of
action
is
actually
just
trying
to
get
the
that
data
into
our
express
server.
So
what
I'm
gonna
actually
look
up?
Could
you
just
google
we're
going
to
we're
going
to
do
some?
Google
food,
real,
quick?
Let's.
C
B
A
B
B
A
B
B
Yeah
so
the
web,
the
ym41
initialized
the
web
server
to
be
used
by
the
web
sockets.
I
wonder
if
we
could
actually
pass
in
some
arguments
to
line
42.,
and
this
is
me
basically
shooting
from
the
hip,
so
on
line
42
after
the
word,
the
number
3000
there's,
those
parentheses
yeah.
This
is
a
place
we
could
actually
put
in
some
arguments.
Can
you
just
put
the
word
x
there,
or
is
this
the
letter
x
and
then
in
the
console.log
to
the
right?
B
B
A
A
B
Well,
we
didn't
define
x,
but
sometimes
in
javascript,
we'll
pass
in
extra
arguments
like
error
messages
directly
in
there.
So
I
was
just
shooting
from
the
hip
to
be
able
to
see
if
there
was
an
object
being
returned
that
we
weren't
looking
at
the
other
thing
that
we
could
look
up
is
that
up
on
top
there's
octokid's
web
hook?
So
that's
what
the
web
hook
is
providing
to
us.
B
B
C
A
B
A
B
B
Okay,
this
is
this
is
where
we
can
do
our
magic
okay.
So
this
is
it
yes,
so
daryl
everybody
we're
we're.
Finally,
to
the
point
we
are
so
we
need
to
be
able
to
find
we
have
e,
and
then
we
have
e
data.
I
wonder
what
would
happen
if
we,
instead
of
if
we
comment
out
line
20
and
instead
just
do
console.log
e
okay.
B
A
B
So
yeah,
so
I
think
what
we
need
to
do
is
this
yep.
Actually,
there
we
go
see
where
planet
says
unstarted
starred.
Actually,
sorry,
we
didn't
actually
comment
out
their
comments.
Everything
you
made
is
any
data
yeah
correct,
so
we
just
need
to
make
this
less
noisy.
So
we
can
do
some
work
with
that.
So.
A
B
A
B
Okay,
that
I
think
that
might
be
a
better
idea,
so
let's
go
back
to
the
so.
Basically,
I'm
just
gonna
explain
real
quick
so
that
way
for
my
debugging
purposes
and
everybody
else
who's
watching
and
for
you,
we
can
just
connect
with
the
dots,
okay
and
the
index.
In
this
page,
we
ended
up
discovering
that
the
websocket
receiver
is
here.
We
are
actually
so.
When
do
I
start
yeah,
we
gotta
send
him
our
resume.
Sorry,
are
you
gonna?
Send
your
resume
over
darryl
duck?
B
We,
the
web
hook
receiver
happens
between
what
line
14,
that's
where
it
gets
started.
We're
opening
the
socket
between
the
back-end
server
to
our
front-end
client
and
the
front-end
client
is
where
we're
sitting
right
now
and
then
on
the
messages
that
we're
receiving
from
the
web
sockets
so
not
to
be
confused
of
chat
messages.
These
are
messages
from
the
server
to.
B
B
Yeah,
it's
and
you
can
actually
see
if
you
go
back
there
online.
If
you
look
to
the
right
of
this,
like
the
top
part,
is
what
we
want
all
the
stuff
on
the
right
is
gift.
Is
the
gift.js
messages
so
to
make
this
easier
for
us
to
to
debug?
We
should
probably
just
comment
the
comfy.js
chat
on
line
57,
so
that
when
we
stop
getting
the
chat
messages
from
twitch
and
we
can
just
get
chat
messages
for.
B
B
A
B
What
daryl
was
saying
is
that
in
our
data,
instead
of
sending
just
a
string,
hi,
I'm
a
websocket
server
and
then
the
next
string
is
going
to
be
so-and-so,
started
event
or
or
whatever
we
should
probably
just
send
json.
So
we
could
just
pull
the
name
directly
out
of
it.
So
we
could
structure
this.
We
have
the
ability
to
structure
the
data
and
the
way
we
can
manage
it
so
go
back,
go
all
the
way
back
to
the
index.js,
which
is
going
to
be
again.
A
B
B
B
B
Yeah,
so
we're
sending
so
wait
where
I'm
actually
share
that
blame
around.
Yes,
everybody's
actually
pair
programming
with
us
right
now,
so
we
all
get
the
blame.
We'll
add
you
to
the
we're
gonna,
add
collectively
everybody
in
the
chat
to
the
commit
history.
So
that
way
we
all
get
a
notification
when
we,
when
the
boss
walks
knocks
on
our
door
and
says
hey
this
code,
you
sent,
I
I'm
the
yeah
okay
gotcha,
so
the
hello,
I'm
a
websocket
server,
that's
a
string
that
we're
sending.
B
B
B
A
B
A
B
B
Okay,
yeah
and
it's
a
way
to
pass
data
back
and
forth.
So
imagine
like
when
I,
if
I
send
you
a
text
message,
it's
gonna
send
that
data
over
to
you
and
the
way
the
phone
receives
it.
It
receives
it
in
a
certain
structure,
that's
readable
and
daryl.
I
think
I'm
pretty
sure
darrell
cause
daryl's
been
pretty
on
fire
of
giving
us
pushing
us
in
the
right
direction
was
saying
to
send
the
entire
object
as
json.
B
Instead
of
sending
a
string
because
what's
happening
is
we're
sending
like
these
high
ammo
web
socket
servers
as
a
string
and
then
we're
setting
a
string
of
like
hey
here's,
some
output
as
a
string
and
then
some
data
and
like
we,
we
don't
know
what
to
expect
on
the
receiving
end
on
the
client
and
to
be
able
to
present
that
properly
on
the
screen.
So.
B
A
B
Yeah,
so
what
we'll
probably
want
to
do
is
we
still
want
to
send
those
messages?
Hi,
I'm
a
websocket
server
yeah,
but
we
can
actually
stringify.
We
can
actually
just
make
that
json
instead,
so
everywhere
we
what
we
have
ws.send
we're
going
to
change
to
to
send
json
objects,
so
we
can
start
with
the
we
could
start
at
the
first
one,
which
is,
I
think,
it's
going
to
be.
The
message
received.
B
B
B
B
A
A
B
A
An
extension
to
open
this
url
signing
in
starting
collaboration
session
is
in
the
auto
connection.
Okay,
allow
access
is
getting
around
my
firewalls
now
invitation
links
copy
to
clipboard,
send
it
to
anyone.
You
trust
in
the
chat,
make
it
read
only
or
just
leave
it.
I
can
just
send
it
to
you.
Obviously,.
A
A
B
Yeah
and
what
I
usually
do
so
I
don't
usually
do
this
on
my
stream,
but
every
now
and
then,
if
I
get
to
a
point
when
I'm
live
coding
and
folks
are
like
giving
me
like
just
in
like
this,
I
will
definitely
go
and
whisper
folks
and
let
them
let
them
in
on
the
coding
fun.
I
also
do
this
with
design,
so
I
do
a
bit
of
figma
as
well,
and
I
let
everybody
sort
of
join
in
on
the
fun
on
figma,
because
it's
got
the
nice.
You
know
collaborative
design
elements
as
well.
B
B
A
A
B
B
A
A
B
A
B
A
So
the
that's
dev
life
learn
another
job.
I
think
that's
what
I
like.
I
like
this
bag.
You
can
like
highlight
stuff
and
do
things
it's
cool.
Thank
you,
tech,
workbench,
for
showing
us.
This
is
awesome
all
right.
Now
I
have
to
go
so.
We've
got
the
json
object
in
there
and
now
we've
we're
going
to
remove
this
string.
First
yeah
well,.
B
C
B
That
is
that
yep
and
then
before
the
colon.
You
want
to
create
a
key
and
we
can
just
type
message
message
which
I
don't
know
if
that's
going
to
break
anything
but
we're
logging,
the
the
output
to
the
console.
So,
let's
see
without
doing
so,
there's
two
ways
we
can
do
this.
We
could
do
it
this
way,
which
I
wanted
to
see.
If
this
will
work
and
if
not,
we
can
actually
stringify
it
in
the
json.
Okay.
A
B
A
B
B
A
B
B
B
A
A
B
B
A
B
B
A
A
B
B
A
B
B
So
I
received
the
message
star:
was
it
star
event
received
okay?
So
let's
do
this?
Let's
just
keep
keep
cause
we're
getting
a
string,
as
is
so
we'll
continue
to
move
along
this
path.
We
can
fix
this
in
a
second,
but
I
just
want
to
get
this.
These
words
on
the
screen,
which
I
think
all
you
need
to
do
is
on
line.
B
B
No
actually,
so
we
don't
need
to
add
it
in
because
we
already
have
four
arguments.
The
way
gif
alert
is
receiving.
It
is
receiving
it
as
an
argument
of
reuser,
okay
and
then
user,
we're
actually
seeing
it
online
40
or
74.,
so
we're
actually
already
gonna,
since
it's
already
string
we're
putting
that
string
on
next
to
the
other
string.
So
right
now,
if
we
do
go
back
to
our
local
host,
our,
I
think
we
is
this
already
embedded
into
our
browser
source.
I
can't
remember.
B
Yeah,
that's
e
data,
so
I
think
what
we'll
do
is
probably
remove
the
the
the
what
am
I
trying
to
get
at.
So
let's
go
back
to
the
back
end.
This
is
index.js
in
order
to
make
this
work
in
the
way
that
I
think
we
can
just
get
it
on
the
screen
and
then
move
on.
This
is
not
going
to
be
the
best
code,
but
it's
going
to
be
working
code.
So,
let's.
B
A
B
B
A
B
That
was
the
my
test
message.
The
generate
title
is
actually
so
when
you
do
a
chat
message,
it
generates
a
words
on
the
screen,
so
it's
a
it's
a
similar
like
a
dictionary.
It's
a
key
value
store
to
be
able
to
present
a
title
based
on
the
type
of
chat
message.
I
can
show
that
a
bit
towards
the
end,
but
for
now,
since
we
can
get
the
user
the
context
of
the
user
on
the
screen,
I
think
we
should
focus
on
that.
A
B
B
A
B
B
A
A
B
B
B
B
B
A
B
B
A
B
B
B
A
B
B
A
A
B
B
A
B
A
B
A
B
In
the
future,
like,
I
would
not
put
like
right
now:
we're
hard-coding,
even
in
the
gift.js
we're
hard-coding,
b,
dougie
and
github,
and
the
repo
like
this
should
I
ideally
be
usable
by
any
project
any
repo
so
like.
If
we
had
this
come.
If
we
had
an
open
source
friday
on
this
channel
and
had
like
view,
come
on
like
we'd,
be
able
to
say,
hey
we're
just
going
to
change
these
quick
environment
variables
and
this
works
in
production.
B
A
B
A
A
B
B
A
A
B
B
A
B
A
A
B
Yes
and
then
you
would
basically,
as
you
generate
commands,
then
you
can
have
separate
gifs
that
show
up
as
well.
It's
pretty
much
it
this
thing's,
your
your
own,
your
own
little
peachy,
dress
dish
of
being
able
to
make
integrations
on
on
twitch,
but
yeah
they're,
all
labeled.
You
see
the
sound
effects
and
if
you
scroll
down
you'll,
see
sort
of
how
these
are
sort
of
handled
as
well.
B
A
A
A
B
Yeah
yeah,
honestly,
that
is
true
like
if
we
create
an
amv
file,
actually
that'd,
be
a
really
cool
little
problem
to
solve.
If
we,
if
we
want
to
keep
on
this
track
of
doing
these
live
streams
with
this
twitch
integration,
we
could
probably
make
this
thing
pretty
nice,
because
I
think
you
now
have
your
your
bearings
around
everything,
and
I
think
I
do
too
as
well,
but
I
guess
what
they're
what
they're
talking
about
is
like,
instead
of
putting.
A
B
At
least
these,
where
we
were
manually
entering
in
handles,
we
should
have
a
config
file
and
if
there's
no
config
like,
if
we
haven't
set
up
a
twitch
chat
integration,
we
should
actually
just
have
a
default
and
the
default
could
be
github.
The
default
could
be
bw
twitch,
but
we
should
have
a
like
default
set
or
database,
which.
B
Creep
basically,
where
this
you're
making
this
prop
this
project
way
too
complicated
databases
are
a
database,
would
be
great
too
as
well,
but
for
the
sake
of
going
through
the
process
of
sharing
and
how
to
build
this
thing,
we're
basically
doing
the
simplest
steps.
First-
and
I
I
didn't
mention
like
part
of
my
sort
of
love
for
doing
these
chat
integrations
on
twitch-
is
because
the
majority
of
twitch
chat
integrations
even
the
ones
that,
like
you,
can
leverage
they're
very
complicated.
B
So
if
I
go
to
look
at
the
code
of
different
chat
integrations
on
stream
elements,
I
have
no
context
of
how
we
got
to
this
point
and
I'm
expected
to
basically
use
this
and
then,
if
I
go
in
and
build
this
or
like
build
on
top
of
it,
then
I'm
like.
Oh,
I
had
just
so
much
learning.
I
have
to
do
so.
I've
intentionally
kept
this
simplistic,
where
it's
all
in
one
file,
all
the
gif
interactions.
The
index.html
is
super
simplistic.
B
B
B
B
B
A
A
B
A
B
B
B
B
A
A
A
B
Yeah,
that's
because
I
just
I
just
forced
to
commit
from
github,
so
if
people
didn't
know
that
you
could
do
suggested
changes
and
as
a
reviewer,
you
could
also
for
you
could
actually
commit
those
changes.
So
there
will
be
one
commit
from
me
on
on
your
branch,
which
tends
to
happen.
This
is
like
a
super
powerful
tool
because
as
a
maintainer,
sometimes
you
want
to
make
a
quick
change
that
doesn't
require
to
go
to
back
and
forth
again.
A
B
B
B
A
B
B
A
B
B
B
B
A
A
B
A
B
A
C
B
B
This
will
work,
hopefully,
okay
on
underneath
the
body
in
index.html,
where
I'm
at
you
should
be
able
to
add
a
div
okay
and
that
dim
should
have
a
class
called
content,
because
we
already
have
the
flexbox
there
we're
just
not
using
it
yeah
and
then
we'll
close
that
div
yeah
and
then
we'll
want
to
do.
One
of
these.
B
C
A
B
B
Every
time
it
actually
disappears,
so
the
inspect
element
will
be
expected
inspecting
only
for
10
seconds
until
it
goes
away,
so
we
could
potentially
use
the
chrome
console,
pause
the
element
and
then
inspect
it,
but
that
might
be
a
little
extra
work
similar
to
how
we
were
doing
earlier.
Trying
to
figure
out
this
websocket
stuff.
We've
got
all
the.
A
B
A
A
B
A
B
A
B
B
It's
yeah,
it's
all
restarting,
on
its
own
too,
as
well.
Yeah
are.
This
is
not
does
known
mod,
not
hot,
you
know.
Actually
I
think
you
have
to
restart
the
server
okay,
because
at
the
moment
the
way
no
mod
works.
It's
not
actually
pointing
to
the
investor
html,
because
that's
gonna
be
our
static
version.
Let's
do
npm.
A
A
B
B
B
B
B
A
B
B
So
the
way
this
works
in
the
way.
This
is
why
it's
kind
of
challenging,
because
we're
doing
again,
I
simplified
this
quite
a
bit,
because
I
didn't
want
to
use
a
javascript
library
to
make
this
work
for
the
sake
of
explanation,
but
we're
we're
trying
to
find
the
container
and
the
container
itself
is
defined.
B
B
A
B
B
B
B
B
A
C
B
B
No,
we
don't
need
a
gif.
The
gif's,
not
gonna,
not
gonna,
do
much
for
us.
Sorry,
I'm
deleting
the
wrong
stuff.
That's
right!
Let's
delete
some
of
this
white
space
too,
because
that
that's
not
gonna.
That's
gonna,
get
rejected
in
the
code
review
all
right
so
going
back
to
where
we
were,
I'm
just
I'm
just
undoing
exactly
what
we
did
and
we're
back
to
we're
kind
of
back
to
where
we
started.
B
A
B
B
B
B
A
B
B
B
B
A
A
B
A
B
B
B
B
B
A
B
B
B
B
B
B
B
B
And
then
push
it
up
to
your
branch,
so
that
way
it's
just
it's
available,
yeah
in
the
internet
and
then
we
could
actually
yeah
we'll
definitely
end
it
there.
I
enjoyed
this
because
I
think
we
had
oh
flex
direction
yeah,
so
we
had
the
display
yeah.
I
guess
that
kind
of
works.
Sorry,
I
have
just
one
more
erratic
change.
Coming.
B
Yeah
back
in
my
previous
life,
when
I
did
no
justify
content,
got
it
yeah
yeah
that
one
I
used
to
do
only
front-end
ui
work.
All
this
was
like
pretty
like
I.
I
was
doing
that
at
a
time
when
flexbox
was
getting
very
popular,
so
I
knew
all
the
stuff
by
by
heart,
but
it's
been,
it's
been
a
while.
That's
why
I
use
things
like
tailwinds
to
do
the
job.
For
me.
A
A
A
A
A
A
All
right,
so
you
feel
free
to
fix
that
whenever
and
then
we
can
daryl's
like
I
got,
he
got
both
his
job
and
our
job
done.
At
the
same
time,
that's
great
you
like
the
stream,
I'm
glad
we
have
a
shirt
yeah
every
do
we
have
a
schedule?
Well
we're
roughly
every
friday,
do
you
have
a
a
virtual
event,
meetup
page
for
your
next
one
already.
B
Yes,
so
we
have
a
meet
up
for
the
next
three
weeks,
so
tomorrow
we
actually
need
to
be
the
creator
of
the
octocat
web,
hooks
library
that
we've
been
using
I'll,
be
chatting
with
him
about
next
level.
Repository
management.
He
does
a
lot
of
automation.
His
name
is
gregor,
we'll
be
talking
to
him
next
week.
Sorry
we'll
be
talking
to
him
literally
tomorrow,
my
time
this.
A
A
So
vito,
you
know
I
both
put
up
the
link
for
the
actual
meetup
group,
which
is
where
we
post
all
of
these,
including
our
virtual
regional
meetups.
But
the
last
thing
that
I
just
posted
there
is
the
next
level
repository
management
with
octoher.
The
video
he's
been
talking
about
all
streams,
so
come
along
with
that
one.
If
you
want
to
keep
engaging
with
us
and
chatting
feel
free
to
come
and
we
don't
have
a
discord
but
feel
free
to
come
and
chat
in
our
community
community
forums.
A
So
jared
was
like.
I
don't
do
that.
Mr
just
tells
me
yeah
otherwise
b-doggy
and
I
both
stream
on
our
own
channels,
so
feel
free
to
come
and
chat
to
us.
Anytime,
like
I
mean
like
yeah
daryl's
over
like
you'll,
ask
me
like
when's
the
next
time
I'll
be
like.
Oh
it's
tomorrow,
it's
next
week
or
we
just
announced
another
one,
otherwise,
obviously
follow
us
on
twitter
as
well.
A
B
A
B
I
would
mention
that
we
did
have
a
home
assistant
on
last
week
and
the
whole
demo
that
we
did
was
actually
the
the
creator
of
home
assistant
who's,
also
the
maintainer.
He
had
a
light
just
behind
his
head
and
the
whole
demo.
Like
the
entire
time.
We
were
just
turning
the
lights
on
and
off.
So
if
you
don't
want.
B
A
A
Thank
you,
everyone
in
the
chat
for
being
awesome
and
giving
us
lots
of
you
know
ideas
saying:
oh,
you
know
that
close
lines
wrong.
I'm
just
chatting
with
us
and
being
part
of
this.
I
think
it
was
yeah.
I
probably
got
some
bad
advice.
Quite
works
now,
you're,
fine
yeah.
We
hope
you
had
a
really
good
time.
As
bw
said,
and
I've
said
we
do
these
quite
a
lot
so
come
along
be
part
of
it.
A
It's
really
fun
get
involved
in
community
forums
like
we
don't
have
discord,
but
yeah
jump
on
the
community
forums
and
be
involved.
That
way,
this
stream
will
be
on
open
source
friday
on
our
youtube
channel.
So
if
you
want
to
go
back
and
re-watch
it
you'll
be
able
to
and
we'll
always
do
a
dev
2
post
as
well
so
yeah
anything
else
that
friend.