►
From YouTube: Maximize productivity with GitHub Codespaces
Description
In next month’s “30 Minutes to Merge”, we’ll learn about GitHub Codespaces with GitHub Senior PM Tanmayee Kamath.
#30minutestomerge
Tanmayee will share an overview of the service and walk through some of the latest features to help you be more productive regardless of the complexity of your projects. If you're a team lead/admin, we'll also showcase some of the features to help you onboard your teams onto Codespaces easily!
A
A
A
But
as
always,
I
like
to
introduce
my
guest
with
a
couple
of
interesting
tidbits,
so
just
to
kind
of
break
down
who
she
is
as
a
person
she's,
a
huge
hiker.
She
really
likes
to
hike
and
so
far
her
favorite
trail
has
been
the
beehive
trail
in
banff.
So
if
you
have
any
interesting
ideas
on
where
should
she
should
take
her
hiking
boots?
Next,
just
throw
those
in
chat
and
she'll
probably
check
them
out
at
some
point.
A
She
currently
doesn't
own
any
animals,
but
if
she
were
to
own
some
dogs,
which
would
be
her
preferred
route,
she's
she's,
looking
at
either
golden
dough
golden
doodles
or
beagles,
I
also
like
to
ask
people
what
they've
recently
purchased
and
she
she
did
not
fail
to
deliver.
Sephora
has
recently
stayed
claimed
to
a
decent
chunk
of
her
paycheck
at
a
recent
sale,
and
then
she
also
just
bought
a
table.
A
Fan
she's
got
some
family
visiting
and
they
needed
some
white
noise,
so
table
fan
in
the
checkout
and
then
finally,
she
wanted
a
she
needs,
an
action
that
would
help
to
help
her
get
ready
and
bring
them
to
the
gym.
She
enjoys
going
to
the
gym
and
working
out.
It's
just
that
kind
of
step
of
like
getting
ready
and
getting
there.
B
Awesome,
thank
you
so
much
hey
everyone
yeah.
First
of
all,
I
want
to
thank
beer
of
edu
for
such
an
awesome
introduction.
I
don't
think
I've
been
introduced
that
way
before.
So
thanks
for
that,
my
name
is
tanway
and
I
am
a
product
manager
on
github,
good
spaces.
I've
been
with
github
for
about
a
year
now
I
would
say,
and
I'm
super
passionate
about
you
know
understanding
and
addressing
problems
that
developers
experience
in
their
day-to-day.
B
B
So
let
me
first,
you
know,
share
what
github
code
spaces
are
at
a
very
high
level,
and
then
I'm
going
to
jump
into
some
cool
demos
to
actually
show
you
how
it
works
and
then
we'll
talk
about
some
of
the
new
and
exciting
features
that
we
have
recently
added
support
for,
based
on
the
awesome
feedback
that
all
of
you
share
with
us
all
right.
So
what
are
code
spaces?
B
You
can
think
of
code
spaces
at
a
high
level
as
instant
cloud-powered
development
environments
that
are
completely
customized
for
a
particular
project
that
you're
working
on.
So
as
a
dev,
when
you,
you
know,
want
to
start
working
on
a
project,
you
don't
need
to
necessarily
think
about.
What's
the
right
container
image
or
how
do
I
set
up
my
laptop
for
this
project
to
work
or
what
other
tools
and
scripts
I
should
install
for
my
environment
to
be
up
and
running,
we
take
care
of
all
of
that
fun
stuff
for
you
now.
B
Not
only
are
these
environments
highly
customizable,
you
can
also
personalize
them
for
the
needs
of
you
as
a
developer.
So
let's
say
you
enjoy
working
with
a
certain
set
of
extensions
or
font
sizes,
or
you
know,
environments
that
feel
like
home
to
you.
Your
code
spaces
can
be
configured
to
inherit
those
settings
so
that
no
matter
which
project
you
work
on
your
code.
Space
always
feels
like
local
feels
like
home,
and
you
can
continue
working
on
it
and
then
last,
but
not
the
least.
The
codespace
is
a
managed
service
right.
B
B
Like
you
can
scroll
down
and
see
the
readme
you
can
see
you
know
what
packages
it
has,
what
languages
it
is
used
to
create
and
really
our
goal
is
to
make
sure
that
you
can
very
easily
and
meaningfully
absorb
this
rich
information
without
having
to
think
about
how
do
I
get
started
with
this
project
right
so
to
create
a
code
space?
All
you
got
to
do
is
go
to
this
green
code
button
here
and
click.
The
button
create
me
a
code
space
right.
So
what
we
do
here
is
when
the
code
space
gets
created.
B
You
can
understand
how
your
project
works.
I
actually
created
the
code
space
on
the
main
branch.
So
I'm
going
to,
you
know,
create
a
new
branch
here.
Let's
just
call
it
the
test
branch-
and
one
thing
I
really
like
to
call
out
specifically,
is
that
codespaces
is
more
than
just
an
editor.
Yes,
you
can
edit
your
code.
You
can
navigate
and
learn
more
about
the
project,
but
at
the
same
time
you
also
have
a
terminal
here
right,
so
you
can
actually
run
your
code.
B
B
B
So
if
you
saw
you
know
as
a
dev
getting
started
on
a
project,
all
I
actually
had
to
do
was
click
on
a
button,
and
then
I
was
dropped
into
this
environment.
Where
I
could
just
run
my
code
and
that's
it.
I
had
my
application
up
and
running.
There
are
other
things
I
can
do
with
my
code
space
as
well.
Now,
for
example,
you
know
if
I
head
over
to
the
view
section
here
and
go
to
the
index
dot.
B
Egs-
and
let's
say
you
know,
I
want
to
call
haikus
for
june
a
bit
more
like
make
it
better
right,
like
let
me
go
here
and
actually
add
a
few
more
exclamations
and
a
heart,
and
if
you
see
here
it
re-runs
my
application
and
I
can
actually
click
on
it
and
see
the
changes
happen
in
real
time.
So,
as
a
dev,
let's
say
I'm
developing
a
feature.
I'm
fixing
a
bug.
As
I
make
changes
to
my
code.
B
B
You
can
simply
head
over
to
source
control
right
in
the
context
of
this
code
space
and
either
commit
those
changes
directly
or
create
a
pull
request
right
from
the
context
of
this
environment
and
and
make
sure
that
you
can
submit
the
changes
you
made
to
this
particular
branch
into
into
the
main
branch
of
your
repository,
so
think
of
these
code
spaces
of
these
environments
to
be
super
ephemeral,
meaning
when
you
want
to
do
a
task,
whether
it's
working
on
a
feature
fixing
a
bug
reviewing
a
pr.
You
can
very
quickly
produce
dev
environment.
B
That
has
everything
you
need
to
get
started
on
your
task
and
once
you're
done
with
it,
you
can
simply
commit
the
changes
or
submit
the
pr
and
be
done
with
it.
So
the
whole
end
to
end
process
is
basically
taken
care
for
you
in
this
code
space
now
now
that
you
know
we've
seen
at
a
high
level
how
you
can
get
started
with
code
spaces,
I
I
did
mention
a
custom
configuration
and
highly
customized
environments
a
few
times
right.
So
let's
really
talk
about
how
this
particular
code
space
can
be
customized.
B
The
reason
for
that
is,
once
you
define
this
dev
container
json
in
the
the
root
of
this
particular
repository
every
code,
space,
every
developer,
who
comes
and
creates
a
code
space
off
of
this
particular
repo
will
have
the
same
environment,
and
hence
they
will
have
this
consistent
and
standard
experience
that
teams
can
work
off
of
now.
Let
me
quickly
show
you
what
that
dev
container
json
looks
like
so
that
you
know
when
you
create
your
own,
you,
you
have
some
idea
on
what
are
the
main
things
to
include
in
there.
B
The
first
thing
that
I'll
definitely
call
out
is
the
the
container
image
right
now
we're
actually
going
to
create
a
container
when
you
create
a
code
space.
So
the
main
thing
that
we
need
from
you
is
sort
of
the
base
image
which
is
required
to
create
this
container.
There
are
a
few
ways
you
can
specify
that
you
can
either
give
us
a
docker
compose
yaml
which
refers
to
a
docker
file.
B
You
can
point
to
an
existing
docker
file
that
tells
us
how
to
assemble
your
container
image,
or
you
can
even
point
to
an
existing
image
which
either
lives
in
your
github
container
registry
or
even
a
private
image
registry
that
we
simply
pull
from
and
use
that
to
create
your
container.
So
that's
sort
of
the
basis
of
your
container.
B
On
top
of
that,
there
are
a
few
other
things.
You
can
do
first
think
look
at
the
post
create
command
here,
so
think
of
the
post
create
command
as
a
set
of
commands
that
you
want
to
be
installed
automatically
every
time
a
codespace
is
created,
for
example,
in
this
case
it
was
a
node
application
right,
so
npm
install
is
a
very
obvious
command
that
every
dev
has
to
run
for
this
environment
to
work
as
expected.
B
So,
instead
of
me
having
my
devs
to
install
this
every
single
time,
I'm
just
going
to
put
it
in
my
dev
container
json
and
every
time
they
create
the
code
space
npm
install
is
just
going
to
be
run
for
them.
Similarly,
if
there
are
a
bunch
of
visual
studio
code,
extensions
that
you
think
work
well
for
the
entire
team,
just
put
them
in
here,
so
that
your
devs
don't
have
to
install
those
extensions
every
time
they
create
a
code
space
and
last,
but
not
the
least
port
forwarding.
B
So
that
was
a
quick
overview
on
what
a
dev
container
json
could
look
like,
like
I
said,
there's
much
more.
You
can
do
with
these
custom
configurations
and
we'd,
be
here
all
day.
If
you
know
I
had
to
go
over
each
of
those,
but
we
have
extensive
documentation
to
help
you.
You
know
explore
further
and
create
your
own
own
configurations,
all
right.
So
now
that
you
know
we've
spoken
about
how
you
can
create
a
code
space,
what
a
dev
container
configuration
is.
B
The
next
thing
you
might
be
wondering
is
on
day
one
I'm
not
going
to
have
this
configuration
right.
How
do
I
actually
go
about
creating
this
custom
configuration
so
that
I
can
provide
the
standardized
experience
for
my
team
so
for
that
I'm
actually
going
to
head
over
to
another
codespace
here,
and
in
this
case
this
codespace
is,
does
not
have
a
custom
configuration
and
the
and
the
scenario
to
think
about
in
this
case
is
you
are
trying
code
spaces
on
day.
B
One
right,
you,
you
don't
know
what
code
spaces
are,
so
you
obviously
don't
know
how
to
create
a
container
configuration.
So
in
such
instances
on
day
one
we
actually
create
a
code
space
using
a
default
codespaces
image
or
a
default
container
image.
That's
hosted
and
managed
by
the
github
service
for
you
to
get
up
and
running
with
codespaces
right
and
a
great
way
to
identify
that
is
we
actually
tell
you
that
we
tell
you
hey
you're
on
a
default
image.
This
image
includes
a
bunch
of
runtimes
tools
such
as
python,
node
docker.
B
That
sort
of
is
a
catch
all
scenario,
if
you
will
to
drop
you
into
an
environment,
to
quickly
get
you
up
and
running
on
day,
0
or
day
1..
Of
course,
in
some
scenarios
you
might
choose
to
continue
using
our
default
image,
but
you
have
to
remember
that
it's
bulky
you
have
no
control
over.
You
know
how
you
want
to
customize
it.
B
So
if
you
have
a
specific
flavor
of
the
configuration
that
you
want
to
enable
for
your
team,
we
highly
recommend
creating
your
own
dev
container
configurations
so
to
create
that
the
the
first
step
when
you're
you
know
dropped
into
this
code,
space
is
to
hit
ctrl
shift
p
on
your
keyboard.
Alternatively,
you
can
also
click
on
this
code.
Spaces
option
on
the
bottom
left
corner
of
the
screen
and
then
look
for
the
add
development
container
configuration
files.
B
So
this
command
basically
provides
you
with
a
list
of
pre-made
custom,
dev
container
templates
that
you
can
quickly
get
started
with
so
the
idea
here
is,
we
don't
want
you
to
spend
your
time
writing
the
dev
container
from
scratch.
So
we
give
you
a
list
of
pre-made
template
configurations
that
make
your
life
easy
right.
The
other
cool
bonus
on
top
of
that
is
that
this
list
you
see
here
is
actually
shown
based
on
the
type
of
project
that
you
have.
B
So
in
this
case,
this
is
a
sample
javascript
codespace
that
I
have
it's
a
javascript
app.
If
you
will
a
bunch
of
javascript
files
that
you
see
here.
So
if
you
see
node.js,
node.js
and
mongodb
are
sort
of
the
first
recommendations
in
this
in
this
list.
Here,
of
course,
if
you
don't
like
any
of
these,
you
can
click
on
show
all
definitions,
and
that
should
give
you
a
wide
variety
of
container
configurations
to
select
from,
but
that's
a
nice
way
for
us
to
guide
you
in
the
right
direction.
B
Now,
for
the
purpose
of
this
demo,
I'm
just
gonna
select
the
debian
template,
I'm
gonna
select
the
default
debian
version,
and
next
up,
you
can
select
a
set
of
dev
container
features
to
install
now
think
of
dev
container
features
as
additional
scripts
that
you
can
use
to
further
customize
your
dev
container
configuration.
If
you
will
so
things
like
you
know,
adding
let's
say,
go
or
I
want
to
have
the
azure
cli
as
a
part
of
my
container
configuration,
you
can
simply
check
those
boxes
and
hit.
B
Ok,
it's
asking
me
to
select
the
go
version.
I'm
just
going
to
go
for
the
latest
version
here
and
after
I
hit
ok,
if
you
see
here,
we
go
ahead
on
the
left
panel.
We
go
create
a
dev
container
folder
for
you.
We
create
a
corresponding
dev
container
json
and
a
corresponding
docker
file
with
an
image
source
from
the
microsoft
container
registry.
B
So
the
the
process
of
adding
the
dev
container
is
pretty
straightforward
for
you
and
from
this
point
on,
you
can
actually
make
the
changes
that
are
required
and
then
apply
the
step
container,
dot,
json
change
to
your
code
space.
This
step
is
extremely
important
because,
if
you
see
here,
even
though
I
added
the
def
container
json
to
my
code
space,
currently
it's
not
applied
right.
It
still
says
I'm
on
the
default
image.
So
to
apply
the
step
container
configuration
to
the
code
space.
B
You
would
hit
ctrl
shift
p
again,
which
opens
up
the
command
palette,
and
this
time
you
would
look
for
the
rebuild
container
command.
So
I'm
not
going
to
rebuild
for
the
purpose
of
time,
but
what
rebuild
essentially
does?
Is
it
recreates
this
code
space?
Now
this
time
around,
it
actually
detects
the
present
presence
of
that
dev
container
configuration
and
we're
going
to
create
your
container
using
that
configuration,
as
opposed
to
the
default
image
that
we
were
using
previously,
and
the
awesome
part
about
this
is
that
you
can
keep
doing
this
right.
B
You
can
rebuild
make
some
changes,
maybe
add
some
extensions
rebuild
again
iterate
on
your
configuration
configuration
as
much
as
you'd
like
and
once
you're
satisfied
with
your
dev
container
configuration
you
can
head
over
back
to
source
control
and
basically
create
a
pull
request
and
merge
this
dev
container
into
your
into
the
root
of
your
repository.
So
once
it
is
actually
committed
into
your
source
code,
every
codespace
from
there
on
will
use
the
custom
configuration
that
you
created
as
opposed
to
the
default
configuration.
B
So
this
is
a
great
way
for
you
to
sort
of
you
know,
set
up
code
spaces,
perhaps
you're
a
team
lead
a
devops
engineer,
and
you
really
want
to
standardize
and
streamline
the
entire
development
process
for
your
team
head
over
to
your
repository.
Follow
these
steps-
and
you
know,
add
a
def
container
so
that
all
of
the
team
members
you
know
working
on
your
project
will
have
a
very
consistent
and
standard
environment
to
work
on
all
right,
so
that
was
sort
of
a
quick
rundown
on
a
bunch
of
things.
B
You
can
do
right
like
right
from
creating
a
codespace
to
configuring
it
and
setting
it
up.
For
your
repository
now,
let's
talk
about.
What's
what
are
some
of
the
new
things
that
we
we've
released
recently
for
codespaces
now,
one
of
my
primary
goals
is
to
really
ensure
that
organizations
and
teams
within
organizations
have
everything
they
need
to
be
successful
with
code
spaces
as
they
scale
up
and
adopt
and
add
more
users
to
to
use
code
spaces
and
sort
of
when
we
started
out
the
primary
project.
Type
that
we
supported,
or
we
assumed
was.
B
B
Typically,
we've
seen
microservices
come
up
very
often,
and
previously
this
used
to
require
the
developer,
to
create
a
pack
token
grant
that
back
token
access
to
the
additional
repositories
that
this
code
space
needs
to
access
and
then
manage
that
packed
token
over
time.
But,
hey,
that's,
that's
no
more
needed.
Now.
We
actually
released
support
for
a
particular
setting
in
your
dev
container
config,
so
it's
called
customizations
where
you
can
actually
tell
us
in
the
custom
configuration
itself
as
to
which
other
repositories
need
to
be
accessed
from
this
code
space.
B
So
in
this
case
I
can
say,
bookish,
potato
musical
journey
and
all
other
repos
in
bookish
potato
and
also
specify
what
level
of
permissions
are
needed
right
like
for
the
musical
journey
repo.
I
need
right
permissions
for
everything
else.
I
basically
need
read
permission,
so
you
can
tell
us
what
level
of
provisions
and
which
repositories
you
need
to
access
and
then,
when
a
developer
creates
a
code
space,
we
show
them
a
nice
ui
that
tells
them
hey
your
code.
Space
is
requesting
permissions
for
these
repositories.
B
B
So
if
you
are
working
on
a
monorepo
and
your
team
lead
has
configured
these
configurations,
then
all
you
got
to
do
is
pick
the
right,
one
that
you
need
and
then
you'll
be
dropped
into
a
very
customized
environment
with
the
right
permission
sets
with
the
right
scripts.
For
that
specific
application
inside
of
your
monorepo
awesome,
so
that
was
sort
of
the
first
area
in
terms
of
enabling
teams
to
work
with
code
spaces
on
additional
project
types.
B
B
You
know
projects
with
thousands
of
lines
of
code,
maybe
a
bunch
of
steps
or
the
build
times
or
post
create
commands
that
take
a
very,
very
long
time
to
execute
and
in
such
cases
the
creation
of
the
code
space
definitely
slows
down,
and
we
don't
want
you
to
be
staring
at
your
screen
when
your
code
space
is
being
created
for
huge
amounts
of
time
and
that's
where
pre-builds
enter
right.
So
what
privileges
do
is
they
actually
speed
up
the
creation
of
your
code
spaces
specifically
for
complex
projects?
B
Awesome.
The
other
area
of
feedback
that
we
hear
quite
often
is
policies.
Now,
as
you
know,
organizations
start
adopting
code
spaces.
One
of
the
things
that
admins
need
is
the
ability
to
manage
and
control
the
usage
of
code
spaces,
and
this
is
primarily
for
like
controlling
costs,
making
sure
code
spaces
are
compliant
and
secure
as
more
and
more
teams
start
using
it.
There
are
a
few
policies
that
we've
added
and
we
continue
to
work
on
more.
So
any
feedback
here
is
very
much
appreciated.
B
Specifically,
you
know
to
ensure
that
developers
don't
accidentally
mark
a
port
public
forget
about
it
and
then
you
know,
company
resources
could
potentially
be
accessible
to
to
anyone,
so
you
can
simply
disable
that
option
altogether
now.
So
those
are
some
of
the
policies
that
are
available
and
we're
working
on
some
more
to
help
ensure
you
can
continue
managing
your
code
spaces
and
then
the
last
thing
I'll
talk
about
is
private
networking.
So
this
is
basically
the
ability
to
access,
on-prem
or
vpn
based
resources
from
a
code
space.
B
So
this
solution
currently
is
in
private
beta
and
we
are
actually
calling
for
anyone
who
wants
to
try
it
to
reach
out
to
us
at
codespaces
github.com,
so
that
we
can
share
next
steps
with
you.
If
this
is
a
problem
that
you're
experiencing
today,
we'd
love
to
hear
if
this
solution
addresses
the
need-
and
we
can
iterate
and
build
the
right
feature
for
you
awesome.
So
that
was
a
lot
of
information,
and
I
know
that
I
it's
it's.
B
We
have
a
discussions
forum
in
case
you
have
feedback,
feature
requests,
pain,
points
that
you
want
to
share
with
us,
and
then
we
also
have
a
public
roadmap
in
case
you're
curious
about
what's
upcoming
for
codespaces.
So
I
think
all
that's
left.
After
all,
this
is
to
for
you
to
give
code
spaces
a
try
and
let
us
know
what
you
think
and
share
your
feedback
with
us.
So
thanks
thanks
for
listening
in.
A
Yeah,
thank
you
so
much
for
joining
us
today.
That
was
really
awesome
to
kind
of
like
break
down
all
the
different
things
that
you
like
how
to
get
started
with
code
spaces
and
then
like
what
you
can
do
with
it
and
then
the
kind
of
like
where
we're
going
with
it.
It's
a
really
cool
tool
to
play
around
with.
A
I
don't
get
to
play
play
around
with
it
as
much
as
I'd
like,
but
I
definitely
get
to
fiddle
with
it
from
time
to
time,
but
yeah,
that's
everything
from
us
here
at
github.
I
wanted
to
again
thank
you
very
much
for
joining
tamai
thanks
for
running
down
code
spaces
again
that
was
awesome
and
then
for
everyone
that
tuned
in.
Thank
you
very
much
for
joining
the
30
minutes
to
merge
session.
A
We
typically
try
to
give
you
like
30
minutes
of
content
about
git
or
github,
and
you
can
always
find
us
on
the
github
community
site,
which
is
kind
of
where
this
video
series
or
this
this
live
stream
kind
of
came
from,
and
that
kind
of
give
us
ideas
on
what
you
want
to
hear
about
the
next
time
we
pop
in
on
your
favorite
social
media,
but
yeah.
So
so,
thank
you
very
much.
Everyone
have
a
great
time
have
a
great
day
and
hope.