►
From YouTube: GitHub Beyond Your Browser - GitHub Satellite 2017
Description
Presented by:
Phil Haack
Director of Engineering for Client Apps, GitHub
GitHub is an important part of a developer's workflow. It helps developers coordinate and collaborate on software. But most of the help that GitHub provides is in the browser, waiting for developers to reach out to it. Meanwhile, developers write code on their own machines with text editors and IDEs.
We can reduce friction and improve workflows by bridging that gap. The GitHub Client Apps team extends GitHub beyond the browser to fill that gap. This team consists of Atom, Electron, Desktop, and Editor Tools. In this talk, you'll learn about the tools we've shipped to make your GitHub workflows better.
At Satellite 2017, attendees came to exchange cutting edge practices on how to bring together the people and tools you need to build great software. Watch the recordings to find out what GitHub's been working on, and hear how other teams use the GitHub ecosystem to customize the way they work.
We'll be getting together again in San Francisco on October 10th-12th for GitHub Universe. We hope you'll join us for three days filled with the creativity and curiosity of the largest software community in the world.
For more information, go to githubuniverse.com.
A
Hello,
everyone
I'm
really
glad
to
be
here
in
London.
I
was
actually
here
back
in
March,
but
before
I
begin,
I
have
to
ask
from
what
I
hear
the
name:
github
I'm
gonna
sound,
really
funny
to
you
right.
You
can
be
honest
like
why?
Would
anyone
want
to
build
a
site?
That's
the
hub
of
unpleasant
people.
A
Well,
I'm
glad
you
do
like
our
site
and
I'm
glad
you're.
Here
you
stuck
with
us
and
I.
Think
your
on
behalf
of
github
now
on
to
the
matter,
github
beyond
the
browser.
So
when
you
use
github,
you
spend
a
lot
of
time
in
the
browser
you
review,
pull
requests.
You
look
at
profiles,
you
might
argue
the
value
of
semicolons
or
lack
thereof,
an
issue
comments
endlessly,
but
that
assumes
that
the
code
has
already
hosted
up
there
on
github.
But
before
it's
hosted
when
the
code
is
on
your
machine,
you
spend
a
lot
of
time.
A
A
A
Excuse
me:
how
does
one
get
anyways?
Well?
The
answer
lies
in
this
xkcd
comment.
This
is
good.
It
tracks
collaborative
work
on
projects
through
a
beautiful
distributed
graph
theory
tree
model
cool.
How
do
we
use
it?
No
idea
just
memorize
these
shell
commands
and
type
them
to
sync
up.
If
you
get
errors,
save
your
project
elsewhere
delete
the
work
and
download
a
fresh
copy
right.
This
is
the
mental
model
of
get
that
a
lot
of
people
who
you
get
every
single
day
have.
A
We
build
tools
that
slot
into
the
way
you
want
to
work
and
in
some
cool
some
cases,
these
tools
make
it.
So
you
don't
need
yet,
if
you
really
don't
want
it,
but
for
the
most
part
they
act
as
a
bridge
between
get
github
and
the
tools
that
you're
using
every
day
and
they
bridge
the
gaps.
They
don't
replace
these
tools,
they
don't
replace
git.
After
all,
I
personally
still
love
you
can
get
warts
and
all,
but
sometimes
I
need
a
little
help.
So,
first
a
little
about
me.
A
A
So
this
is
a
group
that
consists
of
four
teams
listed
here.
First,
we
have
Adam
a
text
editor,
you
know
and
love.
Just
last
week
we
announced
the
new
beta
that
includes
git
and
github
integration,
a
desktop
which
Chris
had
referred
to
in
this
keynote,
a
cross-platform
GUI
forget
and
github
released
last
week.
A
It's
the
next
generation
of
our
pre-existing
clients,
which
used
to
be
separately
billed
for
Mac
and
Windows,
but
now
they're,
both
built
on
electron,
a
platform
that
lets
you
use
web
technologies
to
build,
cross-platform
applications
and
and
as
I've
mentioned
atom
and
desktop,
are
now
built
using
electron,
we're
not
the
only
ones
building
on
it,
though,
a
lot
of
other
companies
are
making
huge
investments
in
electron,
we've
seen,
flack
Microsoft
is
building
on
it.
In
fact
reason
we
recently
we
learned
that
a
title.
A
The
music
company
by
Jay
V,
is
building
their
music
or
built
their
music
player
on
it.
So
I
like
to
imagine
jay-z
and
Beyonce
our
programming
on
electron.
That
could
happen
and
then
the
last
team
is
editor
tools.
So
this
team
builds
extensions
for
existing
editor,
such
as
Visual
Studio
and
unity,
and
get
up
for
unity.
Get
up
for
Visual
Studio
get
up
for
unity.
I
know
it
sounds
like
a
benefit
festival,
but
it's
actually
a
plugin.
A
So
here's
what
we
believe
we
want
to
extend
github
to
where
developers
write
software.
We
believe
that,
in
order
to
be
where
developers
build
software,
we
need
to
be
everywhere,
software's
built.
If
Chris
had
mentioned,
we
need
to
go
where
you
are.
We
need
to
meet
you
where
you
are,
then
the
reason
we
want
to
be
everywhere
is
we
genuinely
want
to
help
developers
have
a
good
time
when
the
writing
code
to
get
and
using
github,
we
want
to
make
it
more
approachable
and
more
productive.
A
We
want
to
build
tools
that
fit
the
way
you
work
and
we
believe
that
github
is
much
more
than
just
the
command
line
or
the
browser
to
demonstrate.
My
point
I've
concocted
this
wild
scenario.
It's
a
little
story
that
may
feel
a
little
familiar
if
you've
written
software
as
part
of
a
team.
So
imagine
we
have
a
software
team
named
TBD,
that's
the
actual
team
name
and
they're
building
a
to-do
app
like
many
opinionated
developers
out
there.
A
They
hate
every
to-do
list
app
out
there,
so
they
decided
they
had
to
build
their
own,
and
this
app
requires
a
back-end
service,
a
friend,
end
registration
website
and,
for
some
reason,
an
Easter
Egg,
where
you
can
play
a
game
they're
going
to
require
developers,
designers,
documentation,
writers,
testers
support
lawyers
and
others
to
all
work
together,
and
this
is
where
we
begin
our
story,
so
I
will
switch
here.
Second,
all
right.
A
Okay,
great,
that's
working,
so
here's
the
front
end
to
the
to-do
app.
This
is
a
repository.
It's
a
simple
electron,
app
and
I
mentioned.
Oh
I
forgot
to
mention
that
the
list
of
names
are
these
various
personas
that
I'm
going
to
take
as
I
go
through
this,
and
so
we
have
this
to-do
app,
that's
written
in
electron.
This
is
the
front
end
and
it's
talking
to
back-end
services.
So
you
can
see,
don't
forget
things
pretty
pretty
straightforward
right!
A
So
now,
I'm
Don
to
develop
a
Don
to
designer
and
I
need
to
go
to
pull,
request
and
I,
see
that
little
slow
I
see
that
someone's
made
up
a
pull
request,
design
changes
for
Don,
oh
no!
It's
the
manager
he's
like
hey,
Don,
I'm,
not
a
designer,
but
I
figured
how
hard
could
it
be?
Here's
my
suggestions
for
sprucing
up
the
app.
Oh
boy:
I
love
it.
When
managers
decide
they,
we
can
know
how
to
design
right
now.
A
Here's
the
thing
if
I
want
to
I
could
review
the
code
changes
right
here
in
github,
but
I,
don't
know
about
you,
but
when
I
look
at
CSS,
I
can't
necessarily
translate.
What's
that
going
to
look
like
when
I'm
actually
running
the
app
and
what
I
really
want
to
do
is
go
here
and
run
the
set
of
git
commands
and
get
this
code
up
in
the
cloud
onto
my
local
machine?
A
Well,
it
not
a
lot
of
people
realize
is
that
if
you
have
desktop
installed,
I'm
going
to
zoom
in
here
oops
sorry,
we
have
this
nice
open
this
in
github
desktop
so
rather
than
running
that
set
of
three
or
four
commands
I'm
going
to
just
click
this
button
and
you
see
on
Windows
and
Mac.
The
experience
is
slightly
different,
but
it's
saying
o
open
get
up
desktop
and
that
happened
really
quickly.
But
I
want
you
to
notice
right
here
in
the
top
there
I'll
zoom.
In
again
it's
on
the
branch
of
the
pull
request.
A
Now
it
pulled
that
code
down
switch
to
that
pull
request
branch
so
now
I
can
actually
go
and
run
this
app,
so
I'm
going
to
go
npm
start,
and
this
is
an
electron
app
again
pretty
straightforward
and
oh
no!
This
is
terrible.
So
I've
seen
the
design
that
the
the
manager
is
trying
to
do
design.
It's
got
comics
as
Dondo
designer.
I
need
to
help
this
design
out.
A
So
what
I'm
going
to
do
is
create
a
new
branch
in
desktop
so
I'm,
going
to
a
file
new
branch
and
we're
going
to
call
this
design
fixes
and
then
I
can
pick
which
branch
I
want
to
target
so
I'm
going
to
make
these
changes
against
this.
These
fixes
that
my
manager
had
submitted
and
I'll
create
this
branch,
and
now
I
can
go
to
my
editor
of
choice
and
make
these
changes.
Now
what
I'm
going
to
do,
because
I
find
that
live
coding
is
fraught
with
error.
A
I
have
already
succeed,
I've
already
prepared
a
set
of
patches,
so
you
can
imagine
that
I
just
went
in
I
did
my
work
right
in
my
editor
of
choice.
Maybe
it's
notepad
and
now
I'm
going
to
go
back
to
desktop
and
we
can
see
in
the
changes
view
it
lists
the
changes
that
I
made.
Now
you
could
do
all
this
in
the
git
command
line,
but
one
nice
thing
where
I
feel
like
the
desktop
application
excels
is
when
you
create
commits
it's
really
nice.
A
A
I'm
going
to
uncheck
views
main
JSX
and
I'll
just
go
ahead
and
check
in
everything
else,
some
design
stuff
and
commit
that,
but
with
main
I,
can
actually
select
individual
lines
and
say
you
know
what
I
just
want
to
commit
that
change
or
that
set
of
change.
If
I
click
in
this
little
gutter
here,
I
can
select
a
block,
so
I
might
say
commit.
This
is
one
logical,
commit
change
the
header
to
header
tags
and
commit
that
and
what
you
see
that
that
change
now
has
been
committed.
A
Hopefully
you
have
better
commit
messages
than
I
do
and
then
I
can
go
ahead
and
I
can
publish
this
branch,
so
I
click
that
and
that's
pushing
the
branch
up
to
github,
calm
and
now
that
it's
there
I
can
go
to
the
branch,
mute
menu
and
you'll
notice.
Here
we
actually
do
accelerator
key,
so
we
try
to
have
keyboard
navigation
for
just
about
anything.
A
So
alt
B
will
bring
up
the
branch
and
I
can
go
to
compare
and
github,
and
you
can
see
what
shortcut
that
corresponds
to,
and
that
brings
up
the
compare
view
and
so
then,
from
there
I
can
create
a
pull
request
and
say:
hey!
Try
this
instead,
so
you're
gonna
have
to
use
use
your
imagination
here
and
pretend
that
that's
dawn
and
not
me,
but
we'll
go
there.
So
let's
actually
try
these
changes.
That
dawn
the
designer
made,
and
we
can
see.
Oh,
that
that
looks
better.
A
A
Toggle
developer
tools
or
control
ship
die
so
as
if
you
were
in
Google
Chrome,
and
you
get
your
you
get
your
developer
tools
right
there
in
the
bar,
so
you
can
actually
run
our
app
and
you
can
explore
our
HTML,
our
a
CSS.
You
can
actually
run
JavaScript
in
the
console
here
against
the
app
and
you
could
really
get
a
deep
sense
of
how
our
app
is
running,
and
the
same
is
true
for
Adam
as
well.
So,
ok,
so
we're
going
to
switch.
A
So
that
was
the
workflow
of
Don,
the
designer
working
well
with
the
developer
team.
So
now
we
have
Frederik
the
front-end
developer
and
I
need
to
make
some
changes
to
the
node
site
that
Lex
on
site
and
I'm
going
to
open
this
in
Adam.
So,
let's
see
Adam
dot
so
I'm
running
the
version
that
Adam
the
latest
beta.
That
was
just
released
last
week
and
she
did
it.
Oh
there.
It
is.
A
And
down
here
kind
of
hard
to
see,
because
it's
a
little
small
but
I'm
actually
going
to
switch
to
this
hack
tries
the
code
branch.
So
we
have
a
little
branch
switcher
right
down
there
and
one
thing
you
can
see
down
here:
I'll
zoom
in
there
you
can
see
that
it
tells
you
like
what
my
git
status
is
so
I'm
one
commit
behind
masked
behind.
A
What's
on
the
code
on
github,
comm
and
I'm,
one
ahead,
also,
what's
on
github,
calm,
meaning
I
have
a
local
commit
that
I
haven't
pushed
what's
cool
here
is
that
I
can
go
to
the
get
up
pane
and
we
can
see
that
there
are
tool,
pull
requests
associated
with
them.
So,
let's
oh
I,
see
so
I'll
click
one
of
these.
So
normally
you
might
have
one
pole
request
associated
with
the
branch,
and
so
when
you
go
to
this
pane,
you
can
actually
see
the
pull
request.
A
That's
already
exist
for
this
branch
and
it
says
hi
Frederick
trying
to
be
helpful,
pointing
care
boss
here
and
write
some
code
to
provide
an
error
method
for
empty
tasks.
Could
you
take
a
look
at
this?
I
have
no
idea
what
I'm
doing
alright
so
we're
going
to
help
the
manager
out
again
and
what
I'm
going
to
do
here
is
I'm
going
to
pull
this
changes
so
again,
I'm
going
to
try
to
zoom
in
here,
so
you
can
see
what
I'm
doing
so.
A
I
can
just
click
on
this
down
arrow,
and
you
see
it
gives
me
a
menu
to
pull
or
push
I'm
going
to
pull.
First
and
let's
see
what
happened?
Oh,
we
got
an
error.
It
says
we
have
commerce
conflicts,
so,
according
the
xkcd,
what
I
do
next
is
I,
delete
the
project
and
reclone
it
and
start
all
over.
Well,
not
anymore
with
Adam
I
can
click
on
here
and
oh
wait.
A
Yep
there
we
go
and
we
can
see
here
that
the
merge
conflicts
are
highlighted
for
us
and
we
have
a
way
of
easily
picking
which
change.
Do
we
want?
Do
we
want
the
one
we
pulled
down
or
do
we
want
the
one
that
we
have
locally
so
I'll
just
go
ahead
and
click
use
me
there,
but
not
only
do
we
have
the
ability
to
pick
the
change.
We
can
also
go
in
here
and
just
edit
with
everything.
A
A
So
that's
a
tricky
thing
you
gotta
remember
to
save
after
you
resolve
a
conflict
so
now
I
can
double
click.
This
and
I
can
hit
commit
and
I've
merged
I've
resolved
those
merge
conflicts
now
I've
committed
those
changes
and
I'm
going
to
make
some
more
changes
here
and
once
again,
I'm
cheating
by
I
have
my
changes
prepared
ahead
of
time.
This
is
my
Julia
Child's
moment
where
I
just
take
the
cooked
turkey
out
of
the
oven,
nobody's
a
Julia
Child's
fan
here.
All
right,
that's
fine!
A
So
here
we
Adam
is
picked
up
the
set
of
unstaged
changes.
Now
I
can
go
in
and
I
can
make
commits,
but
I
can
also
do
partial
commits
just
like
we
did
with
desktop
so
here
I'll
write,
I'll,
select
those
changes
and
right
click
and
stage
that
selection,
and
you
can
see
here
that
these
space
changes
are
there.
I
can
commit
that
so
commit
stage,
changes
and.
A
Voila,
the
rest
of
the
changes
are
still
in
here.
I
can
commit
the
rest,
so
I
could
stage
that
all
of
it
by
clicking
that,
but
since
it's
just
one
file,
I
can
double
click
the
stage
it
and
commit
the
rest.
So
you
get
a
nice
control
of
creating
commits
right
from
within
Adam.
You
don't
have
to
leave
if
that
fits
the
style
of
development
that
you
prefer.
A
A
A
Okay,
all
right,
so
we're
going
to
step
the
front
end
electron,
but
this
front
end
electron
app
need
to
talk
to
a
web
service,
and
so
I
built
a
web
api
using
asp.net
core
8
feet
under
MVC
core.
It's
the
new,
the
new
MVC
stack
from
Microsoft,
because
I
was
kind
of
curious
to
see
how
far
it's
come
along
in
a
previous
life.
I
worked
at
Microsoft
on
asp.net
MVC,
so
I
thought
I'd
see
what
the
the
new
rage
is
and
so
we're
going
to
navigate
to
the
API.
A
So
this
is
also
up
on
github,
so
we
have
to
do
app
and
to
do
API
and
one
of
the
things
I
want
to
show.
Is
this
clone
or
download
button
here,
and
you
can
see
that
there's
this
open
and
Visual
Studio?
So
if
you
have
the
Visual
Studio
extension
installed
and
you've
logged
into
it
into
github
with
it,
we
light
up
this
button
because
we
now
know
that
you,
you
can
support
this,
and
when
you
click
this
you
can
see
it
will
open
it
in
Microsoft,
Visual
Studio.
A
So
again,
this
is
when
I
mentioned
earlier,
the
bridge.
This
is
what
I'm
talking
about
how
we
can
take
this
experience
in
a
browser
and
seamlessly
pull
it
down
into
your
local
machine
and
that
we'd
like
to
extend
this
experience
to
other
editors
down
the
road.
One
of
the
things
here
is
a
little
different
from
desktop.
It
doesn't
start
cloning
it
automatically
it
populates
the
clone,
dialog
and
then
I
can
start
getting
to
work
on
this
repository
right
from
visual
studio.
A
I
happen
to
already
have
opened
it
because
they
didn't
trust
that
the
Wi-Fi
would
be
fast
enough
or
actually
wait
there.
It
is
I
already
have
it
cloned.
So
we
have
this
so
I'm
individual
studio
and
again
it's
an
IDE
where,
if
you're
not
familiar
with
it,
a
lot
of
it
almost
provides
everything
you
could
ever
want
as
a
developer.
A
All
in
one
package
and
developers
who
tend
to
use
visual
studio
like
to
stay
in
visual
studio,
so
I'm
going
to
go
to
the
github
pane,
and
you
can
see
here
that
there's
a
list
of
pull
requests
we,
so
we
if
you're
in
a
repo,
we
know
what
reposes
we
look
on
github.com.
We
pull
down
the
pull
request
and
we
list
them
right
here,
a
little
bit
different
behavior
from
Adam,
but
you
know
we're
working
to
make
a
lot
of
these
experiences
more
and
more
similar
as
we
move
further.
A
What's
nice
about
this,
is
you
know,
as
you
can
imagine,
I
might
want
to
check
out
the
code
in
this
pull
request.
So
I
can
go
click
on
this
pull
request
and
then
I
can
check
out
the
change.
This
pull
request
right
there
and
that's
going
to
check
out
that
branch
and
bring
that
code
down
to
my
local
machine
now
I'm
going
to
make
some
changes
there.
Oh.
A
I
got
to
make
sure
that
I
switch
to
the
right
project.
Ok,
so
Beatrice
is
the
back-end
developer.
Now
we've
made
some
changes
and
I
can
go
to
this
team
Explorer
and
the
Riva
tour.
Let's
go
to
this
little
house
here,
you
can
see
one
of
the
tricky
aspects
of
extending
someone
else's
IDE
is
that
you
have
to
work
within
their
ecosystem
and
what's
interesting
here
is
that
this
pane
here
is
called
the
team
Explorer
pane
for
historical
reasons
and
we're
trying
to
fit
github
in
there.
So
the
changes
view
is
actually
their
functionality.
A
That's
not
us,
but
as
you
can
imagine,
pull
requests.
That's
us,
and
so
we've
tightly
integrated
an
experience
that
really
feels
native.
So
when
I
go
to
here
and
click
this,
this
is
the
you
know.
This
is
all
Visual.
Studio
shows
me
to
disk.
I
can
fix
the
blank
error,
handling
and
create
the
commit
here.
A
So
again,
that's
still
functionality,
that's
specific
to
Visual
Studio,
but
when
I
go
to
the
pull
request,
I
can
create
new
one
and
I
can
have
this
change
of
port
I
pick
the
branch
that
I
want
to
target
I'll
just
go
ahead
and
target
this
test,
the
change
PR
now
this
is
all
Fiat
hub
integration
that
we've
built
into
Visual
Studio
that
I'm
sure
I'm
right
there
all
right.
So
now
we're
going
to
go
to
the
gabriella
the
game
developer.
A
For
some
reason,
this
team
decided
that
it
wanted
to
put
in
easter
egg
in
the
electron
app
and
have
a
full
game
in
there.
It's
really.
We
all
know
that
that
was
just
contrived
so
like
a
demo
unity,
but
let's
work
with
me
here.
So
this
is
a
game
called
dat
boy
and
I'm
going
to
run
it
real
quick-
and
you
can
see
here
that,
like
I,
can
actually
move
this
around.
A
A
So
when
I'm
down
here,
I
can
actually
right.
Click
here
and
I
can
request
a
lock
and
I'll
zoom
out,
and
you
can
see
here
that
that
put
a
little
icon
there.
So
that's
now
locked
and
nobody
else
can
change
that
file.
While
I'm
doing
these
changes
so
I'm
going
to
zoom
out
I'm
going
to
again
the
Julie
Child's
moment
here,
I
see.
A
And
then
there's
a
way
to
push
it,
but
I
forgot
okay
in
case
so
we're
trying
we're
trying
to
reach
new
audiences,
so
getup
for
unity
is
currently
still
in
at
what
we
call
it.
Consider
a
pre
viewer
or
alpha
stage,
so
it
isn't
quite
as
polished
as
the
experience
you'll
find
in
visual
studio.
Yet
so
that's
unity.
A
A
A
Adam
is
that
you
know
a
full-featured
text
editor,
so
the
source
code
can
be
challenging,
but
it's
also
broken
up
into
a
lot
of
packages.
It's
a
highly
extensible.
We
set
out
to
build
the
you
know.
Most
extensible
text
editor
possible
where
you
can
leverage
your
existing
HTML
CSS
JavaScript
skills
to
extend
it.
So
that's
a
great
example
of
you
know
a
text
editor,
but
the
packages
are
kind
of
interesting
to
you
know,
write
your
own
package.
A
Electron
is
open,
source
and
desktop
one
of
the
cool
things
about
desktop
as
an
open
source
application
is
we've
seen
a
lot
of
apps
on
electron
early
apps,
we're
kind
of
like
hey
I'll,
take
my
website
and
a
hosted
an
electron
now
at
the
desktop
app,
and
that's
certainly
a
quick
way
to
get
your
app
running
on
the
desktop,
but
with
a
debt
def
overloading
these
terms
with
get
of
desktop.
We
really
wanted
to
build
an
app
from
the
ground
up
that
felt
native
as
much
as
possible
that
use
the
paradigm
unique
to
each
platform.