►
Description
Learn how to contribute to AsyncAPI Initiative with our contributor guide https://github.com/orgs/asyncapi/discussions/483
A
A
You
left
me,
but
I
hear
you
clicking,
but
it's
because
of
the
delay
of
this
life
stream,
so
well
we're
waiting
for
for
Ace
to
join,
because
he
has
a
network
issues.
A
Today's
live
stream,
like
it's
gonna,
be
it's
a
first
live
stream,
we're
doing
that
is
dedicated
to
Oktoberfest,
so
we
want
to
start
with
Basics
and
the
basics
is
like
introduce
you
to
our
contributor
guides
for
happy
birthday.
Participants
and
I'm
also
I'll
be
the
one
that
will
play
the
role
of
a
contributor.
A
A
And
like
huge
request,
because
in
this
this
I
don't
know
how
to
call
it
like
this
live
streaming.
This
live
stream,
we're
doing
it
at
four
actually
16
UTC
time,
which
for
some
might
be
late,
like,
for
example,
it's
6
p.m,
and
for
folks
from
from
Europe
for
some,
it's
5
PM,
depending
if
you're
from
Portugal
or
or
England
or
the
rest
of
the
of
the
of
the
Europe
or
Ireland.
A
How
could
I
forget
about
Ireland?
So
just
let
us
know
like
give
us
feedback.
What
is
the
best
time
like?
When?
Would
you
expect
actually
to
have
such
live
streams?
What's
the
best
hour
to
actually
run
them
to
to
reach
your
life
in
life?
To
have
some
interactions
with
you
answer
some
questions
every
time
so
yeah,
please
give
us
that
feedback.
That's
pretty
important
for
us
and
now
I
see
that.
B
B
I'm,
just
having
a
little
bit
of
issue
with
the
audio
quality
I'm
getting
back
so
I
have
no
idea.
Why.
B
A
B
B
A
I'm
sorry
Mama
I
never
meant
to
hurt.
You
come
on
so.
B
A
Talking
like
for
eight
minutes,
I'm
talking
for
eight
minutes
and
nobody
I
mean
thank
you
Jonas
for
letting
me
know,
but
you
could
do
it
earlier
right
or
you
just
joined,
which
explains
so
yeah,
even
though
it
was
super
low,
I
hope
you
could.
You
could
at
least
understand.
What's
the
goal
of
this
live
stream
and
and
yeah
I
guess,
like
so
I'm,
not
sure
what
I
finished
so
yeah
I
I
think
what
I
introduced
already?
A
What's
the
what's
the
topic
for
today,
so
I
guess
we
can
already
go
into
playing
our
roles
where
you
are
a
maintainer
and
I'm
the
contributor
so
and
but
yeah
damn
it
because
I
forgot
like
we
did
this
live
stream
some
time
ago.
So
and
also
it's
it's
for
people
from
hacktoberfest.
So
there
can
be
many
people
watching
the
recording
later
that
are
not
so
much
familiar.
A
And
with
our
faces
so
maybe
Ace
also
like
before
we
start
talking
about
the
the
guide.
Maybe
we'll
also
talk
about
the
like
introduce
yourself.
Please.
B
Oh
hi,
everyone
I'm
Hayes,
I'm
Aziz,
but
I'm,
popularly
known
as
a
so
did
the
community
and
yeah
a
developer
relations
engineer
with
async,
API
and
yeah.
So
that's
a
little
bit
about
me,
but
I
do
I'm
more
engaged
in
the
community
and
I
also
help
you
know
contributors
a
lot.
That's
one!
That's
one
of
the
fun
thing
about
me:
I
love
every
contributors.
So
if
it
is
your
first
time
here,
you
know
I'm
looking
forward
to
saying
what
you'll
be
doing
with
us
and
yeah.
B
B
Yes,
so
yeah,
if
it's
the
first
time
you
know
coming:
oh
it's
your
first
time
finding
about
the
finding
about
instant
API.
So
it's
basically
it's
really
simple,
you
know,
is
actually
an
open
source
tool
to
easily
build
and
maintain
your
event
driven,
architectures
right
so
and
in
the
in
the
in
the
community
in
the
organizations
we
have
a
lot
of
tools
that,
as
a
contributor,
you
can
contribute
to
and
an
example
of
those
tools
are
Studio
the
the
Escape
their
website.
B
A
lot
more.
We
have
tons
tons
of
tools
you
can
contribute
to,
and
the
funniest
thing
is
you:
it
is
not
just
being
a
coder
right,
a
developer
to
contributor
with
ckpi.
We
have
all
set
of
of
issues.
You
can
contribute
tools
which
actually
range
from
documentation
to
design.
So
if
you
I
think,
if
you're
a
technical
writer,
yeah
you'll
feel
free
to
contribute
to
this
in
API
organization
and
join
the
community
and
also
if
you
are
into
design
you
know,
we
have
tons
of
design
issues
that
you
can.
B
You
can
jump
into
and
start
designing
right,
so
it
doesn't
matter
where
you
fall
into
this
category.
You
definitely
find
something
or
some
way
to
contribute
to
this
in
kpi
community.
A
A
So
let
me
maybe
share
my
screen
right
because
I
think
the
best
way
to
actually
teach
you
something
is
when
I
will
be
sharing
my
screen.
So
give
me
a
second.
A
A
Much
about
it
so
with
getting
like
did
it
get
better
when
I
made
it
larger.
B
Yeah
yeah
he
did
so
if
you're
watching
from
YouTube,
if
you're
watching
the
live
stream
from
YouTube
or
any
other
platform,
please
can
you
confirm
if
the
screen
sharing
is
clear,
foreign.
A
A
Okay,
but
I
also
actually
have
a
preview
on
YouTube
in
the
other
screen.
A
A
A
So
yeah,
finally
time
to
start
70
minutes
after
starting
the
live
stream.
That's
a
record!
So
I
sent
you
already
a
link
into
YouTube
and
and
twitch.
So
to
kick
off.
Our
support.
Overfest
is
created
two
guide
for
contributors
and
the
other
one
for
maintainers.
But
of
course,
that's
a
live
stream
for
contributors,
so
you're
the
most
interested
with
the
topic.
So
basically,
that's
your
like
the
best
way
to
start
us
with
factors.
A
The
dancing
API
is
to
go
to
to
go
to
this
guide
and
so,
and
the
most
important
is,
of
course,
to
familiarize
with
the
like
me
as
a
contributor
I,
obviously,
and
like
there
are
two
basic
things
about
open
source
and
about
certain
open
source
projects.
Is
that,
like
the
project
that
is
like.
A
Maintained
in
a
good
way,
I
don't
want
to
say,
maintain
in
a
good
way
that,
like,
if
somebody
doesn't
have
a
contributor
guide,
is
not
maintained
in
a
good
way.
I
mean
if,
if
the
project
wants
to
build
a
community
and
they
encourage
the
the
contributions
they
need
to
have
contributing
guide.
So
that's
a
default
like
every
project
that
actually
expects
contributions
should
have
a
contribution
guide,
so
I
definitely
discourage
you
to
go
to
projects
that
don't
have
it
now.
A
The
other
part
is
when
there's
a
it's
a
small
project
with
just
like
two
contributors:
three
countries,
Beyond
contributors-
you
probably
should
not
expect
them
to
have
code
of
conduct,
because
why
would
you
in
such
a
small
group
but
in
case
of
larger
projects
like,
for
example,
as
an
API?
A
You
should
not
only
familiarize
yourself
with
the
contribution
guide,
but
also
with
the
code
of
conduct
of
the
project,
to
make
sure
that
if
you
join
the
project
and
start
interacting
with
the
community,
you
do
it
in
a
respectful
way
by
following
all
the
rules
that
are
described
in
the
code
of
conduct.
But
it's
also
for
your
advantage.
Code
of
conduct
is
not
just
to
protect
maintainers
but
actually
protect
contributors.
So
you
basically
know
what
rights
you
have
in
the
project.
A
A
You
just
have
to
look
into
the
contributing
guide
and
code
of
conduct,
we're
going
to
start
with
picking
the
right
issue
and
talking
about
actually
how
to
start
interacting
because
it
sometimes
it
depends
on
the
project
but
the
best
practice,
at
least
from
in
my
Bible,
from
my
point
of
view,
best
practices
that
you
start
contributing
to
the
project,
things
that
are
useful
for
the
project.
You
discussed
it
with
the
community
or
there's
already
an
existing
issue
in
some
repository.
A
When
you
just
come
to
the
project
edit,
some
readme
add
some
like
missing,
comma
or
missing
dot
at
the
end
of
the
of
the
sentence,
and
you
open
up
a
request:
you're
thinking,
you're
helping
but
you're,
not
very
much
helping
you're,
actually
disturbing
a
bit
contributors
and
and
other
contributors
and
other
maintainers
in
the
project
because,
like
if
you're,
if
you
want
to
be
a
good
citizen
in
open
source-
and
you
want
to
come
to
like
get
really
experience
in
in
hacktoberfest,
do
it
the
right
way
like
just
don't
do
it
for
the
swag?
A
You
just
have
to
do
four
contributions
in
one
month,
so
that's
not
really.
A
lot
in
in
one
month
span
so
so
try
to
learn
really
how
what
it
is
to
contribute
to
open
source,
how
much
effort
it
needs
and
and
and
see
how
grateful
contributors
are
maintainers
are
when
they
get
contribution.
Super
cool
feeling
that
I
remember
when
I
had
when
my
first
pull
request
in
open
source
got
approved
when
you
have
this
feeling
that
you
actually
did
something
useful
and
and
make
for
for
a
given
community.
A
So
that's
my
first
advice
for
for
you
as
a
person
coming
to
a
project
from
a
from
Oktoberfest,
so
looking
from
asking
API
perspective
exactly
so
as
I
said,
make
sure
that
you're
doing
something
meaningful.
So
there
are
two
ways
like
we
have
dedicated
dashboard
with
issues
that
are
labeled
as
hacktoberfest.
A
We
don't
have
many,
it's
just
12
issues
out
of
120
costs
that
were
already
closed
in
the
past
in
whenever
we
took
part
in
the
Oktoberfest,
because
now
it's
our
third
year,
so
that's
the
first
place.
We
should
go
and
explore
like
what
issues
you
can
pick
up
and
contribute
to
the
project,
because
if
something
is
marked
as
Octoberfest,
that's
it's
marked
intentionally
because
on
the
maintainers
can
add
labels.
A
So
that's
the
best
issues
to
pick
up,
but
sometimes
you
don't
feel
that
it's
the
best
you
can
do.
You
might
feel
that
some
issues
are
too
difficult
or
to
trivial.
You
don't
want
to
do
just
a
simple
docs
fix.
You
actually
would
like
to
contribute
some
code,
for
example.
Then
there's
another
way
and
this
way
is
basically
contact
maintainers
and
ask
them
what
else
you
could
do,
except
of
the
issues
and
just
explain
that
you're
a
Oktoberfest
participant.
So
we
have
a
and
you
find
it
in
the
guide
from
Ace.
A
A
How
do
I
start
I
looked
into
the
issues
that
you
proposed,
but
I'd
like
to
get
something
different
like
I'd
like
to
get
some
issues
about
where
Java
is
involved,
for
example,
and
and
I
I
can
assure
you
that
one
of
the
maintainers
will
jump
in
and
help
you
out
to
find
something
useful
that
you
can
contribute,
or
actually
just
point
you
to
a
proper
person
that
you
can
ask
for
for
mentoring.
A
Okay,
so
far,
so
good
and
yeah,
then
setting
up
the
environment,
sometimes
it's
specific
for
a
given
repository.
So,
of
course,
like
yeah,
that's
something
needed
that
you
have
to
do
and
I'll
gonna
show
you
how
I
do
it
and.
A
A
So
always
make
sure
that,
like
whenever
you
open
up
request,
you
make
sure
that
everything
that
you
did
was
according
to
the
contribution
guide,
that
you
have
a
correct,
PR,
title
and
stuff
like
that,
but
yeah.
Let's,
let's
really
see
the
contribution
flow
in
action.
A
In
the
meantime,
let
me
know
in
the
in
the
channel
if
everything
is
correct.
The
quality
of
the
video
and
the
sound
and
everything
I'm
saying
so
far
is
Clear.
Remember
ask
questions.
We
have
the
questions
the
chat
rendered
in
the
live
stream.
So
we
see
your
questions
coming
so
yeah
ask
them
so
yeah
now
I'm
playing
the
role
of
contributors,
so
yeah
there's
an
issue.
I
want
to
pick
up
actually
an
issue
that
I
created
before
the
before
before
this
live
stream.
A
So
we
can
already
see
I
went
to
the
repo
I
actually
checked.
The
readme
I
saw
some
mistakes
in
the
readme
in
the
chatbot
repo,
actually
I
choose
to
chatbot
repo,
because
Ace
is
maintainer
in
this
repo.
So
actually
he
can
approve
my
pull
request
in
the
end
of
this
live
stream
and
we
can
get
it
matched
but
yeah.
Let's,
let's
let's
go
to
this
issue,
yes
and
I,
see
and
I
think
you're
in
the
live
stream
or
not
so
yeah.
A
That's
I
hope
you
noticed
after
making
a
comment
that
you
worked.
I
want
to
work
on
that.
You
notice
that
it's
actually
already
booked
by
me
so
I
definitely
don't
want
you
I'm
hot
to
your
time
on
this
issue,
because
I'm
gonna
do
it
now
during
the
live
stream.
A
So
yeah
I
find
I,
find
an
issue
and
I
do
what
did
so?
I
write
a
comment:
hey
that's
the
issue.
I
want
to
work
on
during
the
Oktoberfest.
Let
me
do
it:
we
don't
assign
issues
addressing
API
like
because
in
open
source
you
at
some
point
of
time.
You
learn
that
assignments
are
don't
make
much
sense.
It's
because,
like
people
sometimes
come
assign,
say
assigned
to
me
and
then
they
just
gone.
A
Never
come
back
and
this
assignment
is
actually
sometimes
confusing,
but
because
it
looks
like
somebody's
working
on
the
issue,
but
they
they
aren't.
So
that's
why
we
don't
use
much
assignments,
I
think
some
people
do
but
I
personally,
don't
and
I
think
most
of
the
maintainers.
Don't
so
just
use
comments
and
yeah,
so
I
have
description
what's
in
to
fix
in
the
readme
and
I'm.
Don't
have
to
ask
more
questions
normally,
just
ask
more
follow-up
questions
to
the
maintainer.
If
something
is
not
clear
and
and
yeah.
A
So
yeah
summary
of
contributions,
something
I
talked
about
open
issue,
discuss
open,
pull
request
and
get
it
approved,
merge
code
of
conduct
and
yeah
the
most
important
like
so
when
you
like.
You
want
to
work
on
the
issue.
You
know
what
has
to
be
done
in
the
issue.
You
go
to
pull
request
and
I
highly
encourage
you
to
to
read
contribution
guides
because
there's
one
document
super
important
that
is
linked
in
this
contribution
guide.
A
That
I
definitely
encourage
you
to
follow
to
actually
set
up
your
your
first
contribution
in
a
in
a
right
way.
So,
let's
open
the
git
workflow
document
and
it's
yeah
instructions
prepare
a
fork
right,
so
GitHub,
it's
a
place
where
he
host
repositories,
but
if
you
want
to
contribute
in
open
source
common
practice,
is
that
and
it's
actually
by
default?
It's
not
just
a
common
practice.
If
you're
from
outside
the
organization,
you
don't
have
rights
to
to
make
any
modifications
in
a
given
GitHub
organization.
A
You
basically
are
not
able
to
push
any
code
to
the
Upstream
you're
not
able
to
to
push
any
any
to
create
branches
in
in
some
existing
repositories.
You
have
to
make
a
copy
of
the
repo,
so
basically
you
have
to
Fork
the
repo
so
to
Fork
the
repo
you
just
go
to.
A
A
And
yeah
create
Fork
and
now
you're
gonna,
see
like
I'm
I
call
myself
experience
maintainer,
let's
say
and
I
now
will
show
you
like
domestify,
that
when
people
think
that
that,
like
somebody's
senior
or
somebody's
experienced,
they
probably
use
just
terminal,
they
use
git
in
terminal
they
use,
they
probably
have
even
veeam
editor
where
they
write
code
and
probably
even
browser
they
browse
through
the
terminal.
So
so,
no
so,
for
example,
what
I
do
I
always
click
here
and
I'm
a
huge
fan
of
GitHub
desktop?
A
A
So
I
can
show
you
GitHub
desktop
and
why
do
I
I
don't
use
GitHub
CLI,
for
example,
or
git
CLI
native
kit.
Cli
is
because
I
just
respect
people
that
created
a
GitHub
desktop
if
they
spend
their
time
on
it.
We
should
use
it
so
yeah.
Let
me
share
my
screen,
but
with
the
with
the
desktop
GitHub
desktop.
A
Okay,
so
basically,
when
I
clicked
on
the
green
button
and
I
had
already
GitHub
desktop
installed,
it
immediately
opened
a
a
new
new
clone
of
repo
and
it
detects
that
I
have
this
Fork
on
my
local,
so
I'm,
just
gonna
I'm,
just
gonna
do.
A
Let's
just
remove
me
later
because,
anyway,
later
I'm
gonna
just
remove
this
temporary
Fork
that
I
just
created
so
I
get
the
the
repo
cloned
and
again
my
usual
work.
Workflow
looks
like
this:
I
create
a
repo
like
I
clone
repo
locally
and
from
this
Fork
I
click
on
open
in
Visual,
Studio
code
and
yes,
I
know
in
the
terminal.
A
I
can
most
probably
just
do
git
clone
the
repo
and
then
I
can
enter
the
the
cloned
repo
enter.
The
directory
and
I
can
also
do
code
space
dot
to
open
vs
code
from
a
given
root
repo
but
I'm.
Just
old
and
I,
like
my
habits
and
I
just
use
my
habits
from
the
past,
even
though
I
know
I
can
do
it
quicker
and
faster.
A
Now,
yeah.
Now
the
third
application
I'm
going
to
show
you
now
is
the
vs
code.
I
think
it's
vs
code.
A
A
After
clicking
the
button
opening
Visual
Studio
code,
Visual
Studio
code
open
for
me,
so
that's
my
go
to
editor
for
for
files
and
so
in
the
navigation.
I
I.
Don't
do
anything
yet
because
now
it's
important
to
notice
one
thing
when
you
Fork
the
repo
and
when
you
clone
the
repo
to
your
local,
you
are
still
on
a
master
branch
of
your
fork,
as
you
can
see
here
at
the
bottom
left.
A
A
The
system-
oh
my
I,
can't
cheat
the
system.
Okay,
so
I'm,
not
gonna,
okay,
I'm,
actually
I
can
show
it
to
you
differently.
So
let
me
open
a
terminal
inside
the
inside
the
vs
code,
so
I
can
show
it
to
you
here.
A
And
it's
going
to
set
up
in
a
second
yeah,
and
so
we
can
see
I
so
I
I
have
my
own
plugin
and
not
even
plugin
I
just
configured
my
my
terminal
in
the
way
that
it
shows
me
it
hides
my
my
home
directory,
and
it
just
shows
me
what
branch
I'm
I'm
on
in
a
given
terminal
session.
So
you
can
see
that
I'm
on
a
fork
but
I'm
still
on
the
master
and
and
how
now
it's
a
super
important
part.
A
So,
let's,
let's
go
back
to
the
let's
go
back
to
the
instruction.
A
Because
now
we're
going
into
next
steps
of
this
git
workflow
kit,
workflow
instruction.
A
Okay,
okay,
so
you
can
see
the
the
instructions
so
in
the
instructions
we
talk
about,
actually
how
to
configure
your
fork
on
local
to
make
sure
it
works
properly,
because
the
by
default,
when
you
clone
the
repo
to
your
local,
the
master
branch
that
you
have
in
your
fork
is
not
the
same
as
the
master,
Branch
or
main
branch
in
the
in
the
Upstream
in
async
API
chatbot.
In
this
example,
it's
your
fork
master.
A
So,
let's
say
while
I
contribute
and
somebody
opens
different,
pull
requests
in
chatbot
and
they
get
them
merged
into
the
master
on
asking
API
chatbot.
A
My
local
Master
will
not
get
these
updates
automatically
I'm
not
going
to
be
able
also
in
quick
way
to
get
these
updates
from
the
Upstream,
which
means
that
my
master
will
be
out
of
synchronous,
sync
with
the
with
the
app
stream
with
asking
API
chatbot,
which
basically
means
that
once
I
make
another
contributions,
I
get
a
bunch
of
conflicts
because
all
suddenly
my
base
Branch,
where
I
started
working
on
things,
is
not
necessarily
the
same
as
what
we
have
on
the
upstream
and
some
strange
things
start
happening
to
the
project.
A
You,
for
example,
see
that
your
in
your
pull
request,
you
have
changes
that
are
actually
already
in
the
master
and
it's
super
confusing
and
we
I
say
it
on
my
own,
like
regularly
at
least
once
a
month.
Somebody
has
such
issues
with
with
a
proper
configuration
of
of
fork
when
they
want
to
contribute
to
the
project.
So
don't
go
this
path
now,
I'm
gonna,
I'm,
gonna,
again
skip
to.
A
So
this
instruction,
it
gives
you
two
options
you
can,
especially
if
you
want
to
contribute
like
really
really
long
term,
not
just
one
not
just
to
pull
requests,
but
actually
more,
it's
very
useful
to
not
go
through
the
configuration
like
manually.
A
Every
time
you
configure
your
fork,
especially
if
you
want
to
contribute
to
many
projects,
not
just
chatbot
but
actually
also
websites
back
Etc.
Then
I
always
recommend
to
use
the
the
script
that
I
prepared
some
time
for
for
the
community
and
that's
how
basically
I
I
do
things
so
I'm
gonna,
I'm
gonna
now
go
through
this
instruction
and
show
you
like
how
it
how
it
should
be
executed.
A
And
yeah,
so
what
I
do
like
I,
basically
by
following
the
instruction
I
just
went
to
my
guest
I,
took
the
script
that
I
have
I
added
it
to
my
bash
configuration
as
well,
so
basically,
I
have
all
the
instructions
already
in
the
script.
A
So
what
I
do
usually
I
just
do
con
of
Fork,
so
I
have
my
own
git
command
and
I
and
I
know
that
it
accepts
three
parameters,
which
is
the
the
origin
of
the
repository
that
I
forged,
which
is
async
API
organization,
the
or
the
original
name
of
the
Repository
chatbot
and
and
the
the
main
branch.
In
this
case
it's
Master
branch
and
I
hit
enter
and
this
the
script
configures.
For
me,
everything
but
I
think
it's
nice
always
before
you
automate
things
to
actually
do
things
manually.
A
So
this
is
what
we're
gonna
do
we're
just
gonna
go
through
this
instruction
manually.
So
first
you
check
like
if
you
have
like.
Maybe
you
forgot,
you
have
this
Fork
already
configured,
so
you
basically
check
the
the
origin
and
the
Upstream
information
and
the
the
origin
points,
obviously
to
your
to
your
fork.
A
So
you
see
it's!
It's
not
asking
API,
it's,
it's
I!
Think
it's
terberg.
So
it's
in
this
case,
like
the
the
origin
of
the
repo,
is
my
Fork
so
and
the
same
information
is
the
Upstream
you
sometimes
you
don't
have
it
so.
Basically,
that's
why
the
instruction
that
we
have
tells
you
to
add
the
Upstream,
so
actually
the
information.
Where
is
the
the
Upstream,
the
original
repository
located?
A
But
in
this
case
we
in
case
of
this
chatbot
when
I
cloned
and
check
the
information
about
remotes
I,
see
the
origin
and
the
Upstream.
So
we
can
skip
to
step
three
of
the
instruction
where
we
will
fetch
the
master
Upstream.
A
Okay.
So
now
we
are
sure
that,
like
the
the
apps
Upstream
Master
is
up
to
date
and
what
we
do
with
the
last
step
of
the
instruction
as
simple
as
that
we
just
do.
A
We
basically
link
our
origin
Master
with
the
Upstream
master.
So,
basically,
next
time,
when
you
do
git
pull.
A
You
are
sure
that
you're
not
actually
get
pulling
from
from
derberg
slash
chatbot,
but
you're
actually
keep
pulling
from
asking
apis
like
chatbot,
and
it's
super
Nifty.
It's
it
speeds
up
the
work
because,
like
you
like,
you,
can
update
your
local,
even
though
it's
Fork,
but
you
can
update
it's
like
update
it.
Like
it's
Upstream,
it's
very
useful.
A
Now,
once
we
have
the
master,
the
local
Master
configured,
we
need
to
cut
out
the
that's
at
least
one
of
the
names
we
have
for
it
like
cut
out
the
the
branch
that
you
want
to
work
on,
so
never
work
on
the
master
always
create
new
Branch
for
every
single
contribution,
so
git
check
out.
A
The
beauty,
actually
the
beauty
of
using
shortcuts
is
that
I
don't
remember
how
to
create
a
branch
so
I'm
gonna
just
do
git
check
out
branch.
That's
what
I,
what
Elias
I
have,
but
also
I
can.
A
Edit
bash
I
think
is
my
my
secret
script.
Yeah.
So
I
can
see
my
Elias
Alias
that
I
have
and
my
Alias
for
git
checkout
branch
is
oh
yeah,
so
we
could
check
out
B.
A
A
So,
let's
do
git
check
out
B
and
the
branch
name
will
be
fix.
Read
me
Octoberfest,
okay,
so
that's
that's
your
basic
setup
when
you
want
to
start
making
actually
some
changes
in
files
you
and
the
setup
prior
to
creating
the
the
custom
Branch.
This
is
something
you
do
just
once
after
forking,
the
repository
of
course.
When
you
want
to
contribute
to
another
project
from
using
API,
you
have
to
Fork
it
again.
A
You
have
to
configure
it
again,
but
it's
just
one
time
configuration
and
and
later
you
just
you
just
do
like
when
you
finish
your
branches
is
merged
and
your
pull
request
is
merged.
You
just
do
and
get
to
check
out
master
and
you
do
kit
pool
git
pull.
A
So
you
pull
again
the
changes
that
are
in
the
Upstream
in
async
API
slot,
slash
chatbot.
Let's
go
back
to
the
branch
where
we
want
to
make
changes.
A
And
because,
like
that's
usually
how
we
talk
overviews
also
BRS
are
not
really
important
and
should
be
used
in
markdown,
because
GitHub
is
adding
a
break
line
after
every
single
heading.
And
if
we
add
it,
then
it
looks
strange.
A
Now
the
the
second
part
of
the
of
the
issue
was
to
get
rid
of
coming
soon
stuff
because,
like
actually
in
the
stuff,
where
are
that
they're
like
18
13
months
ago,
I
think
so
obviously,
sometimes
you
just
can't
do
things
in
a
given
project.
You
have
to
jump
to
another
one,
so
it's
not
good
practice
to
say
coming
soon,
because
you're
making
promises
that
actually
are
hard
to
to
accomplish.
So,
let's,
let's
make
sure
that
we
don't
talk
about
anything
coming
soon.
A
A
Docker
there's
an
issue
for
it,
so
we
don't
have
to
say
it's
coming
soon
like
when
we're
gonna
have
it
we're
just
gonna,
add
it
and
in
case
of
contributing
we
should
have
like.
Actually
we
have
contributing
MD
so
which
you
said
should
have
preheat
more
in.
A
Yes,
it's
correct
contributing
MD
is
opening,
so
that's,
that's!
That's
it
to
contribute
the
changes,
so
the
most
important
actually
Improvement
here
is
the
is
the
getting
rid
of
stuff
that
we
promised
that
are
coming
soon
and
something
important
to
notice
like,
even
though
these
are
some
trivial
changes
that
could
apply
to
every
repo
they
not
necessarily
have
to
async
API
consists
of
60
different
repositories
with
different
maintainers.
In
this
case
me
and
A's
are
maintainers,
so
we're
okay
to
make
this
cleanup
with
other
repositories.
A
A
So
yeah,
that's
all
saved
and
now
I
know.
I
know
in
the
terminal.
I
could
now
just
commit
all
push
it
open
and
pull
requests
Etc,
but
I'm
not
gonna.
Do
it
because
that's
not
how
I
do
things
I
use
git
in
CLI
only
to
really
set
up
the
fork,
pull
from
the
master
and
and
create
branch,
and
that's
it
and
and
then
later
I
just
really
switched
to
GitHub
desktop,
so
we're
gonna.
Do
it
again?
A
This
needs
to
improve
what
was
the
name.
It's.
A
So
why
I
actually
do
it
like
why
I
don't
use
the
terminal
again?
It's
like
habits
like
as
I
said,
like
I'm
old
I,
have
my
habits
and
stuff
that
work
for
me
as
always,
and
I
I.
Basically,
as
I
I
started
in
Tech,
not
essay
coder,
first
I
I
just
did
not
believe
in
myself.
A
I
was
I
thought
that
I'm
crappy,
coder
and
I'm
not
like
I
finish,
computer
science
and
I
thought
like
I'm,
basically
useless
so,
but
I
knew
English,
so
I
said
like
yeah
I
can
at
least
do
technical
writing
so
when
I
was
really
starting
practicing
many
times
many
years
ago,
I
to
understand
git
in
a
better
way,
especially
that
it
was
something
coming.
That
was
something
new
when
I
started.
A
There
was
not
too
much
guides
about
it
so,
and
there
were
many
different
tools
like
not
even
GitHub
desktop
I,
don't
remember
when
it
was
something
that
was
later
acquired
by
atlasian,
so
I
really
enjoyed
having
a
visual
clients,
because
I
could
always
easily
spot
like
on
the
left.
Yeah,
you
can
see
the
list
of
files
that
got
changed
and
on
the
right,
always
when
you
click
on
the
given
file,
you
can
see
what's
actually
being
removed
from
Define.
What's
added
I
simply
prefer
this.
A
It's
I'm
person
that
use
eyes
that
has
this
passion
for
design,
which
is
total
false,
but
yeah.
What
so?
What
I
do
now
I
I
commit
this
change
in
the
readme
and
I.
Do
something
like
actually
talks,
docs,
colon
and
I
say
update,
actually
remove
remove
calming
soon
from
readme.
So
the
the
comment
method
message
has
to
say:
what
is
it
doing,
what
it's
introducing?
A
What
change
it's,
introducing
in
the
in
the
project
and
I'm
going
to
talk
about
this
in
a
sec,
this
strange
prefix,
so
just
what
I
click
I
just
commit
to
the
branch
and
I
click
on
publish
branch.
A
And
that's
another
reason
why
I
use
GitHub
desktop
because
it's
it
has
this
button,
create
pull
request
and
this
button
takes
me
directly
to
GitHub
to
the
create
pull
request
View
of
a
given
a
given
change.
So
I
can
see
like
that.
My
my
change
will
go
to
RC
API,
both
a
chatbot
to
the
master
branch,
and
it's
going
to
go
from
my
Fork
from
this
specific
branch
and
I
see.
A
My
comment
is
already
used
as
APR
title
I
see
the
some
template
so
I
can,
in
the
description
I
can
say,
update
readme
to
remove
coming
soon
remove.
A
Break
break
lines,
is
it
break
lines
or
brake
lines?
Prayer,
no
break
right,
damn
it
like
it's
brake
lines:
okay
and
yes
and
yeah
the
and
the
last
important
part
is.
A
Oh
I
hate
you
GitHub
for
doing
it.
Oh
yeah
resolves
this
particular
issue
when
I
do
it
this
way
it's
once
we
merge
the
pull
request.
It
will
automatically
close
the
issue.
So
it's
a
nicer
automation
that
comes
out
from
GitHub
by
default
and
yeah.
Let's,
even
though
I
have
a
correct,
PR
title,
I'm
gonna
break
it
and
basing
on
the
way
I
break
it.
I'm
actually
gonna
explain
what
this
prefix
is
and
that's
the
last
step
of
the
contribution,
so
yeah
create
a
pull
request:
hey
maintainer.
A
Things
happening
to
the
pull
request
like,
for
example,
we
have
sonar
Cloud
checks,
enabled
that
check
the
quality
of
the
code
or
do
some
security
scans.
We
also
run
many
different
things
by
default,
like
testing
in
case
there
are
some
tests,
but
I,
don't
think
Ace
provides
a
test
for
the
chatbot
and
the
important
check
is
lint
PR
title
lint
PR
title
and
why
it's
so
important,
so
in
the
contributing
guide
you
have
this
section,
which
is
called
conventional
comment,
something
that
not
all
open
source
projects
adopted.
A
We
adopted
it
strongly
and
it
is
super
cool
because
it
allows
you
to
automate,
because
if
you
have
and
we're
following
conventional,
commit
specification
that
you
can
read
more
about
later,
but
it
there's
basically
a
spec
where
that
defines
how
the
prefix
should
be
named
to
trigger
later
some
automation,
if
you
have
one
in
place.
So,
for
example,
when
you
do
a
pull
request
that
has
a
feet,
prefix
and
you're
using
semantic
relays
package,
then
you
have
proper
Automation
in
place.
Then
it
can
figure
out.
A
A
A
B
A
A
A
A
So
we
can
only
just
finish
here
and
it's
provide
so-called
dry
explanation.
So
not
interactive,
not
really
showing
things
in
life,
but
basically
saying
what
will
be
the
next
thing.
So
the
next
thing
would
be
like
if
the
actions
would
work
and
the
test
would
go
green,
but
the
linked
PR
title
would
be
red
and
it
would
be
red
because
the
the
automation
that
we
have
in
place
would
figure
out
that
there's,
no,
that
there
is
no
prefix
in
the
pr
title,
and
we
also
the
cool
stuff
I
wanted
to
show.
A
Is
that,
like
one
of
our
contributors
added
super
cool
automation,
where
we
also
like
we
don't
just
show
that
it's
red,
but
actually
our
bot
makes
a
comment
to
the
pull
request
and
says,
like
Hey,
we're
following
conventional
comments
here
and
provides
examples
of
different
prefixes
that
you
can
use
so
but
yeah.
We
can't
show
it
to
you.
So
basically
that
would
green.
A
That
would
turn
red,
but
then
I
would
just
go
to
edit.
A
Fix
it
save
it,
this
action
of
saving
would
trigger
automation.
Again,
it
would
turn
green,
and
only
then
is
the
moment
where
really
a
A
maintainer
can
actually
merge
your
pull
request
because
certain
automation
is
mandatory,
so
even
maintainer
doesn't
have
power
to
merge
a
pull
request
that
has
some
automated
checks
failing.
So
your
last
step
is
not
credible
request.
A
Your
last
step
as
contributor
is
to
create
a
pull
request
and
make
sure
that
all
the
checks,
automated
checks,
actually
turn
green
and
if
they
not,
if
they
don't
check
the
locks,
if
you
don't,
if
you
can't
figure
anything
from
the
logs,
then
in
add
comment
asking
maintainer
for
support
and
then
maintainer
will
help
you
out
tell
you
what
has
to
be
fixed.
A
Sometimes
maintainer
can
be
delayed.
It's
like
maintainer
will
not
answer
in
five
minutes.
After
creating
the
request.
Sometimes
they
will
answer
the
next
day,
so
just
be
patient,
but
in
hacktoberfest
we
know
it's
just
one
month.
So,
like
always
try
to
like
after
one
day
ask
in
the
comments
like
hey
is
there
anything
I
can
do
to
speed
up
the
merging
Etc,
but
if
everything
goes
well,
it
gets
green.
Then
you
have
such
nice
maintainer
as
A's.
Adding
comments
like
well
done.
A
I
know
it's
well
done
because
I
did
it,
then
he'll
just
accept
and
and
merge
and
kaching
first
contribution
done
at
school
how's
that.
B
No
you,
you
did
absolutely
great.
Oh
my
gosh
yeah,
that
was
that
was
I'm
gonna
rate
you
a
hundred
of
a
hundred.
That
was
a
really
nice
option,
thanks
so
I'm
gonna
add
up
a
couple
of
things
from
the
contributors
perspective
yeah.
B
So
as
a
contributor,
if
you
are
having
Asus,
you
know,
maybe
setting
up
your
local
environment
and
an
example
is,
if
you
contributing
to
the
website
or
the
doc
section
in
the
website
and
you're
using
Windows
right
and
you
follow
the
normal
guide
of
such
or
new
representators
setting
up
locally
and
for
some
reason
you
have
you're
facing
some
challenges
in
in
accessing
some
particular
pages
in
the
dark
right
and
yeah.
So
we
have
that
particular
issue
because
it
is
Windows
related
yeah.
So
we
have
some
alternative
ways
of
of
doing
it.
B
But
if
you
can,
if
you
can
find
it
right
or
you
have
an
hard
time
figuring
how
to
set
it
up,
you
know
if
you
feel
free
to
reach
out
to
hi
Young
on
the
in
the
in
the
slack
channel.
We
are
always
willing
to
hop
on
a
call
with
you
or
have
a
quick
chat
until
it
will
resolve
your
issues,
and
this
doesn't
have
to
be.
You
know
about
environments
setting
up
right.
B
A
Perfect
thanks
for
adding
this
I,
don't
see
any
comments
coming
in,
so
we
either
put
people
in
sleep,
I,
think
at
GitHub
actions
and
the
status
of
GitHub.
A
So
yeah
I
think
we
can
finish
it
like
10
past
almost
10
past
I
have
to
go
and
feed
my
kids
and
yeah.
So
from
that
thanks
a
lot
I
think
we're
gonna.
A
Do
it,
especially
in
October,
more
regular,
so
stay
tuned
with
async
API
on
any
channel
you
you
prefer
and
remember
like
in
one
month
we
have
an
conference,
you
can
go
to
conference.assing
api.com
to
learn
more,
but
it's
basically
an
asking
API
Community
Conference,
where
we
don't
have
only
presentations
about
using
casting
API,
passing
API
specifications,
API
tools,
but
also
we
have
presentations
from
contributors,
so
we're
looking
for
some
mentorship
or
some
inspirational
inspirational
talks
from
people
that
decided
to
contribute
to
open
source
and
how
it
ended
up
for
them.
A
Thank
you
and
enjoy
the
rest
of
the
day.
Bye.