►
From YouTube: The GitHub CLI - Open Source Friday
Description
This is our VOD (recording) from the Open Source Friday live stream on the 9th October 2020, 5pm AEDT. We interviewed Mislav Marohnić from the newly launched GitHub CLI. We talked all about Open Source; what it is, how to get involved, what the community is like. Mislav has been in the Open Source community and working as a maintainer for over 10 years so he has lots of words of wisdom.
Join MishManners and friends live for Open Source Fridays at https://www.meetup.com/GitHub-Virtual-Meetup
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
Google+: http://google.com/+github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Hello,
everyone
and
welcome
in
to
the
open
source,
friday
stream,
and
it's
not
working
hello.
We
working
yeah
we're
working
just
want
to
double
check.
We've
also
had
some
fun
times
with
the
nice
obs
update.
So
thank
you
and
well
done
obs
for
releasing
your
version
26
and
messing
with
all
my
audio
settings,
hello,
hello,
everyone
welcome
and
good
morning
to
all
those
on
the
other
side
of
the
pond
and
good
afternoon
to
all
those
here
in
australia,
new
zealand
and
on
apac
time
zone.
A
A
We
have
that
coda,
41h
invisible
programmer,
fantastic
cow,
mods,
navi
glock,
mike
hello,
everyone
so
excited
to
have
you
all
here,
and
I
am
very,
very
excited
today
to
have
a
really
really
awesome
guest
with
us
here
today
we
have
miss
lab
from
the
github
cli
team,
and
this
slime
has
told
me
that
he's
got
up
very,
very
early
just
to
be
here
just
to
chat
to
you
all
about
how
amazing
the
github
cli
is.
So,
let's
all
welcome,
miss
live
to
the
stream
how's
it
going
miss
lab.
B
A
A
We
have
lee
riley
in
the
chat
saying
it's
beer
o'clock
in
california
too.
It's
like
really
just
look
at
my
watch
here.
I've
got
the
world
time
zone
on
my
watch
and
I'm
pretty
sure
is
either
well
past
4
o'clock.
It
says
in
san
francisco.
It's
all
eight
past
11
p.m
in
the
evening.
So
I
suppose
it's
still
3
o'clock,
but
it
is
a
thursday
night
still
for
you
in
california,
over
in
san
francisco,
say,
hey
exo
great,
to
have
you
here
again
now.
Miss
slab
tell
us
a
little
bit
about
the
github
cli.
A
B
We
are
really
proud
of
the
fact
that
we
put
up
this
like
really
stable
release
that
seemed
to
work
really
well
for
the
audience
that
we
wanted
to
make
it
for
and
now
for
our
team.
That's
just
kind
of
the
beginning,
because
we
wanted
to
put
this
first
release
out
there
as
like
a
bare
minimum
that
we
could
imagine
putting
something
that's
called
1.0,
and
now
we
get
to
find
out
what
are
all
the
other
things
that
we
could
build
into
it
and
what
makes
sense
to
be
in
a
github
cli.
B
A
Pretty
cool,
so
if
you
haven't
downloaded
it,
you
can
go
jump
over
to
the
website
and
download
it
here.
But
I'm
keen
to
hear
from
the
chat
who
has
actually
had
a
play
around
with
the
github
cli
recently
like
who's
played
with
it.
What
are
you
doing
with
it
and
how
are
you
using
now
for
those
of
them
people
in
the
chat
who
don't
know
what
the
github
cli
is
mislab
tell
us
what
the
github
cli
is
all
about.
B
Well,
if
anyone's
like
me,
then
they
spend
a
lot
of
time
in
a
terminal
because
for
developers
this
is
just
what
a
lot
of
tools
already
are
and
myself.
I
also
am
a
heavy
git
cli
user
as
well,
so
it
was
the
place
where
I
do
version
control
and
do
most
of
my
development
tasks.
So
we
decided
that
it
makes
sense
that
a
lot
of
also
the
git
up
features
like
issues
and
pull
requests
and
similar
things
related.
B
Usually
related
repositories
are
also
available
from
the
same
terminal,
and
there
were
tools
like
this
before
there
was
one
like
some
official
get
up
to
before
called
hub,
and
there
are
other
third
party
ones,
but
this
is
the
first
time
that
we
wanted
to
do
something
about
it.
That
really
has
a
get
up
name
behind
it.
B
When
we
discussed
it,
we
sometimes
discuss
these
things
whenever
I'm
in
on
the
github
team
that
decides
to
make
something
open
source
we
are
instead
talking
about.
Why
should
this
not
be
open
source
and
if
we
can't
really
come
up
with
any
strong
reason
like,
for
instance,
oh,
this
would,
you
know,
expose
us
too
much
to
some
security
implications
and
things
like
that
which
obviously
this
tool
doesn't,
but
then
some
others
might
then
for
them.
B
For
the
time
being,
we
don't
do
that,
but
I
think
I
like
to
tend
with
my
mentality
and
and
my
peers
as
well,
that
we
should
try
to
open
source
as
much
as
possible.
So
I
think
it
only
makes
sense,
especially
because
this
is
good,
that
the
tool
is
open
source
because
there's
literally
no
reason
to
be
closed
source.
It's
mostly
an
api
client.
A
And
I
think
that's
like
such
a
good
mentality.
You
have
right
like
I
was
in
a
stream
the
other
day
and
someone
asked
me
something
and
I
was
like
no.
I
said
why
would
you
do
that,
and
I
was
like
why
not
like
you
know
like
she
said:
if
you
can't
think
of
any
clear
reasons
not
to
do
something,
then
you
should
definitely
do
it.
It's
not
always
about
the.
Why
it's
often
about
the!
A
Why
not
now,
if
we
talk
about
the
the
terminal,
it's
open
source
people
can
go
and
contribute
to
it
and
they
can
check
it
out
on
the
repo
here
since
you've
gone,
live
on
the
github
cli
only
a
couple
weeks
ago.
How
much
contribution
have
you
had?
Has
there
been
more
contribution
because
of
oktoberfest
like
tell
us
a
little
bit
about
what's
been
happening
on
the
contribution
side
of
things.
B
Well
so
far,
I
think
we've
had
a
lot
of
a
lot
of
issues
and
requests
coming
in,
especially
after
the
1.0,
because
people
feel
it's
the
perfect
time.
First
of
all,
there's
a
lot
of
eyes
on
it
and
second
of
all,
people
feel
like
it's
a
perfect
time
to
voice
the
thing
that
they
feel
like
they
imagine
should
be
next
feature,
so
we
had
an
onslaught
of
issues
and
but
in
the
pure
quest
side
I
still
haven't
felt
yet
the
effects
of
hectoberfest.
B
I
think
it's
maybe
a
little
bit
early,
but
I
think
that
might
be
due
to
the
fact
that
we
also
had
a
lot
of
like
really
good
quality
contributions
and
contributors
in
the
time
leading
up
to
the
1.0,
because
we
were
also
pretty
active.
We
were
announcing
releases
back
then
in
beta
and
kept
really
open
communication
with
everyone,
and
I
would
say
that
we
wouldn't
be
able
to
make
it
with
the
feature
set
that
we
set
for
ourselves
so
1.0.
B
A
And
one
of
the
questions
we
get
a
lot
on
these
open
source.
Brighter
streams
is:
how
do
you
encourage
contributors
to
come
to
the
project?
How
do
you
build
like
a
culture
and
what
your
contribution
is
like,
so
why
don't
you
tell
me
a
little
bit
about
how
you
attract
contributors
and
then
we
might
walk
through
say
if
I
want
to
contribute
to
ci
what
I
would
do
as
a
first-time
contributor
landing
on
this
repo?
What
would
I
do?
Where
would
I
go.
A
B
So
I
would,
I
would
definitely
say
that,
for
most
of
my
experience
being
an
open
source
maintainer,
which
is
now
about
probably
more
than
10
years-
is
that
I
don't
think
I
was
always
as
good
at
it.
I
think
I
was
often
before
acting
as
sort
of
gatekeeper
and
made
it
really
hard,
sometimes
unintentionally,
of
course,
to
contribute
to
projects,
and
I
feel
that
lately
I've
started
to
realize
some
of
the
things
that
really
don't
work
out
and
and
on
the
other
hand,
some
of
the
things
that
do
work
out
really
well.
B
So
we
had
a
chance
to
try
it
out
with
a
with
a
github
cli,
and
I
feel
that
the
most
important
thing
is
to
make
people
feel
included
and
part
of
something
and
that's
a
really
tricky
line
to
walk,
because,
on
the
other
hand,
as
any
kind
of
core
team
on
any
sort
of
project.
Usually
there's
there's
a
core
team.
There's
a
group
of
decision-making
people
and
those
people
ultimately
have
the
the
decision-making
power
to
drive
the
the
roadmap
of
a
project
and
direction,
or
something
like
that.
B
So
I
feel
that
with
github
cli
we
open
so
much
to
feedback
and
we've
been
asking
constantly,
since
even
before
beta
and
in
during
the
whole
beta
process,
we've
had
the
feedback
form
and,
of
course,
issues
as
ways
to
really
keep
tabs
on
on
what
is
the
pulse
of
the
community
and
what
do
people
want,
and
I
think
that
worked
really
well,
and
I
feel
that
years
ago,
some
of
the
projects
that
I
was
sometimes
wondering.
Oh,
why
does
this
very
popular
project
doesn't
get
as
many
contributions
now
looking
back?
B
B
That
would
mean
just
sticking
more
closely
to
the
tools
that
people
are
mostly
familiar
with,
and
I
feel
as
soon
as
people
can
start
tinkering
the
sooner
the
people
can
start
ignoring
seeing
the
effect
of
what
they
do,
the
easier
it's
going
to
be
for
them
to
then
either
solve
the
bug
they're.
Having
or
add
the
feature
that
really
wanted
to.
A
Yeah
definitely
now
we're
definitely
going
to
come
back
to
some
of
your
experience
in
open
source
and
your
journey
into
open
source
because
you've
got,
as
you
said,
your
10
or
plus
years
weather
experience
and
there's
a
lot
of
people
here
in
the
chat.
They're,
definitely
going
to
want
to
hear
from
that
experience,
but
let's
jump
into
this
first
time
contributing
type
scenario,
because
there's
a
lot
of
people
who
come
in
and
they
look
at
a
project.
I've
been
getting
questions
all
week.
We've
been
doing
lots
of
hacktober,
fair
streams
of
you
know.
A
How
do
you
find
a
project
or
then
once
you've
found
a
project?
How
do
you
work
out
if
that's
a
good
project
to
contribute
to,
especially
as
a
first-time
user?
So
let's
walk
through
it
so
say
I
landed
on
we'll
go
to
here
on
the
code
page
on
the
github
client
and
I'm
thinking
I
want
to
contribute
to
this
project.
A
B
So
it's
always
up
to
date,
and
we
then
link
on
the
bottom
of
this
page
to
the
issues
page
where
people
can
can
look
at
feedback
and
they're
on
the
issues
page.
I
would
definitely
the
first
thing
check
what
is
already
open,
because
there's
a
lot
of
things
or
they
open.
We
have
a
huge
backlog
and
people
also
working
on
some
pull
requests
and
that's
another
thing
that
we're
seeing
is
a
lot
of
people.
Just
don't
first
look
at
what's
already
out
there
and
they
just
kind
of
re-request
similar
things.
B
The
way
I
like
to
familiarize
myself
with
the
project
is,
I
look
not
just
the
open
issues,
but
I
often
look
also
the
closed
issues
based
on
some
topic
that
I'm
interested
in
to
see.
If
that's
been
discussed
in
the
past,
maybe
that's
been
suggested,
but
also
rejected
because
it
doesn't
fit
with
a
philosophy
of
the
project.
So
I
feel
the
one
small
thing
that
everyone
can
do
for
maintainers
is
just
make
sure
that
they're
not
just
adding
to
the
backlog,
but
without
kind
of
do
making
due
diligence
first
and
then.
A
Github
a
little
tip
for
everyone
that
I've
been
telling
on
my
streams
if
you're
on
a
code
base-
and
you
don't
know
what,
where
the
file
is
located
because
I'm
like
I
don't
know
where
the
file's
located
press
t
on
any
repo
code
base
and
it'll,
bring
up
a
search
tool
or
search
every
single
file
that
you
need
to.
So
I
just
typed
contribute
there
and
it
popped
up.
So
here
we
go
so
here's
the
contributing
docs.
This
looks
really
nice
and
easy.
A
There's
one
thing:
we
often
tell
new
time
and
first
time
contributors
is
looking
at
the
contribution
guidelines
and,
looking
and
saying
you
know,
does
it
doesn't
feel
welcoming?
Does
it
feel
easy
to
contribute?
And
what
I
like
is
this
do's
and
don'ts
it?
Really?
It
really
easily
shows
you
like
what
to
do
and
what
not
to
do
so.
How's
the
feedback
being
missed,
live
from
the
contributing
docs
and
for
first-time
contributors
coming
to
the
project.
So
far,.
B
I
would
say-
and
I
feel,
that
the
stumbling
blocks
there
aren't
like
starting
out,
but
maybe
figuring
out
deeper
things,
for
instance,
how
to
like
effectively
run
tests
and
things
like
that,
and
that
is
also
something
that
we
are
also
figuring
out,
how
to
effectively
cover
our
code
base
with
the
test
suite.
So
we
completely
understand
that
somebody
gets
a
little
bit
stuck
on
that
part.
It
doesn't
know
how
the
current
ones
are
wired
up.
B
That
is
something
that
we
we
would
definitely
like
to
explore
ourselves,
and
then
we
label
those
features
appropriately,
so
that
we
would
like
to
avoid
somebody
really
spending
a
lot
of
time
working
on
those
just
to
for
us
to
tell
us.
Oh
sorry,
we
won't
be
even
reviewing
this
poor
request
because
so
and
so
reasons
right.
So
we
have
some
of
the
least
of
those
things
in
the
please
avoid
or
the
don'ts,
because
we've
been
getting
yeah,
we've
had
to
disappoint
a
lot
of
people
by
telling
them.
Oh.
A
Now
I've
got
a
little
bit
of
confusion
in
the
chat,
so
I'm
going
to
clear
out
this
confusion
for
you
right
now,
so
the
github
cli
is
open
source.
So
anyone
who's
thinking
that
it's
not
open
source
github
cli
is
100
open
source.
It
is
free.
You
are
able
to
contribute
to
it
as
well
and
they're,
welcoming
contributors
from
everyone
we're
going
to
talk
about
a
little
bit
about
the
types
of
contributors
that
you'd
like
to
see
to
this
life.
Now
we've
got
some
questions
about
actually
supporting
or
participating
in
hockey.
A
B
A
There
you
go
so
I'm
assuming
you
would
like
to
participate
in
october,
1st
and
yeah.
It
only
happened
a
couple
of
days
ago,
but
I'm
opt-in
only
now
for
hacktoberfest,
so
miss
life
is
going
to
go
check
that
out
for
people.
So
if
anyone
wants
to
check
out
the
projects
that
have
opted
in
for
hacktoefest,
you
can
jump
over
to
the
oktoberfest
website.
A
There's
almost
34
000,
open
source
projects
that
have
opted
in
for
hacktoberfest
feel
free
to
have
a
look
at
those
as
well,
but
github
cli
should
be
on
there
very
soon
right
now
we're
looking
at
the
types
of
contributors
that
you
would
like
to
come
to
the
project.
Now
lots
of
people
look
for.
You
know
a
certain
type
of
contributor
on
their
coder
people,
looking
at
contributing
to
documentation
with
different
projects.
Now
what
are
the
kinds
of
people
or
developers
you're
looking
at
for
contributing
to
the
cli.
B
B
B
I
would.
How
would
they
say?
I
used
to
strongly
feel
that
I
really
like
to
see
the
code
ones
the
most
as
a
maintainer,
because
those
were
the
ones
that
will
help
me
out
the
most
like.
If
somebody
sold
the
bug,
then
I'm
just
saved
hours
by
not
having
to
find
it
myself,
especially
if
it's
obscure
and
another
system
that
I
don't
use
every
day
like
windows
and
but
now
I
believe
that
there's
sort
of
like
a
long
tail
effect
to
that
as
well.
B
That,
even
though
there's
some
contributions
that
are
really
heavy
on
code
first
and
foremost,
and
they
look
really
big
and
they
seem
like
they've
saved
us
a
lot
of
hours
or
something.
But
if
behind
that,
one
there's
also
a
100,
really
small
ones,
ranging
from
a
type
of
fix
to
just
a
small
documentation,
change
those
really
help
as
well,
and
I
feel
that
contributors
contributors,
especially
those
who
contribute
documentation.
B
They
have
a
really
good
outside
perspective
because
they
just
went
probably
half
an
hour
ago
through
the
process
of
setting
up
the
project
or
if
something
didn't
work
for
them,
or
anything
like
that.
When
people
contribute
installation,
docs
or
tips
how
to
set
things
up
on
another
system
that
we
haven't
covered
really
well,
that's
amazing
as
well,
not
because
that
helps
us
as
much
because
we
probably
not
going
to
set
it
up
on
the
same
system
but
yeah.
B
Yeah-
and
I
feel
that
in
that
way,
people
are
looking
out
for
each
other,
so
contributors
are
looking
out,
sometimes
for
other
contributors
that
way
and
the
project
that's
more
larger
in
size.
The
github
cli
is
also
going
to
have
different
types
of
contributors
as
well,
which
is
outside
of
code
or
documentation
which
is
something's
design
and
things
like
that.
A
And
I
think
that's
what's
happening
across
the
open
source
community
as
well
we're
seeing
especially
like
with
things
like
oktoberfest
and
new
projects
that
are
coming
up,
they're
saying
they
want
contributors
from
like
a
bunch
of
different
walks
of
life.
I
know
one
of
the
teams
that
we
interviewed
on
this
a
couple
weeks
ago
have
have
their
hack
trouble
festival
and
they
have
columns
so
contributors.
A
B
Well
back
when
back
before,
there
was
github,
which
is
this
murky
era
of
my
memory-
that
I
can't
really
remember.
But
I
remember
like
it
was
very
long
ago.
We
just
used
svn
to
to
obtain
code,
and
still
there
was
this
era
of
sending
patches
to
mailing
lists,
which
was
you
know
for
me,
a
distant
memory
and
it's
still
a
reality
for
some
communities
like
the
linux
kernel.
B
I
would
guess-
and
things
like
that,
but
I
I
do
remember
that
back
then
I
was
a
contributor
to
early
on
rails,
but
before
that's
a
php
framework
of
sorts,
I
would
say
zen
framework
and
that
was
still
before.
I
was
really
big
on
on
php
and
later
I
transitioned
into
ruby,
because
I
just
I
was
following
more
kind
of
exciting
and
scripting
language
that
will
allow
me
to
do
meta
programming
and
create
dsl
dsls,
and
things
like
that.
B
I
just
I
think
that
was
probably
my
first
project
that
I
migrated
over
from
svn
to
git
and
had
to
teach
myself
git
in
the
process,
because
I
wanted
to
be
a
part
of
this
thing
called
github,
but
I
didn't
know
good
at
all
and
started
learning
it
from
the
command
line
back.
Then
there
was
probably
not
so
much
of
the
nicer
interfaces
like
it
of
desktop
and,
and
some
other
guise
form
for
git.
B
So
the
literally
the
only
way
you
could
learn
it
and
use
it
first
from
terminal,
and
then
I
was
as
I
was
learning
it.
I
would
be
writing
my
own
scripts
and
little
workarounds
and
eventually
start
writing.
The
first
get
up
cli
or
start
contributing
the
first
git
of
cli.
That
was
that's
called
hub
and
still
exists,
but.
A
B
And
then,
of
course,
I
had
my
ideas
to
add
and
the
project
wasn't
really
strictly
maintained
in
the
sense
that
it
didn't
have
any
kind
of
direction
or
vision
what
it
was
to
be
so
it
was
kind
of
like.
Oh,
you
had
this
weird
command
and
you
had
this
one,
but
the
creator's
involvement
with
it.
It's
kind
of
like
fell
off
after
a
while,
like
it
often
does
and
there's
no
it's
it's
just.
B
I
feel
like
it's
a
natural
cycle
of
a
lot
of
business
project
if
nobody
picks
them
up,
but
in
case
this
case,
I
really
picked
it
up,
because
I
was
really
enthusiastic
about
it
and
kept
adding
and
adding
and
adding
to
it
and
was
maintaining
it
actively
for
10
years,
during
which
time
github
was
really
grew
and
growing
features.
And
when
those
features
received
apis,
we
would
add
them
as
support
to
to
hub
and
therefore
get
up
all
this
time,
since
almost
since
inception
did
have
a
cli.
B
A
lot
of
breaking
changes
to
put
it
at
some
point
in
which
we
could
call
it.
Okay,
it's
now
some
official
get
a
product
that
we
call
1.0
or
something
like
that,
and
because
I
didn't
think
that
that
was
a
really
healthy
thing
to
do
to
people
who
are
currently
using
hub
to
start
like
reshaping
it
in
a
way
that
would
break
in
a
lot
of
ways
for
existing
users.
It
was
a
much
better
idea,
just
to
start
a
fresh
code
base.
It
was
not
an
easy
decision.
It
was
a
very
hard
decision.
A
A
A
Time
and
for
a
project
you
mentioned
that
like
when
you
started
working
on
the
hub,
all
the
other
maintenance
left
and
you
picked
it
up.
So
obviously
that
is
a
breaking
point.
If
you
will
of
open
sources,
you
know
all
the
maintainers
going
to
stay
so
with
the
github
cli.
How
many
maintainers
are
there
like
core
maintainers
either
to
the
project?
B
A
Just
makes
things
a
lot
easier
right,
just
yeah
yeah
you
can
bounce
ideas
off
people,
you
know.
Obviously
you
get
more
work
done,
but
just
having
that
your
team
driving
the
project,
I
think,
is
really
key.
Now
I've
got
a
couple
of
questions
coming
from
the
chat,
so
keep
the
questions
coming.
We're
going
to
ask
this
song
feel
free
to
shaft
it
back
to
me
if
you
want
to,
but
is
the
github
client
going
to
be
an
npm
package
like
git
and
others
talk
about
github
for
cli
and
npm.
There.
B
Yeah,
I
I
wouldn't
say
necessarily
no
completely,
because
I
was
actually
surprised
at
what
sort
of
things
were
packaged
in
npm
successfully
and
then
distributed
like
that.
I
used
to
think
that
it's
only
for
javascript
libraries
and
then
later
it
dawned
on
me
that
the
javascript
community
is
actually
using
it
a
lot
as
also
a
distribution
tool.
B
B
We
feel
that
the
current
ways
and
installation
of
the
binaries
are
are
pretty
much
available
to
anyone
on
any
system
and
that
we
don't
feel
strongly
about
necessarily
making
available
trim
pm,
especially
then,
because
that's
a
commitment
that
we
have
to
keep
up
and
we
can't
just
try
it
out
for
a
month
and
see
how
we
feel
about
it.
And
then,
when
people
have
bad
experience
with
it,
we
can
just
kind
of
backtrack
out
of
it
and
stop
publishing
updates.
B
Yeah
we
need
to
go
all
in
so
we
should
first
see
how
we
feel
about
that.
But
I
think
people
haven't
there's
only
been
maybe
two
requests
so
far
that
are
hinting
at
that
and
I
feel
that
everybody
else
was
finding.
It
really
easy
to
install
using
their
package
manager
of
choice
on
a
system,
and
I
now
I
ignored
npm
as
a
package
manager
of
a
choice
but
like
a
more
os
based
one
like
apt-get,
on
ubuntu
or
debian
or
homebrew
on
mac
os,
which
is
not
official.
B
A
Definitely
now
we've
got
obviously
it
only
got
released.
Not
that
long
ago
we've
already
got
github
one
cli
1.1
out
already,
so
what
other
kind
of
things
are
you
looking
at
for
the
future
of
cli,
now,
obviously
you're
taking
a
lot
of
feedback
from
the
community?
What
sort
of
some
of
the
big
picture
goals
or
some
of
the
the
plans,
the
cli
in
the
future.
B
Well,
I
feel
that
that
we
wanna
we
wanna,
definitely
figure
out
what
are
the
sort
of
workflows
that
people
do
through
the
terminal
still
and
how
we
can
expose
some
things
that
otherwise
people
have
to
jump
in
between
the
browser
and
the
terminal
for
and
not
all
of
them
are
equally
good
ideas
for
cli.
For
instance,
some
people
have
suggested
projects
and
project
boards
and
cards
to
be
exposed
somehow
through
cli,
and
we
consider
that
briefly.
B
But
then
we
try
to
imagine
this
like
highly
visual
tool,
which
is
split
into
these
columns
or
something,
even
though
you
can
technically
force
that
output
through
a
terminal
using
ascii
tables
or
something
like
that.
It's
not
really
experience
that
we
want
for
users,
so
instead
we're
not
gonna
explore
so
much
too
much
in
that
direction,
which
we
still
believe
that
the
graphical
interface,
like
literally
projects
boards
on
the
web,
would
be
much
more
effective
to
manage
that.
B
But
I
I'm
more
looking
towards
things
that,
first
of
all,
my
primary
way
of
thinking
about
projects
like
this,
so
that
get
up
cli
would
be
how
much
we
can
expose
raw
data
to
users
for
them
to
write
their
own
scripts,
and
that
is
always
going
to
be
a
sub
feature.
That
is
built
a
little
bit
underneath
the
surface
of
the
cli,
and
that
is
that
it's
really
handy
to
use
for
scripting.
B
So
I
do
want
to
continue
investing
into
like.
Oh,
what
sort
of
data
could
we
liberate
through
the
github
cli
to
people
who
want
to
write
scripts,
but
they
necessarily
don't
want
to
write
scripts,
that
directly
interface
with
a
github
api,
because
there's
then
a
lot
of
json
parsing
and
notification,
and
things
like
that
they
want
to
handle,
and
with
this
they
have
a
tool
already
that
went
through.
All
of
that
that
can
do
the
parsing
to
them.
B
They
mostly
do
that
from
their
terminal
right
and
if
there's
a
tool
already
to
kind
of
capture
that
whole
process
streamline
it
for
them
and
connect
it
to
their
account
immediately
with
them
without
them.
Having
to
like
well
copy
this
code
now
and
now
open
the
browser
and
log
in
and
paste
it
there
over
your
account.
So
if
we
can
help
people
not
having
to
already
make
a
complicated
process
more
complicated,
then
we'll
totally
gonna
jump
at
the
opportunity.
A
100
we've
got
some
people
in
the
chat
we've
got
lost.
Algorithm
has
said
thanks
for
your
work
on
cli
has
changed
so
many
workflows
for
the
better
over
this
side.
So
thanks
for
that
lost
algorithm,
we
love
people
showing
their
appreciation
so
you're,
talking
literally
to
the
man,
who's
been
heading
up
the
whole
project
and
we've
got
some
questions
as
well
around.
What's
the
uptake
of
like
cli,
like
obviously,
we've
got
lots
of.
A
Oh
look
again:
we've
got
280
open
issues,
there's
not
to
say
anything
about
the
800
plus
issues
that
are
already
closed
and
we've
got
lots
of
poor
requires.
But
what's
the
uptake
of
the
actual
cli
like
like?
Have
we
seen
lots
of
people
download
it
enjoy
it?
What's
the
kind
of
feedback
been
like
so
far.
B
I
think
the
feedback
has
been
lots
of
people
have
definitely
tried
it,
because
we
the
only
way
we
can
see
the
people's
activity
because
we
cli
doesn't
have
any
kind
of
tracking
in
it.
The
only
way
that
we
can
see
activity
is
by
just
looking
at
the
traffic
generates
to
the
github
api,
which
is
the
only
way
we
have
of
it
right
now,
and
even
though
we
had
a
really
active
beta
period,
we've
seen
four
or
five
times
as
much
activity
just
a
few
days
after
the
announcement.
B
So
lots
of
people
are
trying
it
out
and
do
we
wanna.
We
want
to
position
it
as
a
sort
of
like
an
indispensable
just
part
of
of
a
tool
set
when
somebody's
working
with
github
and,
of
course
this
is
just
for
people
who
are
using
their
terminals.
So
I
understand
there's
a
lot
of
github
users.
They're
not
like
me:
they
don't
live
their
whole
days
in
the
terminal.
Yeah.
A
I
definitely
don't
live
my
whole
day
in
the
terminal.
I've
started
using
the
terminal,
a
lot
more
since
github
cli
got
released
and
I
started
playing
around
with
it
a
little
bit
more,
I'm
like
well.
This
is
actually
really
fun,
but
yeah
I've
been
really
enjoying
it.
So
yeah
it's
been
like
this
is
really
cool.
I
can
write
something
and
then
something
happens
over
there
and
then
you
go
into
the
website
and
or
like
the
browser.
You
see
it
change
it
for
me,
like
I'm,
I'm
not
a
developer
by
background.
A
And
I
think
I'm
going
to
ask
you
a
question
so
for
me,
I've
been
really
loving
the
clone
repo,
because
I
work
a
lot
with
like
projects
and
I'm
doing
like
learning
the
code
and
so
for
me
being
able
to
like
clone
a
reaper
and
put
on
my
local
desktop
and
then
throw
it
into
github
desktop
and
then
like
do
all
the
changes
it
needs
and
then
like
see
the
outfit.
I
think
that
for
me,
is
like
probably
my
favorite
thing,
as
well
as
like
being
able
to
open
an
issue.
A
B
It's
still,
it
is
a
little
bit
manual
still
because
you
do
need
to
somehow
process
the
result
of
that,
but
it
it
makes
a
lot
of
api
tasks
a
little
bit
easier,
just
a
tad
easier
for
everyone,
and
I
would
like
to
also
continue
in
that
fashion
and
make
it
even
more
accessible
to
the
point
that
even
no
json
parsing
utilities
are
needed
on
the
other
end
and
things
like
that,
and
so
one
single
command.
That
would
definitely
be
my
favorite.
B
B
And
we
try
to
make
it
nicer
without
going
over
over
the
top,
but
we
try
to
support
anything
that
the
github
already
supports
and-
and
I
feel
that
for
those
commands
that's
what's
happening
under
the
hood-
is
if
their
output
is
redirected
to
script.
Instead
of
straight
to
your
terminal,
which
is
formatted
really
nicely,
then
we
don't
do
the
colors.
B
We
don't
do
the
nice
formatting,
but
we
kind
of
output
these
raw
data
streams,
so
people
can
choose
how
they
want
to
see
the
data
they
can
either
intake
in
their
terminal
visually
or
they
can
pipe
into
a
script
where
they
kind
of
further
filter
it
and
process
it.
So
my
favorite
feature
would
be
the
fact
that
it's
so
adaptable
that
it's
versatile
to
different
styles
of
views,
yeah.
A
I
think
it's
really
cool
and
I
obviously
did
the
the
github
command
line.
Little
two-minute
social
video
that
went
out
and
there's
a
few
of
the
things
that
I
was
doing,
I'm
like
wow.
This
is
this
would
be
a
really
really
cool
feature.
That's
going
to
just
blow
people's
minds.
We've
got
a
question
in
the
chat
from
techy
man,
which
says
he's
asking
like
what
feature
of
the
github
client
do.
You
think
actually
has
the
most
value.
B
Well,
it's
hard
to
just
select
one
feature,
but
definitely
what
is
proven
to
be
the
most
popular
feature
set
and
that's
not
a
single
command.
I
would
say
the
set
of
commands
around
pull
requests,
they're
kind
of
closely
related
you
they
flow
from
one
to
another,
so,
for
instance,
checking
out
the
pull
request
and
then
doing
some
other
tasks
while
you've
have
the
checked
output
requests
like,
for
instance,
merging
it
from
the
github,
cli
or
or
or
basically
we
have
a
bunch.
A
B
I
feel
that
makes
almost
the
most
sense
for
people
who
need
this
sort
of
access
who
would
otherwise
have
to
jump
to
between
github.com
and
their
terminal.
So
I
feel
that's
in
and
that's
not
only
my
feeling.
I
think
that
from
the
stats
that
we
got
it,
it
looks
like
the
pull
request
set
of
related
commands,
including
poor
request.
Creating
as
well
from
the
command
line,
is
by
far
the
most
used
set
of
commands
and.
A
We've
got
a
copy
of
the
chat
saying
we
like
creating
issues,
so
that
was
one
of
the
things
that
I
tried
out
and
that's
what
you
see
in
the
emojis.
So
if
you've
got
an
issue
template
the
mojit
comes
up
and
it's
really
cool
now
we
haven't
got
that
long
left
and
I
did
want
to
jump
back
a
little
bit
so
again
to
your
experience,
because
you've
got
so
much
experience
in
this
space.
You
talked
a
little
bit
about
how
you
got
involved
in
open
source.
A
You
kind
of
like
just
fell
into
it
after
finding
something
that
you
really
were
passionate
about
all
the
other
maintainers
left
and
then
you're
like
cool.
I
like
this
project,
so
I'm
gonna
take
it
over,
but
for
those
people
out
there,
we've
got
people
in
the
chat.
We're
going
to
people
have
been
listening
to
this
afterwards.
What
are
kind
of
your
top
tips
to
those
people
out
there
who
may
be
thinking
about
contributing
or
getting
into
open
source?
B
Oh,
could
I
be
a
part
of
making
this
better
for
not
just
thinking?
This
is
something
that
other
people
have.
This
is
something
that
other
people
have
created
and
I
am
just
kind
of
a
consumer
all
of
these
things,
but
to
remind
yourself,
like
quite
ordinary
people
in
their
living
rooms,
in
their
bedrooms
and
in
their
weekends,
have
created
these
things
in
their
free
time,
without
much
often
without
so
much
forethought
or
or
even
research.
B
So
I
think
the
primary
thing
that
I
would
suggest
to
anyone
to
who's
considering
contributing
is
to
not
to
try
to
dispel
completely
the
impostor
syndrome,
because
I
I
notice
something's
too
strong.
I
have
it
definitely
myself
that
we
can't
just
wish
it
away,
but
at
least
try
to
resist
it
like
put
up
a
little
bit
of
a
fight
by
reminding
yourself
rationally
kind
of
these
are
people
just
like
me,
and
I
feel
that
I
also
have
some
input
to
to
do
and
to
technically
find
that
project.
B
That's
the
next
step
after
the
courage
step
of
the
summoning
the
courage
step,
I
would
say
the
next
step
would
be
selecting
the
project
and
the
task
to
do
on
it.
And
for
me
it
was
always
the
easiest
to
select
something
that
I
was
actively
using.
As
I
said
already
or
considering,
using
or
or
had
even
trouble
figuring
out
how
to
start
it
up,
sometimes
my
contributions
came
from
the
fact
that
I
tried
to
use
something
and
it
didn't
work
at
all
and,
like.
B
B
B
That's
a
part
of
asking-
and
I
feel
a
part
of
contributing
is
also
like
accepting
that
it
might
be
no
back
and
that
it's
nothing
personal,
but
it's
mostly
just
an
opportunity
to
you
to
kind
of
then
reshape
how
you
think
about
this
project.
So
maybe
the
feature
was
too
large.
What,
if
we
break
it
down
and
to
bare
minimum
that
could
still
help
you
but
would
be
maybe
acceptable
by
maintainers,
and
then
I
think,
with
my
initial
contributions.
B
After
a
while,
I
learned
that
I
need
to
think
more
like
how
maintainers
felt
about
their
project
and
align
more
with
with
their
idea,
and
then
I
would
make
my
contributions
more
viable
and
therefore
more
more
easier
for
them
to
review
and
eventually
to
merge.
So
there
was
a
lot
of
mistakes
made
initially,
but
I
feel
that
nobody
should
try
to
really
skip
past
them,
like
there's,
really
no
shortcuts
that
we
should
go
through
them
and
we
should
just
all
have
patience
for
each
other
and
support.
A
Yeah,
that's
a
lot
of
really
really
good
tips.
Second
tutorials.
We
do
have
a
lot
of
people
who
are
dropping
into
these
open
source
streams
if
you
are
maintainers
or
who
are
starting
a
project.
So
what
kind
of
top
tips
do
you
have
for
those,
especially
as
someone
who's
been
maintaining
projects
for
10
years?
You
said:
you've
learned
a
lot.
So
what
are
your
some
of
your
top
tips
and
maintainers.
B
For
maintenance
of
the
project
I
would
say
to,
I
would
say
that
very
important
is
to
make
the
project
feel
welcoming
and
not
to
count
on
the
fact
that
people
will
push
through
if
they
have
enough
energy
to
fight
through
your
barriers
as
a
maintainer,
because
only
then
a
certain
kinds
of
people
will
actually
push
through
the
defenses
and
then
the
the
types
of
people
involved
in
the
project
would
be
like
very
uniform.
And
I
I
value
diversity
a
lot.
B
So
I
feel
that
a
project
on
its
face,
which
is
often
most
the
primary
phase
of
a
project
on
github,
is
maybe
it's
readme
and
its
official
site,
and
this
description
and
tags,
and
things
like
that.
So
often
it's
worth
to
step
back
and
see
how
the
the
first
surface
of
the
project
might
be
perceived
from
outsiders
and
how
we
can
signal
the
fact
that
maybe
the
project
is
more
than
just
what
meets
the
eye,
or
maybe
the
project
needs
more
help
than
what
it
appears
and
from
different
kinds
of
people.
B
I
would
say
that
the
most
important
thing
would
be
to
just
really
focus
on
solving
your
initial
idea
well
and
then
to
find
ways
to
get
people
on
board
with
the
idea
and
that
that
part
is
like
the
organic
growth
of
the
project.
That
part
is
the
hardest,
because
I
feel
that
a
lot
of
people
are
thinking.
B
B
A
That's
where
it's
like
any
startup
right,
like
you
can't
just
you
know,
build
the
thing
and
then
hope
people
come
you've
got
to
solve
the
problem.
You've
got
to
market
it
in
the
right
way.
You've
got
to
attract
the
right
people
to
come
to
the
project
and
just
start
using
it
right
and,
like
you
said
it's
a
a
lot,
is
around
trust.
You
know
whether
it's
if
you're
building
a
product
people,
you
know
download
or
people,
take
that
product
and
trust
that
it's
gonna
work.
A
If
it's
open
source
software,
as
you
said,
people
download
that
product,
they
don't
just
trust
that
it's
going
to
work
with
it
they're
trusting
that
you're
not
going
to
you
know,
break
anything
else
that
they've
got
going
on
as
well
right.
So
I
think
you
know
those
are
such
important
things,
and
you
know
this
is
many
of
those
people
listening
into
the
chat.
This
is
like
the
goal
that
you
need
to
be
listening
to
right
now.
This,
like
these
tips,
are
just
like
what
you
want.
B
What
do
you
also
have
to
contribute
with?
Where
does
their
energy
come
from,
and
and
what
motivates
you
and
I
feel
that
the
rest
is
gonna
fall
like
domino's
after
that
initial
figuring
out
that
initial
thing,
the
initial
motivation
and
the
single
most
important
skill
in
in
what
people
like
me
are
doing.
I
would
say
that
it's
just
persistence,
and
sometimes
it
is
hard,
but
sometimes
we're
faced
with
the
stack
trace
and
we're
looking
at
it,
there's
no
rhyme
or
reason
to
it.
B
But
I
would
say
that
persistence
is
the
most
important
skill
and
that
is
also
in
contributing,
and
that
is
also
in
maintaining
and
it
needs
a
lot
of
energy
and
sometimes
it's
hard.
But
I
would
definitely
encourage
everyone
to
keep
up
with
it
because
what's
on
the
other
side
is
a
lot
of
connection
and
a
lot
of
creation
and
we
didn't
get
to
enjoy
the
the
tools
that
we
use
and
use
them
for
great
things.
A
Definitely,
I
think
you
you
started
touch
show
before
too,
but
people
just
need
to
understand
that
whatever
kind
of
skill
level
they
have
and
whatever
kind
of
programming
language
or
anything
like
that,
that
you've
got
you,
your
skills
will
be
valuable
to
open
source.
So
don't
ever
think
that
you're
not
good
enough
or
that
you
know
you
can't
learn
as
well
or
you
can't
learn
from
the
people
around
you.
You
know
a
lot
of
the
streams
have
been
talked
about.
A
A
It's
just
everyone
coming
in
and
helping
one
another
out,
and
you
know
supporting
one
another,
and
so
I
think
you
know
what
the
key
things
you
said
were
amazing,
which
was
you
know
if
you
are
a
maintainer,
you
know
think
about
how
to
make
your
project
welcoming
get
people
involved.
You
know
build
a
culture
that
is
diverse
rather
than
just
one-sided.
A
You
know,
if
you're
thinking
about
contributing
you
know,
block
up
the
courage
to
contribute
and
then
find
a
project
to
contribute
to
you
know.
Hopefully
it's
something
that
you're
already
using
and
then
once
you've
you've
got.
Then
you
start
contributing
to
that
project.
Don't
get
disheartened
if
your
full
request
doesn't
get
merged.
So
I
think
all
those
tips
and
tricks
that
you
just
told
us
are
just
so
amazing
got
people
in
the
chat
saying.
Thank
you
so
much
for
that.
A
Alrighty
all
thanks
to
everyone
for
being
here
today,
I
absolutely
loved
having
you
all
here.
It
was
really
really
exciting
to
chat
to
you
all
about
the
the
cli
about
open
source,
how
to
get
involved
as
maintainers
a
contributor
and
just
talk
to
some
of
the
people
like
mislove,
who
have
been
in
the
community
for
10
years
as
maintained.
That
is
insane
that's
longer
than
half
the
people
here
in
the
chat
have
been
developers.
A
So
if
you
want
to
get
involved-
and
you
want
to
learn
more
and
be
part
of
a
community,
there's
amazing
talent
within
the
developer
community,
especially
within
the
open
source
community,
so
definitely
check
it
out.
As
I
mentioned,
go
check
out
the
github
cli
you
can
download
it
use
it
do
everything
you
want
with
it
today.
You
can
contribute
to
it
again,
keep
an
eye
on
that
repo
that
public
repo-
so
don't
forget
it
is
open
source,
but
keep
an
eye
on
that
public
repo
miss
live
on.
A
The
team
will
check
out
to
make
sure
that
they're
gonna
opt
in
for
hacktoberfest
that
you
can
contribute
as
part
of
hacktoberfest.
Now,
if
you've
been
enjoying.
These
live
streams,
don't
forget
to
sign
up
to
our
meetup
group,
our
github
virtual
meetups
we've
been
putting
all
the
live
streams
over
on
the
github
meetup
group,
so
we've
been
putting
up
all
our
ones
for
the
apac
time
zone
for
those
americans
have
tuned
in.
A
We
have
a
more
american
friendly
time
zone,
one
for
you
to
all
tune
into,
and
we've
been
running,
meetups
and
online
events
for
various
different
regions.
So
we've
been
doing
india,
africa,
spain,
a
whole
bunch
of
other
places,
so
make
sure
you
sign
up
to
that
group
to
find
out
all
the
cool
things
that
are
happening
in
github
and
again
thanks
all
for
being
here
today
really
exciting
to
have
you
all
here.