►
Description
Presented by Cory Wilkerson, VP, Engineering
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
The
github.com
code
base
is
almost
14
years
old
when
the
first
commit
for
getup.com
was
pushed
rails
was
only
two
years.
Old
aws
was
won
and
azure
and
gcp
did
not
yet
exist.
Over
those
14
years,
github's
core
repos
have
seen
well
over
a
million
commits
the
vast
majority
of
those
commits
were
built
and
tested
on
mac
os.
A
Our
migration
to
codespaces
had
two
goals:
first,
to
build
a
better
product
and
validate
the
code.
Spaces
works
well
for
all
kinds
of
applications,
including
those
as
complex
as
github.com.
Second,
we
want
to
make
the
most
of
our
development
time.
Managing
a
local
environment
can
be
a
difficult,
time-consuming
task,
but
we
want
to
keep
our
attention
focused
on
creating
something
new
with
some
great
work
from
my
teammates.
We
achieve
both
goals,
while
building
tools
that
we
believe
represent
the
future
of
software
development.
A
The
same
tools
that
we're
bringing
to
you
at
github
we've
always
prioritized
a
great
local
development
experience
from
day
one
a
first
day
engineer,
working
on
a
new
machine
could
expect
to
have
their
environment
up
and
running
in
about
a
day's
time,
but
the
daily
experience
still
presented
regular
challenges
and
these
challenges
aren't
unique
to
github.
We
all
experience
these
problems.
A
Things
don't
break
because
of
a
lack
of
understanding
or
skill
things
break
because
the
rate
of
change
in
our
systems
and
because
we're
trying
to
absorb
all
of
this
change
onto
a
single
machine,
but
with
code
spaces
we
bring
code
to
an
environment,
that's
built
to
run
that
code,
and
in
this
model
we
can
spin
up
resources
on
demand.
We
can
work
in
parallel
development
tracks
and
if
something
goes
wrong,
we
can
click
a
button
and
launch
into
a
clean
environment
at
any
time.
This
is
a
huge
relief.
A
Before
shipping
code
spaces
broadly,
we
knew
that
we
needed
to
win
over
our
internal
teams,
starting
with
github.com
and
taking
14
years
of
mac,
os
development
assumptions
and
migrating.
All
of
that
to
a
linux
host
was
no
small
feat,
but
after
just
a
few
iterations,
we
had
github.com
up
and
running
in
a
codespace,
all
32
processes
representing
ruby,
c
go
and
other
platforms.
A
Our
first
iterations
had
a
startup
time
of
around
45
minutes,
which
was
fine
for
prototype,
but
it
really
wasn't
transformative
internal
github
teams,
weren't
going
to
change
their
habits.
We
all
want
our
environment
to
start
in
just
seconds.
There
were
three
important
milestones
in
our
optimization
journey:
our
first
leap
getting
time
to
development
down
from
45
minutes
to
25
minutes.
Instead
of
a
full
get
clone
of
a
very
large
repository,
we
moved
to
a
shallow
clone,
then
the
repository
would
be
unshallowed.
In
the
background
when
the
codespace
was
launched,
our
next
target
was
five
minutes.
A
We
moved
a
large
amount
of
bootstrap
code
into
an
image
that
we
build
every
night
using
github
actions.
This
image
is
then
referenced
in
the
project's
dev
container
and
with
this
image
our
code
space
has
booted.
Just
a
few
commits
behind
the
tip
of
our
main
branch
and
five
minutes
is
great,
we're
feeling
good
but
come
on.
You
know
we
didn't
stop
there.
A
A
A
A
The
computer
club
was
a
simple
but
fun
idea,
so
you
remove
github
source
from
your
machine
and
you
commit
to
using
code
spaces
if,
for
some
reason
you
have
to
churn
if
code
spaces
isn't
working
for
you,
you
have
to
raise
the
feedback
to
the
code,
spaces
development
team.
Anyone
churning
from
codespaces
was
our
trigger
to
get
to
work.
That
meant
something
was
broken
in
the
experience
and
every
bit
of
feedback.
We
captured
helped
shape
the
product
and
moved
us
one
step
closer
to
launch.
A
On
the
back
of
this
momentum,
we
launched
code
spaces
to
get
up
teams
and
enterprise
cloud
plans
in
mid-august.
Codespaces
is
now
the
center
of
github's
daily
workflow
and
represents
the
future
of
software
development,
a
future
that
we're
happy
to
share
with
you.
On
the
other
side
of
our
migration.
We
can
say
we
built
a
better
code
spaces
product.
We
demonstrated
that
codespaces
is
well
suited
for
any
number
of
applications,
and
we
made
things
great
for
github,
as
we
focused
on
making
things
great
for
you.
As
with
anything
github
does.