►
Description
Let’s face it, the future of software is where you can accomplish your tasks wherever you want and however you prefer to work. Accordingly, GitHub has expanded its toolset to provide you new experiences this year via GitHub Mobile and GitHub CLI Beta and improved experiences via GitHub Desktop. These three products represent the extended GitHub experience to provide you the right tools to be productive with your work at your fingertips. You deserve nothing less.
In this talk, we’ll take a deeper dive into typical Git and GitHub workflows like pushing your code and opening a pull request, reviewing code, and switching contexts and how you can increase your productivity by leveraging GitHub Mobile, CLI Beta, and Desktop.
GitHub Satellite: A community connected by code
On May 6th, we threw a free virtual event featuring developers working together on the world’s software, announcements from the GitHub team, and inspiring performances by artists who code.
More information: https://githubsatellite.com
Schedule: https://githubsatellite.com/schedule/
A
Intro
to
let's
see
all
right,
it's
putting
github
at
your
fingertips
very
excited
about
this
session.
This
session
is
going
to
be
brought
to
you
by
neha
she's,
a
senior
engineering
manager.
I
get
she's
passionate
about
making
tech
industry
easier
and
more
inclusive
I'll.
Let
you
take
it
from
here.
Neja.
B
Thank
you
as
introduced,
I'm
neha
and
I'm
part
of
the
team
that
builds
github's
client
applications,
which
is
how
I
refer
to
the
group
of
products
that
is
mobile,
cli
and
desktop.
So
we've
shipped
a
lot
of
stuff
in
the
past
year
to
bridge
gaps
that
you've
been
facing
as
our
users
and
that's
actually
how
github
mobile
and
github
cli
came
about
this
year.
B
Our
angle
is
pretty
simple:
it's
about
meeting
you
where
you
are
and
helping
you
create
a
workflow
that
feels
like
home
for
you
and
that's
more
important
now
than
ever.
Gibbs
tool
should
be
serving
you
and
help
be
flexible
in
supporting
you
and
how
you
adjust
to
doing
your
work,
whether
that's
on
your
computer
or
on
your
phone.
So
I'm
here
to
share
some
ways.
You
can
do
that,
depending
on
your
needs
and
preferences.
B
The
bulk
of
this
session
will
cover
these
existing
git
and
github,
workflows
and
I'll
layer
in
how
you
might
augment
those
workflows
using
client
applications.
But
I've
left
a
little
bit
of
time
at
the
end
of
the
talk
to
talk
about
key
features.
Give
you
a
sneak
peek
about.
What's
coming
up
and
to
share
my
one
pager
on
how
to
try
these
tools
and
give
us
feedback
all
right?
So,
let's
get
started.
B
I
can't
see
you
so
I'm
just
going
to
assume
you're
as
excited
as
I
am
about
this,
because
it's
time
to
reflect
all
right
so
you're
at
home.
Maybe
you
put
on
some
real
pants
today,
probably
not,
though,
and
you
get
to
your
computer,
because
it's
time
to
write
some
code,
that's
a
simple
task
right
wrong.
B
B
There's
nothing
like
reliving.
How
complicated
we've
made
this
world
than
by
explaining
it
to
someone
who's,
not
in
tech.
It's
a
lot
of
steps
and
it
can
feel
unnecessary
at
times.
We've
all
been
there
part
of
our
job
as
technologists
is
to
figure
out
how
we
can
simplify
these
tasks.
So,
let's
base
break
the
base
case
down
so
first
we
have
our
get
workflows,
which
you
mostly
perform
on
your
local
computer.
B
This
represents
the
majority
of
our
branch
and
commit
flows,
but
there
are
a
few
times
even
after
you
open
a
pull
request
where
you
might
need
to
work
locally
like
when
you're
making
changes,
testing
a
pull,
request
or
tagging
a
release,
then
we
have
the
github
workflows,
which
are
usually
concentrated
around.
Managing
your
tasks.
Code,
reviewing
merging
and
releasing
this
doesn't
include
other
apps.
You
might
use
like
a
project
or
task
manager,
your
editor
or
any
other
scripts.
You
have
to
run
so.
We
saw
the
base
case.
B
Let's
talk
about
github
desktop
if
you're
a
github
desktop
user
chances.
Are
you
don't
mind
using
a
gui,
especially
for
your
local
tasks,
that
git
would
otherwise
cover?
In
fact,
you
might
prefer
it.
That's
why
github
desktops
workflows
cover
almost
all
of
git
workflows,
shown
here
with
a
little
smidgen
of
github
tasks.
To
save
you,
another
back
and
forth
cycle,
but
in
general
desktop,
doesn't
cover
a
lot
of
github
flows
because
github's
also
an
amazing
gui
and
so
its
responsibilities.
B
More
to
get
to
you
to
where
you
need
to
go
faster
than
it
is
to
duplicate
all
of
the
workflows.
Now,
on
the
other
hand,
github
cli
is
for
people
that
prefer
to
use
their
terminals,
so
instead,
github
cli
brings
the
workflows
that
you
do
on
github
to
your
terminal,
so
you
can
execute
them
alongside
git.
That's
why
you'll
see
a
lot
of
overlap
with
github
workflows,
but
not
get
workflo
flows
unless
there
is
a
github
component
associated
with
it.
B
And
finally,
github
mobile
is
for
those
github
on-the-go
tasks
that
you
might
do
intermittently
or
you
could
do
in
under
five
minutes,
because
because
it's
unlikely
that
you're
currently
coding
on
your
phone,
it
helps
you
concentrate
on
helping.
You
manage
your
tasks,
review
code
and
merge
it.
So
in
a
nutshell,
those
are
the
five
tools
that
you
have
to
customize
right,
get
github.com,
desktop,
cli
and
mobile.
B
Real,
quick
before
we
get
started.
We've
I've
laid
out
my
slides
in
a
certain
way
to
help
you
keep
track
of.
What's
going
on
because
there's
a
lot
that
goes
into
your
workflow
right.
So
here's
a
few
things
to
look
out
for
in
these
slides.
So,
on
the
left
hand,
side
I'll,
keep
track
of
your
task,
and
so
it
aligns
with
the
workflow
diagram
that
I
introduced
and,
on
the
right
hand,
side.
B
I
have
the
tool
that
I'm
talking
about
and
that's
color
coded
too
so
we'll
be
bouncing
between
these
different
tools,
because
that's
the
point
of
the
talk
just
keep
an
eye
out
all
right.
First
things:
first,
at
the
beginning
or
end
of
the
day
or
at
an
end
of
a
task
you're
going
to
want
to
check
in
the
mission
control
and
hear
what
you've
been
missing
out
on
since
you've
been
gone.
So
usually
you
might
go
to
github
notification
pages
which
helps
you
see
what's
happening
across
multiple
repositories.
B
According
to
the
filters
that
you
choose.
Additionally,
you
might
create
an
issue
and
eventually
you
select
a
task
to
assign
yourself
that's
the
basic
landscape
of
task
management
and
selection,
which
happens
on.com,
but
if
you're
not
already
browsing
on.com,
there
are
a
few
things
you
can
do
with
github's
client
applications
that
help
you
manage
your
tasks.
B
Github
desktop
provides
the
options
to
one
create,
an
issue
which
you
can
do
from
the
menu
item.
I
didn't
include
that
in
the
screenshot
and
then
two
check
out
a
list
of
pull
requests
that
you
can
open.
Your
repository
and
it'll
give
you
a
little
bit
of
a
signal
on
status
to
help
you
understand.
What's
changed.
B
B
If
you
want
to
manage
some
of
your
tasks
by
the
terminal
with
github
cli,
there's
tons
of
commands,
you
can
use
my
favorite
one
is
sheet
here.
So
that's
ghpr
status
because
it
gives
me
just
enough
information
to
figure
out
what
my
next
move
is.
Do
I
respond
to
an
outstanding
pr,
or
do
I
review
someone
else's
by
the
way
this
works
for
issues
too?
So
you
can
try
out
gh
issue
status
and
then
you
can
use
the
view
command
to
view
more
context.
B
B
When
I
want
to
see
if
anything's
blocking
on
me,
so
I
can
justify
sleeping
another
hour,
which
is
a
hot
tip
for
me.
I
am
not
liable
for
the
consequences,
though,
if
you
try
it
so
you
can
also
create
issues
within
mobile
and
assign
yourself
to
the
tasks
so
that
by
the
time
you
get
back
to
your
computer,
you
can
just
get
started.
B
Now
that
you
know
what
you
want
to
work
on,
you
have
to
prepare
your
environment
by
getting
the
right
into
the
right,
repository
and
branching.
At
some
point
you
have
to
create
your
repository
or
clone
your
repositories
or
fork
the
repository,
and
then
you
have
to
get
that
url
and
you
have
to
clone
it
locally
right.
So
then,
after
that,
you
have
it's
time
to
create
your
branches
which
you
can
do
on
github.com.
So
I
kind
of
showed
this
here,
but
usually
the
majority
of
that
work
happens
locally.
B
Once
you
get
to
your
local
machine,
if
you
don't
have
the
repository
yet
you'll,
do
this
one-time
task
of
pasting,
the
url
to
clone
the
repo
and
then
create
the
branch
you
want
to
work
on
and
also
by
the
way,
if
you're
on
a
fork.
You
also
have
to
set
your
own
upstream
and
you
can't
even
get
the
updates
easily.
So
it's
kind
of
a
mess,
yes
using
github
and
git
to
clone
a
repository
feels
inefficient
to
me.
B
Let's
look
at
how
we
can
make
this
easier,
github
desktop
lets
you
easily
switch
between
repositories
and
it
even
detects,
if
you're,
on
a
protected
branch.
If
you
have
that
feature
enabled
so
that
you
have
a
seamless
way
to
create
a
branch
and
start
your
work
in
the
larger
scheme
of
things
desktop
lets
you
clone
repositories,
create
them
and
even
handles
your
workflow
by
setting
your
upstream
for
you,
this
is
my
go-to
for
getting
repositories,
because
I
can
see
what
I've
added
in
the
repository
menu.
B
I
love
that
github
cli
also
lets
you
create
clone
and
fork
for
forking.
It
even
offers
to
add
a
remote
which
you
can
see
here
and
it's
a
subtle
touch,
but
one
of
my
favorite
things
is
how
github
cli
responds
to
your
commands,
even
even
when
things
are
going
well.
So
I
love,
I
just
get
these
check
marks,
so
it
says
when
the
fork's
been
created
when
my
origin's
been
renamed,
it
feels
like
I'm
the
boss
and
my
computer
is
giving
me
good
news.
B
You
know
both
desktop
and
cli,
handle
your
repositories
without
switching
contacts,
copying
information
and
don't
make
you
look
up
how
to
set
your
up
streams
or
syncyourlocaland.com
repositories.
Okay,
hooray.
We've
made
it
to
the
stage
where
you
know
what
you
want
to
change
in
the
code
base.
So
that's
the
commit
stage.
This
is
a
time
where
it's
to
write.
This
is
the
time
where
we
write
those
changes
and
it
actually
took
me
way
too
long
to
figure
out
that
for
smaller
commits
you
can
write
that
code
directly
in
github.com
and
commit
it.
B
I
do
this
when
I'm
updating,
readme's
or
copy
basically,
when
I
don't
need
to
run
tests
before
opening
the
pull
request,
although,
as
you
learned
this
morning,
this
is
where
github
code
spaces
really
shines.
So,
if
you're
interested
in
trying
that
out,
you
can
edit
build
and
commit
in
one
tool,
and
you
can
make
much
more
complex
changes
for
now.
Let's
assume
you're
working
locally
and
you
have
coded
the
fix
with
your
favorite
editor.
B
B
How
can
we
make
this
easier
on
ourselves
right
now,
if
I'm
making
it?
If
I'm
not
making
a
change
on
github.com,
I
love
using
github
desktop
because
it
provides
me
a
gui
that
shows
diffs
with
syntax
highlighting
it
lets
me
partially
commit
with
check
boxes
and
selecting
lines.
It
shows
me
what
I've
selected
when
I'm
committing
my
code,
who
needs
git
status.
B
You
want
to
create
your
code.
You
want
to
credit
your
co-author,
there's
a
spot
for
that,
and
here
I'm
actually
crediting
amanda
pinsker,
who
helped
me
create
the
slides
for
this
talk.
So
thanks
amanda,
once
you're
done
committing,
you
might
find
yourself
fetching
origin
rebasing,
resolving
any
conflicts
that
come
about
before
you're
ready
to
push
desktop,
provides
all
of
these
stuff
with
a
pretty
basic
gui,
and
this
is
how
you
can
move
forward,
but
it's
also
just
as
important
to
know
how
you
can
go
back
because
regrets
are
real.
B
And
yes,
you
can
do
this
with
aliases,
but
I
find
that
the
visual
cues
here
of
showing
the
commit
before
I
do
something
instead
of
passing
in
a
sha,
has
made
me
a
lot
more
confident
before
I'm
taking
these
risks
with
an
alias
that,
I
probably
don't
remember
the
contents
of
now
after
you've
pushed
your
code,
things
get
interesting,
which
brings
us
to
stage
four
code
review
code.
Reviewing
has
two
parts
basically
right:
creating
a
pull
request
and
actually
reviewing
the
code.
B
Oops
github
desktop
provides
a
pull
request
option
if
you
have
a
branch
with
pushed
commits
on
it
and
no
corresponding
pull
request.
So
you
don't
have
to
remember
all
that
it
just
kind
of
knows
when
it's
time
for
you
to
create
a
pull
request,
and
you
can
click
on
that
button
to
get
navigated
directly
to
the
page,
to
create
to
the
on.com.
B
Gibcli
takes
a
different
approach
and
it
lets
you
create
the
prior
directly
in
the
terminal,
complete
with
titles
and
a
body,
and
later
this
month,
you'll
be
able
to
add
labels
and
reviewers
too.
This
is
huge
if
you
already
didn't
know
what
to
write.
Of
course,
you
should
be
able
to
do
it
without
going
onto.com.
B
This
example
shows
how
you
can
sign
all
of
that
with
flags
alone.
As
you
can
see,
it
spits
out
your
created,
pull,
request,
url,
and
then
you
can
navigate
to
the
browser.
If
you
want
or
there's
some
other
things
that
you
can
do,
you
can
pass
in
the
web
flag
and
you
can
go
directly
to
the
web
just
like
the
way
that
github
desktop
does
or
for
fun.
There's
a
fill
flag,
that'll
autofill
your
title
and
description
based
on
your
commit
messages.
B
B
Once
you
create
your
pull
request,
you're
in
this
new
limbo,
right,
you're,
waiting
for
just
another
round
of
taking
a
review
or
seeing
responses
and
adding
these
comments.
So
whenever
you
have
to
make
these
changes,
especially
if
you
do
them
locally,
to
push
them
up,
you're
kind
of
straddling
between
github,
yet
again
github
desktop
lets.
You
go
straight
from
your
pull
request
to
check
out
your
branch
locally.
It
opens
a
branch
in
desktop
and
offers
to
stash
your
changes,
so
you
can
check
out
the
code,
build
it
and
push
your
commits.
B
Github
cli
also
does
something
similar.
You
could
see
your
pull
request
or
the
ones
requesting
your
review
with
peer
status,
which
we've
talked
about
before
and
check
it
out
directly,
either
by
the
pull
request
number
or
by
the
branch
name
and
soon
you'll
be
able
to
give
a
basic
review
too.
I'm
so
excited
for
that.
B
But
if
you
don't
need
to
build
your
code
or
test
the
code
locally,
which
my
absolute
favorite
way
to
review
code
is
on
my
phone,
I
can
leave
comments
onlines
and
I
can
review
the
pr
as
a
whole
and
as
an
engineering
manager.
I'm
rarely
reviewing
majorly
technical
code.
I
think
my
teens
have
taken
pity
on
themselves
and
limited
me
to
reviewing
release,
notes
and
some
simpler
stuff,
which
is
fine
by
me.
B
I
can
do
most
of
my
reviews
on
github
mobile
now
and
if
I
ever
have
complex
comments,
they'll
just
have
to
wait
for
me
to
come
back
to
my
desk,
so
they
asked
for
this
at
the
last
stage,
if
you're
ready
to
smash
that
merge
button
and
maybe
even
initiate
a
release,
I've
seen
most
cases
where
github
has
done
this.
But
technically
you
can
do
this
on
git
as
well.
B
So
the
pro
tip
is,
if
you
rebase
or
merge
on
master
into
your
branch,
github
will
actually
recognize
it,
and
you
might
also
have
hooks
that
recognize
and
initiate
releases
based
on
tags.
Now.
You
can't
do
this
yet,
but
you'll
also
be
able
to
view
and
create
tags.
So
you
don't
need
git
for
any
of
these
steps.
You
can
check
out
this
little
teaser
here,
and
this
has
actually
been
a
requested
feature
for
a
while.
B
So
we're
really
excited
to
be
able
to
provide
it
soon,
not
yet
soon
with
github
cli
you'll
be
able
to
do
some
of
this.
Also,
you
can
use
the
pr
status
to
see
which
pull
requests
have
gotten
approved
and
are
ready
for
to
be
merged
and
soon
you'll
be
able
to
merge
those
pull
requests
and
even
delete
the
branch
locally
and
on
github,
which
saves
you
a
pruning
step.
So
that's
something
that
we
haven't
been
able
to
have
before
soon.
B
B
Something
I
didn't
mention
is
that
github
desktop
supports
enterprise
and
proxies,
and
it
even
provides
an
onboarding
tutorial
to
get
you
acquainted
with
the
git
and
github
workflow
within
desktop,
I'm
also
a
big
fan
of
how
it
handles
conflicts.
It
gives
you
a
progress
bar
as
you've
gone
through
a
rebase
and,
if
you've
ever
struggled
through
the
question,
is
this
rebase
going
to
be
ever
over
the
project?
Progress
bar
is
a
lifesaver.
It
gives
me
hope.
B
Github
cli
dropped
its
beta
a
few
weeks
a
few
months
ago,
not
a
few
weeks
ago,
a
few
months
ago.
So
this
is
this
feature
list
is
a
little
bit
thinner,
but
if
you've
been
following
along
they're
rapidly
coming
out
with
new
features
in
the
most
recent
ship,
you
can
get
and
set
your
config,
which
means
that
you
can
set
your
git
protocol
to
ssh
instead
of
it
defaulting
to
https.
B
I
really
like
that.
It
also
gets,
has
a
pretty
solid
help
menu
and
it
has
an
online
manual
that
includes
example
of
usages.
I
use
the
online
manual
all
the
time,
so
I
encourage
you
to
check
it
out.
Finally,
the
workflows
that
we
went
through
only
touched
a
small
sampling
of
github
mobile's
functionality.
B
My
favorite
ones
that
I
haven't
mentioned
are
being
able
to
triage
with
labels
and
which
I
need
to
do
as
a
good,
open
source
contributor
and
adding
reactions.
As
I
check
out
issues,
it's
such
a
little
thing,
but
I
get
such
a
rush
of
dopamine
every
single
time.
I
can
emote
with
a
heart
or
a
rocket,
and
let
someone
know
that
I'm
reading
their
comments,
which
I'm
obviously
doing,
because
I
can
do
that
on
github
mobile
as
promised.
B
B
The
best
way
to
keep
track
of,
what's
coming
up,
is
to
make
sure
that
you're
checking
out
github's
blog
or
following
the
github
or
gh
changelog
twitter
accounts
that
update
you
on
the
latest
changes,
but
since
you've
made
it
this
far
I'll
share
one
more
secret
on
how
you
can
get
a
sneak.
Peek.
I
haven't
mentioned
it
yet,
but
desktop
and
cli
are
open
source
projects,
which
means
that
they
have
open
source
project
boards
as
well
on
the
repository.
B
If
you
have
feedback,
you
can
open
an
issue
directly
into
cli
or
desktops
open
source
projects,
and
you
can
always
email
mobile
feedback
at
github.com
for
mobile
to
share
what
you
think.
Cli
also
has
a
feedback
survey,
that's
linked
on
help.
It's
help
docs
it's
in
this
help
command
and
on
the
repositories,
need
me,
which
you
can
fill
out
and
use
what
you
need
so
keep
in
mind
that
these
are
hard
working
people
and
they're
just
doing
the
best
that
they
can.
B
So
the
best
way
to
help
them
out
is
to
share
context
on
what
you
need,
how
bad
the
pain
is
and
like
what
actually
is
affecting
your
workflow
or
what
you
might
want
to
use
it.
For
that,
the
more
information
that
you
provide
to
us,
the
better.
We
can
make
better
the
better
decisions
that
we
can
make
all
right.
We
did
it.
We
just
went
through
a
bunch
of
ways
that
you
can
change
up
your
workflows
using
github
desktop
github,
cli
and
github
mobile,
which
is
approximately
50
alternatives.
B
I
don't
expect
you
to
have
all
these
memorized,
but
you
can
always
refer
back
to
this
diagram
to
see
what
you
might
want
to
try
out.
These
tools
are
meant
to
extend
and
augment
your
experience,
nothing
more
and
think
about
it.
This
way,
how
many
times
have
you
tabbed
over
your
browser,
only
to
get
distracted
by
all
the
tabs,
the
email
counter,
the
slack
bubbles,
the
twitter
notifications?
B
If
I
want
to
stay,
focused,
I'm
going
to
need
an
army
of
bodyguards
guiding
me
to
the
back
door
of
my
next
page,
because
I
absolutely
will
get
distracted
a
lot
of
these
alternatives.
Do
that
for
you.
This
is
where
I
leave
you,
but
I'm
not
gone
forever.
I'm
still
here
for
q,
a
and
github
satellite
has
a
discussion
open
for
each
session
today.
So
you
can
check
mine
out
and
ask
questions
about
any
of
the
applications
and
my
teammates
are
standing
by
to
respond
to
you
directly.
A
Whoa,
that
was
an
amazing
amazing
talk.
It
wasn't
50
000
different
types.
It
was
fine,
it
was
accounted,
get
github.com
get
on
desktop,
get
up,
cli
get
up
model.
I
just
mobile.
I
just
love
it.
I'm
excited,
I'm
so
excited,
and
I
the
thing
that
blew
my
mind
is
the
fact
that
submitting
a
pull
request
will
create
a
fork
for
you
in
a
repo,
if
you
don't
have
push
access
get
out
of
town.
That
is
such
an
awesome
feature.
A
But
before
I
go
off,
people
have
been
asking
questions,
so
I
don't
want
to
chew
up
all
the
time
fan
girl
in
this
set
of
products.
I
want
to
make
sure
we
can
get
straight
to
the
questions
and
let
chad
come
in
and
ask
his
own
questions
as
well.
So
github
user
pluma
says
dozen
will
github
for
windows
work
with
wsl2.
B
C
Yeah
yeah,
so
I'm
a
vim
user
so
and
I'm
really
tired
of
tabs
in
the
browser.
So
I
can
really
really
really
see
myself
using
a
lot
of
cli
the
cats
out
of
the
bags
that
I
heard
a
preview
of
your
talk
yesterday
you
got
me
really
jazzed,
so
I've
been
trying
out
get
up,
desktop,
cli
and
mobile
all
morning.
One
thing
I
was
hoping
for
on
mobile
that
I
didn't
find
was
getting
up.
Projects
is
that
on
the
roadmap.
B
Yes,
so
by
yes,
I
mean.
Yes,
I'm
really
excited
to
answer
your
question.
So
let
me
try
and
explain
where
we
are
so
so
with
cli
we've
kind
of
started
with
these
main
workflows
that
everyone
works
in,
and
so
we're
really
interested
in
getting
feedback
as
to
what
you
might
use
them
for
and
like
particularly
at
what
part
in
your
workflow.
B
So
it's
something
that
we're
thinking
about,
but
we
want
to
be
really
conscientious
about
how
to
do
it
and
for
mobile.
This
is
something
that
they're
interested
in
in
exploring,
and
so
one
of
the
best
ways
to
give
your
thoughts
is
to
go
to
the
email
address
that
I
provided
and
or
to
talk
about
it
in
discussions
and
kind
of
give
the
feedback
and
what
you're.
Looking
for.
B
So
right
now,
since
codespaces
is
at
the
beginning
stages,
we
don't
have
direct
integration,
but
this
is
actually
a
conversation,
we're
having
very
actively
we're
interested
in
figuring
out
how
we
can
connect
the
two,
especially
in
a
world
where
you
are
basically
on
the
web,
and
you
have
this
environment.
If
you
ever
need
to
go
locally,
we
want
to
be
able,
especially
if
there's
demand.
So
let
us
know
we
want
to
be
able
to
provide
that
for
you.
If
this
is
something
that
you're
interested
in
doing.
C
Cool,
so,
as
I
mentioned,
I
anticipate
I'd
spend
most
of
my
time
in
the
cli
more
than
more
than
desktop,
because
I
don't
write
that
much
code,
but
I'm
still
thinking
about
how
and
when
to
use
what
so
as
you're
an
engineering
manager
and
I'm
an
engineering
manager.
What
kind
of
workflow
do
you
recommend
for
managers.
B
All
right
so,
for
the
most
part
I
kind
of
joked
about
it
earlier.
I
do
most
of
my
work
on.com
because
I'm
editing
copy
or
I'm
doing
a
readme
or
release
notes,
but
there
are
a
few
cases
where
I
might
want
to
test
something
locally
in
the
case
that
I
want
to
test
something
locally
or
if
especially,
if
my
reviews
requested
there's
kind
of
like
this
way
to
check
out,
you
can
check
it
out
on
cli
or
desktop.
B
So
I
like
to
directly
get
directed
to
cli
or
desktop,
and
if
I
know
exactly
what
I
want
to
do
chances
are,
I
have
to
build
her.
I
have
to
run
it
in
my
terminal,
so
that's
where
I
start
using
cli.
So
I
can
use
pr
status
at
that
point
and
I
can
basically
use
all
the
tools
that
I
need
to
to
make
sure
that
I
provide
my
my
feedback.
B
If
I'm
looking
into
a
new
repository
brand
new
because
as
a
manager
and
especially
at
github,
we
manage,
we
have
like
all
of
our
work
on
github,
and
so
I'm
going
through
about
like
30
repositories.
I
do
all
of
that
management
on
github
desktop,
but
finally,
like
I
honestly
I'm
on
the
go
a
lot
or
I
might
be
going
back
and
forth,
and
so
when
it
comes
to
figuring
out
a
is
there
anything.
That's
blocking
me
because
I
have
all
these
repositories
that
I
have
to
go
in
between
mobile
is
my
go-to.
A
B
Right
now,
yeah
like
basically
a
world
where
you
could
bounce
between
github,
desktop
and
github,
cli,
etc
and
like
to
mobile.
I
think,
like
it's
a
little
harder
to
imagine
a
world
where
you
might
bump
from
mobile
to
to
cli
or
desktop
one
of
the
best
parts
about
all
of
this
is
that
all
of
your
information
is
being
synced
right.
So
the
minute
you
push
up
your
work
from
cli
and
desktop.
It
goes
to
com,
and
then
that
means
that
information
synced
with
your
mobile
account.
B
So
that
is
one
of
the
ways
we
use
is
kind
of
like
to
sync
through
github,
and
that's
like
I
kind
of
showed
you
that
if
you
wanted
to
check
out
your
your
pr,
you
can
kind
of
go
directly
from
com
to
your
pr,
and
so
those
are
kind
of
like
one
of
some
of
the
ways
that
we've
recently
worked
in
and
if
you
remember
the
code
spaces
tutorial
this
morning,
you
could
there's
also
this
code
button,
and
so
it
allows
you
to
check
out.
You
have
desktop
that
way.
B
I
want
to
know
okay,
what
is
the
point
that
you're
interested
in
going
from
desktop
to
cli
so
that
we
make
sure
that
we
build
the
right
thing
and
that's
one
of
the
best
parts
about
being
in
an
open
source
world
is
that
I
can
ask
you
that
question
and
then
you
can
actually
directly
answer
that
question
at
any
time.
At
your
leisure.
C
B
Right
so
for
there's
two,
and
so
with
github,
cli
and
github
desktop.
What
you'll
want
to
do
is
if
you
have
a
bug
or
if
you
have
a
feature
request.
The
best
way
to
get
started
is
to
go
ahead.
Open
an
issue.
You'll
usually
see
people.
We
have
like
a
commitment
to
make
sure
that
we
respond
to
everyone
within
a
week,
but
you'll
see
people
respond
a
lot
faster.
We
have
great
time
zone
coverage,
and
so
there's
really
people
who
are
interested
in
hearing
more.