►
From YouTube: GitHub Universe 2021: Day 1
Description
Join us as we explore the future of software.
Join our main broadcast to catch the GitHub keynote and talks from GitHub developers, product pros and open source peers.
https://githubuniverse.com
A
A
A
A
A
A
A
A
A
A
A
A
A
A
C
Welcome
to
github
universe,
it
has
been
an
incredible
year.
Every
day
we
come
to
work
to
build
the
best
developer
experiences
in
the
world
for
you,
but
then
we're
lucky
enough
that
we
get
to
use
them
too,
and
so,
whether
it's
a
really
big,
innovative
new
product,
like
you,
know,
co-pilot
or
get
up
code
spaces
or
whether
it's
just
making
the
things
that
you
use
every
day,
a
little
bit
better.
D
D
Let
me
message
corey
real,
quick
and
see
if
he's
able
to
help
out
hey
court,
you
have
a
second
chat
about
the
demo
hey
april.
Did
you
get
my
message?
Oh
okay,
so
I
was
thinking
the
best
way
to
demo
code.
Spaces
is
if
we
do
it
together,.
D
E
D
Awesome:
okay:
this
is
a
code
space
running
github.com.
My
team
uses
a
pre-configured
environment
specific
to
github.com
and
it
all
starts
with
this
file
the
dev
container,
located
at
the
root
of
the
repository.
It's
config
is
code
that
drives
code
space
customization.
So
when
any
team
member
creates
a
code
space,
they
benefit
from
a
base
image.
Minimum
vm
requirements,
shared
vs
code,
extensions,
automatically
forwarded
ports
and
more,
but
we
all
have
our
own
unique
preferences.
So
codespace
also
allows
me
to
customize
my
environment
to
fit
my
exact
needs.
D
My
github.files
repo
gives
me
my
tmux
bindings
and
settingsync
installs
my
favorite
extensions,
and
ensures
that
I'm
always
in
dark
mode.
We're
looking
at
github.com
running
in
my
code,
space
in
the
cloud
and
the
fan
on
my
local
computer
is
quiet
and
with
one
small
change
reload
the
page,
and
this
becomes
where
you
build
software
starting
today,
I
can
securely
share
access
to
ports.
In
my
code,
space
with
members
of
my
organization
now
I
can
quickly
share
my
code.
D
Ssh
access,
when
my
team
needs
to
start
a
new
feature,
it
doesn't
matter
what
device
they
use.
They
connect
to
a
machine
with
32
cores
and
64
gigs
of
ram
with
code
spaces.
We
sped
up
our
development
interloop
and
now
you
can
too
code.
Spaces
is
available
for
teams
and
organizations.
Right
now,
and
in
case
you
missed
it.
We
introduced
a
web
editor
for
everyone,
just
visit
any
repo
and
hit
the
dot
key.
F
F
That's
where
github
copilot
comes
in
our
aipar
programmer
built
to
give
suggestions
to
finish
lines
of
code
or
even
entire
functions.
All
within
your
editor,
when
we
first
open
the
technical
preview
in
july,
we
start
off
with
the
most
popular
editor
visual
studio
code,
we're
working
on
expanding
support
to
visual
studio
them
and
intellij.
F
Here,
let
me
show
you
so
here,
I'm
using
copilot
in
pycharm
and
working
on
a
python
project.
You
can
see.
As
I
start
a
new
function.
Copilot
shows
me
a
suggestion
to
complete
my
function
and
it's
exactly
what
I
needed
since
we
started
30
of
all
code
written
by
early
adopters,
come
from
co-pilot
suggestions,
co-pilot
works
best
with
python,
javascript,
typescript,
ruby
and
go
and
we're
also
going
to
support
languages.
F
G
G
Now
that
we
have
the
breakdown,
you
can
see
that
the
issue
generates
a
progress
indicator
at
the
top.
If
we
mark
an
item
as
completed
the
progress
indicator,
automatically
updates,
not
only
that
you
can
convert
any
of
the
task
list
items
into
issues,
creating
a
work
hierarchy
to
help
you
keep
contacts,
then,
as
you
complete
work,
the
hierarchy
automatically
updates
for
you.
How
sweet
is
that?
Sometimes
we
need
to
plan
and
track
a
bigger
body
of
work.
G
That's
why
we
have
improved
projects
to
give
you
a
live,
canvas
to
filter
sort,
group
issues
and
pull
requests.
Octory
k
wants
to
launch
a
new
game.
Turkey
invaders,
let's
track
it
with
a
new
project.
This
starts
you
with
a
spreadsheet
like
canvas
optimized
for
information
density
and
customization.
G
Next,
we
add
custom
fields
for
each
area.
There
are
five
core
field
types
text
number
date:
single
select
and
iteration
I'll
use
them
so
I'll,
add
an
area
single
select
releases
and
also
customize
the
status
field.
I'll
enter
the
work
for
the
prototype
as
draft
items
and
convert
them
into
issues
very
similar
to
how
we
did
it
in
task
lists
then
fill
out
the
rest
of
the
metadata.
G
This
is
looking
great
now
fast
forward.
More
work
has
been
done
and
I
can
start
customizing
views
for
a
specific
perspective,
let's
name
the
first
one,
scope
and
group
them
by
our
releases,
so
I'm
going
to
hit
command
k
and
gbr
and
now
is
grouped
by
releases
next,
I'm
creating
a
second
view
for
our
standup,
a
board
that
includes
some
of
these
custom
fields,
same
data,
just
a
different
visualization.
G
In
the
third
view,
we
will
filter
to
the
core
game
areas:
lots
of
power
on
the
filters
that
we
have
included
things
like
this,
so
I
could
actually
look
for
an
issue
or
put
requests
empty
fields
and
even
exclusion.
We
also
want
to
set
up
a
couple
of
workflows
to
make
our
lives
easier.
Let's
make
this
items
close,
set
the
status
to
done,
and
this
is
looking
great.
G
I
Whoa,
I
was
just
checking
out
those
new
github
issues
features
anyway
at
github.
We
want
to
make
sure
that
every
developer
has
what
they
need
to
succeed
at
any
scale.
We
just
launched
enterprise
server
3.2,
which
contained
more
than
70
brand
new
features
that
includes
powerful
new
continuous
deployment
features
provided
by
our
automation
platform.
Github
actions,
our
new
workflow
visualizer,
gives
you
the
ability
to
target
jobs
to
environments,
and
you
can
now
deploy
to
staging
and
then
production
all
with
one
workflow.
I
I
But
what
about
your
company's
other
secrets,
tokens
and
credentials
leak
credentials
are
one
of
the
most
commonly
exploited
application.
Security
risks,
github
secret
scanning
scans,
all
of
your
code
to
find
them
before
you
deploy
and
now
in
enterprise
server
3.2,
you
can
scan
for
your
own
company's
credentials
using
custom
patterns.
Those
are
secret
scanning
patterns.
You
define,
in
addition
to
more
than
100
token
patents
from
cloud
and
service
providers
that
we
include
automatically
now.
I
Let's
talk
about
code
scanning,
our
semantic
analysis,
engine
that
keeps
vulnerabilities
out
of
your
code,
we've
added
new
severity
labels
and
search
tools
to
make
it
easier
to
focus
on
the
most
important
vulnerabilities
to
you
and
your
team
and
we've
recently
added
support
for
scanning
ruby
as
well.
But
we
know
that
finding
these
vulnerabilities
isn't
enough.
J
Stop
playing
building
software
today
is
so
much
more
than
just
the
source
code.
That's
why
we're
working
alongside
creator,
communities
and
maintainers
to
build
tools
for
all
parts
of
this
process
take
get
up
discussions.
We've
worked
with
maintainers
to
improve
the
product,
and
now
we
have
some
new
features
to
power
up
your
communities.
J
Let's
start
with
discussions
labels
with
discussions,
labels
maintainers
can
now
keep
their
spaces
organized.
Here.
You
can
see
that
the
gatsby
community
is
using
labels
to
denote
topic
status
and
which
gatsby
release
the
discussion
falls
under
when
you're
following
a
forum
thread,
it
can
be
hard
to
keep
up
with
what
you've
already
read
versus
what
you
haven't
read.
Yet
this
happens
to
me
all
the
time,
but
with
this
new
discussions
feature,
you
can
jump
immediately
to
new
comments.
J
You
haven't
read
yet
you
can
also
see
unread
replies
to
keep
up
with
the
latest
and
this
next
one
is
one.
I'm
super
excited
about
later
this
year,
we'll
be
lighting
up
discussion
polls.
Creating
a
poll
is
simple
to
get
started.
Polls
will
help
maintainers
aggregate
feedback
from
their
community
and
base
product
decisions
on
that
feedback,
ultimately
allowing
them
to
feel
closer
to
the
thoughts
and
opinions
of
their
communities.
That
poll
is
fake.
J
Maintainers
do
all
of
this,
for
you
so
don't
forget
to
support
your
favorite
open
source
projects
and
maintainers
by
sponsoring
them
with
github
sponsors.
Here,
let
me
just
do
that
right
now,
the
world
of
software
runs
on
open
source
and
our
goal
is
to
empower
creator
communities
to
collaborate
together
and
do
their
best
work.
Yet.
K
Since
the
last
universe,
we've
shipped
more
than
20
000
improvements
to
github
releasing
multiple
times
every
day
we
made
it
easier
to
navigate
large
markdown
files
by
adding
a
table
of
contents,
and
we
added
buttons
to
copy
code
blocks
directly
from
readmes,
and
you
can
now
easily
copy
the
raw
contents
of
a
file.
We
added
a
fetch
button
to
the
repo
page
for
forks,
which
makes
it
so
much
simpler
to
stay
up
to
date,
which
changes
in
upstream,
open
source
projects.
K
K
K
K
The
last
feature
I
want
to
show
you
is
the
new
getup
command
palette.
You
know
how
he
can
hit
a
shortcut
in
your
editor
to
quickly
open
files
or
execute
comments.
K
We're
adding
the
same
to
github,
hit
command
k
if
you're
on
a
mac
or
ctrl
k
on
linux
or
windows
anywhere
in
the
github
web
interface,
and
you
will
bring
up
the
command
palette.
You
can
jump
between
your
organizations
and
repositories,
easily
navigate
to
any
file
issue,
pull
request
and
discussions
or
to
execute
commands
or
without
taking
your
fingers
off
the
keyboard.
C
L
This
is
our
sixth
github
universe
and
this
event
serves
as
a
place
where
developers
come
together
to
learn
about
building
the
future
of
software
from
the
people
who
are
creating
it
you're,
going
to
hear
from
a
wide
range
of
people,
including
open
source
developers
hubbers
as
well
as
get
up
customers,
and
you
hear
it
here-
live
from
our
beautifully
designed
and
recently
renovated
headquarters
here
in
san
francisco.
I
want
to
thank
all
of
the
wonderful
humans
that
have
made
this
event
possible.
But
most
of
all
I
want
to
thank
you
for
joining
us
here
today.
L
My
name
is
jared
mccree
and
I
am
one
half
of
this
dynamic
duo
that
graciously
serve
as
your
host
for
the
next
two
days.
I'm
a
staff
product
manager
here
at
github
and
focused
primarily
on
the
enterprise
needs
of
our
customers
and
I'm
joined
here
by
the
host.
That
always
brings
the
most
ms
lorena
mesa.
M
Thanks
jared,
I'm
really
pumped
to
be
here
with
you
too,
at
this
awesome
studio,
but
also
with
all
of
you
out
there
joining
us
from
your
home,
your
workplace
or
maybe
somewhere
out
there
on
the
go.
As
jared
said,
my
name
is
lorena
mesa
and
I
work
on
one
of
github's,
exciting
supply
chain
products,
dependency.
M
Graph,
don't
worry
if
you
haven't
heard
of
dependency
craft
before
you'll,
be
hearing
plenty
about
security
at
github
throughout
universe,
you'll
also
be
hearing
some
great
music
from
justine
and
r
tyler
who'll
be
starting
and
closing
our
live
broadcast
with
live
coded
art
and
sounds
make
sure
to
check
out
their
sets.
It's
going
to
be
a
great
time
now.
Let's
talk
about
that
keynote.
From
nat
and
friends,
we
heard
a
bit
from
allison
on
codespaces
b,
dougie
on
copilot,
mario
on
issues
and
maya
on
ghe,
we'll
be
exploring
these
themes
more
throughout
universe.
M
To
share
with
you.
How
we
here
at
github,
really
do
use
github
too
well
build
github,
something
I'm
really
looking
forward
to
is
the
deep
dive
page
bailey
will
be
taking
us
on
as
we
learn
about
the
ways
github
is
helping
build
the
next
generation
of
ai
code
assistants.
The
future
really
is
now
y'all.
What
are
some
things
you
all
are
looking
forward
to
at
universe?
Let
us
know
by
tweeting
us
with
github
universe
or
let
us
know
your
thoughts
and
comments
by
tagging.
L
So
universe,
2021
is
a
two-day
global
event
and
it's
a
little
bit
different
from
last
year.
Firstly,
if
you're
watching
this
live,
the
main
broadcast
is
broadcasted
and
translated
into
six
languages,
and
you
can
learn
more
by
clicking
on
that
faq
button
at
the
top.
Toolbar
second
is
to
choose
your
own
adventure
experience
where
we've
handed
the
wheel
over
to
you,
so
that
you
can
universe
the
way
you
want
a
universe.
L
This
is
our
main
broadcast
and
for
the
next
90
minutes
we'll
be
showing
you
curated
content
that
builds
on
what
nat
and
company
talked
about
in
the
keynote,
and
while
we'll
be
guiding
you
through
these
talks,
that's
not
the
only
way
you
can
access
them.
We
have
a
whole
library
of
on-demand
content
that
you
can
jump
into
at
any
time
by
going
to
githubuniverse.com.
L
This
is
where
you'll
be
able
to
see
a
replay
of
the
main
broadcast.
That's
happening
right
now,
shortly
after
we
wrap
for
today,
but
the
show
doesn't
stop
there
after
the
main
broadcast,
we'll
have
live
interactive
sessions,
including
workshops
and
q
and
a's
for
your
viewing
enjoyment.
Now
I
said
earlier,
universe
is
interactive.
Lorena,
would
you
please
tell
these
fine
people
how
that's
going
to
happen.
M
Well,
you
can
join
the
conversation
by
participating
in
discussions
to
participate.
You
will
need
a
github
account
to
sign
up
is
completely
free,
our
presenters
and
subject
area
experts
will
be
there
throughout
the
day.
So
please
bring
your
questions.
If
you
have
any,
we
are
here
to
help
you
find
those
answers.
There
will
also
be
live
interactive
sessions
that
start
shortly
after
this
broadcast
all
live
interactive
sessions
and
on-demand
content
can
be
found
at
githubuniverse.com.
M
On
the
upper
right
side,
you
will
need
a
logon
login
with
your
github
account
if
you
haven't
already.
Although
some
of
our
sessions
have
been
sold
out,
there
are
still
many
seats
available
in
many
of
the
sessions.
Once
you
register,
you
can
find
links
to
your
you
can
find
links
to
access
the
sessions
in
your
my
universe,
schedule
and
also
in
your
email,
a
reminder,
though,
that
space
is
limited.
So
please
do
sign
up
soon.
If
you
need
technical
help
during
the
live
streams
because
again
live
streams.
Please
reach
out
to
our
support
team.
L
All
right
folks,
it's
time
to
jump
into
our
first
session
of
the
day.
So
during
the
keynote
you
heard
about
code
spaces
and
how
one
of
the
main
goals
is
to
remove
barriers
to
entry
for
our
users
in
order
to
make
coding
as
inclusive
as
possible,
we
believe
in
this
mission
so
much
that
now
the
majority
of
github's
development
happens
through
codespaces
we're
joined
now
by
github
vp
of
engineering,
corey
wilkerson.
To
learn
more
about
that
journey,
and
our
first
session
called
moving
github's
development
to
code
spaces.
E
E
The
github.com
code
base
is
almost
14
years
old
when
the
first
commit
for
github.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.
E
E
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.
E
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.
Works
on
my
machine
is
a
meme
for
reason.
E
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
anytime.
This
is
a
huge
relief.
E
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.
E
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.
E
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.
E
E
E
E
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
codespace's
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.
E
On
the
back
of
this
momentum,
we
launched
code
spaces
to
github
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
codespaces
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.
E
N
Hi
everyone
I'm
bailey
now
that
corey
has
shown
you
the
inside
scoop
on
how
we
moved
github
development
to
codespaces.
You
might
be
asking
yourself:
how
do
I
get
set
up
with
my
own
projects
or,
if
you're
a
manager?
The
question
is
likely.
How
do
I
onboard
my
team,
luckily
for
you,
allison-
and
I
are
here
to
help
you
out.
O
Absolutely
we're
here
to
ensure
you
have
all
the
details.
You
need
to
start
working
with
code
spaces
now,
whether
that's
getting
your
theme
and
terminal
prompt,
just
right,
setting
cost
and
access
controls
for
your
organization
or
configuring,
your
team's
repository
for
one
click,
startup
bailey.
Where
do
you
want
to
start.
N
Since
containers
are
at
the
heart
of
code
spaces,
we
make
sure
that
you
can
reuse
all
of
your
existing
context.
Your
existing
docker
files,
docker
compose
files
and
lifecycle
scripts
can
all
be
referenced
from
within
the
devcontainer.json,
and
since
this
file
is
checked
in
with
your
source
code,
it
means
anyone
that
creates
a
code.
N
Space
from
this
repo
automatically
gets
a
really
standard
and
repeatable
experience,
and
I
personally
love
this
because
it
enables
everyone
to
just
get
started
really
fast
without
having
to
spare
a
second
thought
to
set
up
for
folks
that
are
new
to
the
team
or
the
project.
It's
really
as
simple
as
ensuring
they
have
access
to
the
right
repositories
and
then
they're
well
on
their
way
to
their
first
pr
with
code
spaces.
O
I
can't
agree
more
bailly,
you
know
codifying
your
configuration
is
really
key
to
a
great
experience.
We
provide
a
default
configuration
to
get
you
started,
but
it
contains
a
lot
and
we
are
constantly
updating
it
as
we
update
various
tools
and
runtimes
that
it
contains
by
specifying
your
own
dev
container
definition,
you
can
be
sure
that
each
code
space
you
create
for
a
given
repository
has
the
same
setup
no
surprises
here.
Unless
you
start
editing
things,
but
hopefully
that's
not
too
much
of
a
surprise.
O
Let's
go
ahead
and
dive
in
here
we've
got
a
sample
project
that
doesn't
have
a
dev
container
configuration
it's
on
our
default
image,
and
you
can
tell
that
because
we
say
it
right
here
in
the
terminal
in
the
welcome
mat,
as
well
as
the
lack
of
a
dev
container
folder
in
the
file
explorer.
The
great
news
is,
we
know
how
to
help
you
get
started,
because
we
have
lots
of
templates
available
to
you.
If
you
go
ahead
and
press
f1
or
control
shift
p
you'll
invoke
the
visual
studio
code
command
palette
from
there.
O
All
you
need
to
do
is
type
in
add
development
container
configuration
files.
Clearly
this
is
a
command
that
I
like
to
use
a
lot
and
hit
enter
from
here
will
bring
up
all
of
these
common
definitions
that
you
can
choose
from
we'll,
actually
look
at
your
project
and
figure
out.
If
there
are
some
templates
that
are
more
reasonable
to
suggest
than
others.
For
example,
we've
got
javascript
files
in
here,
and
so
we
actually
recommend
our
node
definitions
as
a
great
starting
place.
You
can
always
see
the
full
list
by
clicking
show
all
definitions.
O
Now
I
want
a
pretty
simple
definition
to
start,
so
I'm
going
to
go
ahead
and
select
debian
from
here,
it'll.
Ask
me
what
version
I'd
like
to
use,
I'm
going
to
go
ahead
and
choose
the
default,
and
finally,
it's
going
to
ask
which
features
I'd
like
to
install
features
are
commonly
used
tools
that
we
can
install
for
you
as
part
of
your
dev
container
configuration
so
that
you
don't
have
to
figure
out
how
to
install
things
like
the
github,
cli
or
maybe
docker
and
docker
support.
O
O
I've
got
a
docker
file
as
well,
and
there
you
go
a
dev
container
configuration
all
set
and
ready
for
you
to
actually
apply
these
changes
to
your
code
space.
You
can
go
ahead
and
invoke
the
visual
studio
code
command
palette,
one
more
time
and
type
in
rebuild
as
well.
If
you
make
any
changes
to
your
dev
container
configuration,
we
also
pop
up
a
toast
that
lets
you
know
and
allows
you
to
rebuild
right.
O
There
rebuild
allows
you
to
experiment
with
your
dev
container
configuration
as
much
as
you'd
like
without
pushing
changes
out
to
the
repository
that
might
mess
up
other
teammates.
Simply
edit.
Your
dev
container
rebuild
see
the
changes
and
figure
out.
If
you
like
them
and
don't
worry,
if
you
get
into
a
weird
spot,
you
can
always
delete
the
devcontainer.json
and
any
docker
files
hit
rebuild
and
start
from
scratch.
O
Let's
take
a
look
at
a
few
properties
that
are
really
important
to
your
overall
setup.
First,
the
image
property.
This
allows
you
to
easily
reference
an
image
from
any
registry
you'd
like
if
you're
already
storing
your
images
on
github
container
registry,
we've
recently
shipped
an
update
that
allows
you
to
reference
them
directly
from
thedevcontainer.json
without
any
extra
permissions
that
you
need
to
set.
It's
really
as
simple
as
ensuring
your
account
has
read
access
to
the
image
in
question
and
then
putting
the
link
right
here
in
the
image
properties
you're
all.
D
O
Go
no
hassle
needed
next.
We
have
extensions.
This
allows
you
to
install
the
set
of
visual
studio
code,
extensions
that
your
developers
need
to
be
productive
with
this
particular
project.
These
could
be
linters
specific
language,
support
collaboration
tools
and
so
much
more.
The
marketplace
is
really
at
your
disposal.
O
No
longer
will
developers
have
to
go
through
the
laundry
list
and
install
their
extensions
one
by
one.
We
take
care
of
all
of
that
for
you
as
part
of
creation.
Next
up
we
have
two
port,
specific
properties,
ford,
ports
and
port
attributes.
The
ford
ports
property
indicates
the
set
of
ports
that
we
should
forward
automatically
quite
intuitive.
I
know,
whereas
the
port
attributes
property
tells
us
specific
details
about
those
ports.
So,
for
example,
we
are
forwarding
port
3000
by
default.
O
We
are
labeling
it
as
application.
That's
our
front
end
application
on
auto
ford.
So
basically,
this
is
what
is
the
behavior
when
we
see
the
port
is
active
and
being
forwarded,
we're
going
to
go
ahead
and
open
the
browser
automatically.
You
can
also
specify
a
toast
that
you'd
like
to
notify
or
leave
it
silent.
If
you
prefer
more
of
a
focus
mode
and
finally,
the
protocol,
in
this
case
we're
using
https.
O
Finally,
we've
come
to
the
post
create
command
which
will
run
these
specified
commands
after
the
container
is
created.
This
is
a
great
place
to
kick
off
installing
dependencies
cloning,
other
repos
or
any
other
preparation
commands
you'd
normally
do
manually
as
part
of
project
setup,
and
this
is
just
one
of
several
lifecycle
hooks.
We
have
available
to
you
in
the
devcontainer.json
others
you
might
want
to
check
out
our
post
start
command
or
post
attach
command.
So
we
really
have
fine
level
granularity
for
you
to
figure
out
when
your
script
should
execute.
O
N
On
top
of
configuring
projects,
cost
control
is
another
huge
factor
for
people
considering
moving
their
development
to
the
cloud.
I
think
everyone
who
has
ever
run
cloud
compute
has
a
very
real
fear
of
waking
up
to
a
runaway
bill
for
thousands
of
dollars.
Thankfully,
we
have
built-in
features
and
explicit
policies
to
mitigate
all
of
that
stress
code.
Spaces
will
automatically
stop
running
after
30
minutes
of
inactivity
or
when
a
user
has
too
many
code.
Spaces
running
at
once
for
direct
control.
N
Administrators
can
also
set
spending
limits
for
their
team's
code,
spaces,
limit,
auric,
member
access
and
export
usage
data.
So
you
can
get
to
know
those
usage
patterns
code
spaces
are
also
cost
flexible
by
design.
So
you
can
select
exactly
how
much
power
you
need
in
your
machine
and
change
it
at
any
point.
N
So
you
can
power
up
for
those
high
intensity
operations
when
you
need
it
without
having
to
commit
to
32
cores
for
the
lifetime
of
your
code
space
and,
if
you're,
just
looking
to
make
a
quick
file
edit
review
a
pr
or
any
other
task
that
doesn't
require
compute.
Don't
forget
about
github.dev.
That's
our
editor
experience.
You
can
access
just
by
pressing
the
dot
key
on
any
repo
page.
The
web
editor
is
free
and
available
to
all
github
users
right
now.
O
All
right,
so
we've
covered
cost
controls
configuration
setup.
I
think
that
means
we
get
to
talk
about
personalization
now
bailey,
which
is
one
of
my
personal
favorites.
When
I
think
about
personalization.
The
first
thing
that
comes
to
mind
is
theming.
It
sort
of
feels
like
the
new
tabs
versus
spaces
debate
these
days
since
we're
leveraging
the
power
of
visual
studio
code
for
our
editor.
That
means
we
get
to
leverage
some
of
the
great
work
the
team
has
done
to
synchronize
settings
across
any
editor
instances.
First
off
you'll
need
to
ensure
that
settings
sync
is
on.
O
In
this
instance
of
my
code,
space
you'll
see
that
my
other
code,
space
synced
to
the
same
theme
that
I
set
in
my
universe,
demo,
what's
great
with
setting
sync-
is
that
it
applies
to
any
editor
instances
on
the
web
and
locally
that
have
settings
turned
on
and
even
better.
It's
not
just
your
theme
that
syncs
with
setting
sync,
you
can
go
ahead
and
also
sync
keyboard
shortcuts
extensions
snippets
so
that
anywhere
you're
using
visual
studio
code
feels
like
home.
N
Personalization
doesn't
just
stop
at
the
editor
level.
You
can
specify
shell
preferences
via
dot
files
just
be
sure
to
enable
them
in
the
code
spaces
settings
page
and
ensure
that
your
dot
files
repo,
is
public,
whether
you're
building
dot
files
from
scratch
or
updating
a
current
set
to
work
within
codespaces.
N
O
Finally,
we
know
that
personalizing,
your
workflow
also
means
enabling
you
to
use
the
tools
that
you're
already
productive
in
we'd
heard
from
many
customers,
both
internally
and
externally,
that
they
wanted
to
be
able
to
manage
and
work
with
their
code
spaces
right
from
the
command
line
and
while
that
wasn't
possible
at
the
time
it
is
now
with
our
new
github
cli
integration.
You
can
manage
and
connect
to
your
code
spaces
right
from
your
terminal.
O
Let's
take
a
look:
you
can
get
access
to
the
most
common
management
options
you
already
have
in
the
web
or
through
the
visual
studio
code.
Extension
such
as
creating
deleting
and
listing
your
code
spaces,
but
the
one
we're
really
excited
about
is
this
last
one
ssh
support,
while
some
dedicated
users
found
workarounds
in
the
past
to
enable
ssh.
O
This
always
involved
some
initial
setup,
either
through
the
web
or
visual
studio
code,
but
we've
now
automated
all
of
that
setup
within
the
ssh
command.
It'll
go
ahead
and
start
up
connect
me
and
then
we
are
right
here
in
the
code
space
that
I
just
created
now
we're
connected
and
working
in
this
code
space
all
without
ever
leaving
our
terminal.
N
L
You
had
to
get
your
laptop,
didn't
get
the
appropriate
internal
approvals
then
get
your
ide
set
up
and
realize
you
still
didn't,
have
the
appropriate
approvals,
and
just
cried.
I
mean
the
list
goes
on
with
code
spaces
developers
are
able
to
get
started
so
much
faster
and
just
as
a
reminder,
code
spaces
is
available
right
now
for
organizations
and
soon
we'll
be
providing
support
for
individuals.
L
L
Also,
you
can
connect
with
us
by
tweeting
at
us
with
the
github
universe
and
we'll
be
pulling
your
comments
in
throughout
the
live
broadcast
like
this
one
and
I'm
going
to
butcher.
This
handle
at
p
in
sargewet,
says
you're
right
nat.
What
a
year
at
github
with
co-pilot
and
code
spaces,
they
are
game.
Changers
of
the
developer.
Experience
hey!
I
didn't!
I
did
not
manage
my
snacking
as
you
did
now,
I'm
hungry.
L
L
G
L
G
Well,
github
issues
is
used
by
millions
daily,
and
you
know
it's
it's
very
simple,
it's
very
fast,
but
because
of
that,
it's
actually
really
loved
by
developers.
At
the
same
time
when
we
meet
with
customers,
they
let
us
know
three
core
problems
are
happening.
G
Number
one
is
we
lack
custom
fields
so
something
as
simple
as
hey?
I
want
to
just
add
a
priority.
I
want
to
end
up,
becomes
an
exercise
in
label
hacking
more
or
less
number
two.
It's
really
really
hard
to
understand
at
times
what
a
team
is
doing,
what
a
set
of
teams,
so
we
don't
scale
very
well
on
that
end
and
number
three
was
hierarchy,
so
we
kind
of
listened
to
that
and
we
really
set
out
to
build.
You
know,
project
planning
for
developers
and
really
make
github
issues
a
lot
more
powerful.
H
G
So
you
you
want
me
just
to
show
you
a
couple
of
things.
No,
I
would
love
to
show
you
all
right.
Let's,
let's
do
it,
then
let's
do
it.
So
I
am
here
and
the
first
thing
I'm
going
to
kind
of
go
through
the
basics.
First
of
it
and
then
we'll
get
into
like
you
know
at
scale
and
really
those
kind
of
those
questions,
maybe
jump
in
so
here
it
is
it's
at
the
organization
level.
This
is
octa
academy.
G
You
saw
that
in
the
keynote
most
probably
and
what
you
get
is
this
project's
beta.
You
can
start
a
new
project
just
by
doing
this,
I'm
just
going
to
go
into
the
one
you
saw
in
our
target
invaders.
Remember
so,
and
here
it
is
so.
This
is
all
the
work
that
the
orthokit
invaders
are
doing.
We
have
these
custom
fields
and
there
are
really,
if
I
go
and
say
new
field
here,
you're
going
to
see
five
types
of
them
text
number,
so
you
use
number
for
estimates
as
an
example
a
date.
G
So
if
you
have
a
due
date
on
something
you
could
also
utilize
it
for
that
single
select
are
far.
You
know
during
the
actual
private
beta,
that's
the
one
that
people
use
the
most
and
then
we
just
recently
launched
in
the
private
beta
iteration.
So
if
you
follow
the
change
log,
you
probably
saw
it
right
there.
So
in
this
case
we
have
said
I'm
just
going
to
go
into
a
settings
really
quick
and
you
can
see.
I
have
a
lot
of
areas:
producers,
engine
r
game,
loop
website
platform.
G
I
have
releases
like
prototype
alpha
and
beta,
and
you
know
this
team
operating
cycles,
so
they
also
have
a
couple
of
cycles
right
now,
they're
in
cycle
two
or
iteration-
two.
So
just
going
back
to
this,
so
not
only
do
we
have
custom
fields
and
we
kind
of
allow
you
to
grow
with
that.
We
also
have
the
ability
to
just
put
that
in
a
table
and
like
the
information
density
of
that
is,
is
really
a
standard
right
like
so
I
don't
have
to
have
this
spreadsheet.
G
That
always
has
to
be
refreshing
all
the
time
no
need
for
that.
You
just
can
do
a
table
view
right
here,
not
only
that
the
same
data,
you
could
actually
visualize
it
too
in
a
board
view,
which
is
one
of
the
things
that
we
saw,
so
I
just
can
go
over
here
and
instead
of
stamped
up
this
way,
I
just
say
board
and
I'm
going
to
add
a
couple
of
things
over
here.
G
So
maybe,
let's
add
the
releases
and
the
area,
and
now
we
have
that
I'm
gonna
save
the
view
too,
and
this
is
one
of
our
most
popular
features
as
well.
So
now
table
view
great
amazing
density
boards.
Just
like
that
and
look
how
fast
this
is
to
actually
switch.
This
is
live
right.
This
is
live.
You
know
we're
not.
You
know
we're
not
actually
doing
anything
here.
So
another
thing
that
was
really
great,
that
we
kind
of
showed
is
the
ability
to
group
by
the
data.
G
So
this
is
good,
but
what
I
really
want
to
do
is
mainly
see
it,
maybe
by
let's
say
releases
and
now
I
can
see
everything
that
got
done
in
prototype
everything
that
is
planned
for
alpha
and
everything
that
is
applying
for
for
data.
I
could
even
kind
of
rank
items
so,
if
I
want
to
say
you
know
just
move
this
one
over
here
this
one
over
here,
alpha
gonna
go
should
be
the
end
thing,
so
this
is
wrong
there
you
go
so
I
could
even
re-rank
items
within
it,
so
really
really
powerful.
G
Overall.
The
other
thing
that
I
wanted
to
show
was
kind
of
this.
This
hierarchy
view
right,
so
I
just
clicked
on
an
issue.
This
issue
kind
of
has
this
thing
now
over
here
I
created
a
task
list
and
you
can
see
one
of
three
tasks
that
we're
tracking
and
you
know
there
are
three
scopes.
So
if
you
think
about
there's
a
feature
you
want
to
break
down
the
feature
into
like
scopes.
G
Overall,
you
could
do
that,
so
you
could
just
create
the
overall
issue
at
the
top,
and
then
that
may
be
your
feature
and
then,
as
I
have
done
over
here,
I
created
a
task
for
three
of
the
scopes.
I
could
convert
any
of
these
taskless
items
into
issues
just
by
click
of
a
button
and
wow.
Okay,
this
is
live.
This
is
live
there,
you
go
boom,
so
I
could
even
go
into
one
of
the
scopes
and
then
what
you're
going
to
see?
G
Is
that
not
only
have
I
completed
all
these
items,
but
also
you
see
this
tracked
in
that's
the
hierarchy
and
kind
of
the
graph
or
multi-three
that
we're
building
at
the
moment.
Not
only
that,
I
could
go
into
one
of
the
tasks
of
that
scope
and
then
really
see
really
see
as
well.
So
now
I
could
go
from
okay.
Why
are
we
doing
this
task?
I
could
go
and
say
it's
because
of
this
item
number
53
over
here,
oh
and
why
are
we
doing
alien
sprites?
G
G
Let's
do
it
so.
The
other
thing
that
I
wanted
to
show
is
so
imagine
you
know
I
kind
of
alluded
that
it
was
hard
to
understand
what
a
team
is
doing
or
what
multiple
projects
are
doing.
So
one
of
the
things
that
we
have
created
over
here
is
this
octo
arcade
tracker,
and
now
I
could
see
across
all
of
my
teams.
What
are
they
doing?
I
added
different
custom
fields
in
this
case,
so
my
area
now
is
every
game.
My
game
company
is
producing.
G
Progress
is
slightly
different
as
well,
and
now
I'm
making
use
of
that
chip
date
yeah
you
know
so,
and
not
only
that
this
expense
repositories.
You
can
see
it
right
here.
This
is
not
just
on
one
repo,
this
expense
repository.
Absolutely
it's
at
the
organization
level.
So
that's
that
now
you
know
what
like.
G
I
think
this
is
all
fine,
but
you
know
we're
really
not
a
game
company,
so
you
know
what
about
showing
them,
something
like
how
github
really
uses
this:
let's
do
it,
okay,
so
one
of
the
features
that
we
ended
up
doing,
I
think
at
the
beginning
of
the
year,
was
video
upload
support,
and
this
just
allows
you
to
go
into
an
issue
or
pr
and
just
upload
a
video
yeah.
That
feature
has
taken
off
like
crazy,
especially
in
pr's,
absolutely
so.
G
The
team
at
that
moment
that
was
using
video
upload
ended
up
using
you
know
pro
the
new
projects
to
be
able
to
track
their
work,
and
you
would
think
video
uploads
is
something
simple
and
it's
not
like.
Let
me
just
show
you
how
many
items
we
ended
up
tracking
to
do
this.
Excuse
me,
it's
a
very,
very
complicated
feature.
You're
still
scrolling
yeah,
I'm
still
scrolling
down.
G
You
know
so
so
this
was
hard
to
do
and
a
task
list
or
checklist
won't
actually
allow
you
to
do
this
right
exactly
so,
and
you
want
to
track
other
metadata
and
all
of
those
items.
So
what
what
they
did
is
they
did
actually
have
a
couple
of
metadata,
so
they
ended
up
using
planning.
So
I'm
just
going
to
add
it
here,
really
quick
and
then
they're
using
mouses
as
well.
G
You
saw
that
refresh
in
real
time
and
this
kind
of
allows
you
to
understand
all
of
the
work
and
again
it's
across
many
planning
things
that
they
had
and
also
across
many
milestones
as
well,
but
this
is
one
of
the
views
that
they
created
that
I
thought
it
was
amazing,
like
this
is
planned
by
iteration.
So
now
that
the
feature
is
done
now,
they
were
doing
this
every
week.
Clearly,
but
now
that
the
feature
is
done,
if
I
ever
have
a
question
about
how
did
video
upload
support
ended
up
happening?
G
I
couldn't
even
just
utilize
this
and
see
it
look
week
of
11
16
20..
They
started
implementing
url
404.
Then
they
ended
up.
You
know
doing
adrs
and
things
like
that,
and
then
you
just
continuous
and
continuous
and
continuous
week
by
week.
I
could
really
understand
what
is
happening
over
here.
The
other
thing
they
did
is
they
put
all
of
the
pr's
in
one
to
one
of
the
views
and
when
I
talked
to
them
you
know
the
way
they
were
using.
G
This
is
to
understand,
hey
what
needed
to
actually
be
reviewed
and
just
accelerate
their
their
review
times
overall.
So
I
think
I
think
it's
amazing,
not
only
that.
Let
me
just
go
to
all
work.
Another
feature
that
I
just
love
is
ctrl
k,
I'm
going
to
group
my
milestone,
really
quick
and
there
you
go
so
here
it
is
ga
and
everything
that
went
into
ga
public
beta
and
our
staff
ship.
That
is
internal
to
us.
G
So
there
you
go
so
now
we
you
could
utilize
what
we're
doing
to
track
a
feature
which
is
great,
here's
another
team
that
did
the
exact
same
thing.
This
is
our
automation
or
workflows.
P
G
This
is
all
the
work
that
they're
doing
hi
team-
here's-
I
know
here's
by
milestones,
so
they
divided
they
kind
of
scoped
the
work
into
a
set
of
milestones
for
them,
and
you
could
kind
of
see
their
exploration
m3.
They
started
using
this
a
little
bit
with
pr.
So
now,
not
only
can
I
see
the
issues
that
got
resolved,
I
could
all
end
up
seeing
also
the
pr's
that
got
resolved
with
it,
so
et
cetera,
et
cetera.
So
I
I
think
it's
great.
You
know
another
one
that
I
really
like
over
here.
G
If
we
do
area
again
and
they
utilize
a
different
area
than
the
other
ones.
This
is
the
power
of
custom
fields
like
they
live
within.
Here
you
don't
have
to
call
an
administrator
or
anything
like
that
to
be
able
to
add
a
custom
field
to
an
item,
and
if
again,
I
just
grew
by
that
area,
then
I
could
really
see
everything
in
ui
apis
and
our
back
end.
So
it's
kind
of
evenly
split
overall
in
there
so
features
you
could
track
features
with
this.
You
could
be
very
successful
doing
it
before
you
know.
G
We
didn't
have
the
power
and
the
scale
to
be
able
to
do
that
now.
We
do
so
give
it
a
try
for
that.
The
second
thing
that
I
want
to
show
you
is
bug
backlog.
So
this
is
the
real
bug
backlog
that
went
into
the
universe,
ship
that
you
just
have
on
github
issues.
So
there's
still
some
items
in
progress
as
you
can
see,
a
waiting
review
as
well,
but
we
ended
up
you
know
in
a
short
period
of
two
weeks,
ended
up
resolving
around
65
bucks
over
all
polish
items.
G
So
not
only
can
you
use
it
to
track
features,
you
could
also
use
it
overall
to
track
vlogs
and
get
a
view
of
that.
That's
fine,
but
but
we're
not
done
you
know
it's
just
like
a
good.
It
just
keeps
on
giving
yeah.
Let
me
show
you
one
more
one
more
okay
and
then
we
could
probably
just
call
it.
So
this
is
what
I
call
the
planning
and
tracking.
We
call
it
sometimes
the
epic
tracker,
but
it
really
allows
us
to
understand
what
is
happening
across
the
organization
that
we
have.
G
So
we
have
a
bunch
of
things
that
were
happening
for
universe
2021.
This
is
it
and
you
could
probably
see
over
here.
That's
the
project's
automation
that
I
just
ended
up
mentioning
to
you
we're
making
use
of
assignments
progress.
We
have
different
fields
as
well.
So
not
only
can
you
track
a
feature,
you
could
also
end
up
tracking
several
a
bunch
yeah
as
well
absolutely
and
then
really
understand
what
is
happening
at
that
level.
G
So
and
the
last
thing
one
of
the
things
that
I
actually
love
is
the
teams
internally
are
even
using
this
for
okr.
So
I'm
not
going
to
click
on
any
of
these.
Don't
worry
teams,
okay,
but
but
you
know
we're
even
using
it
inside
of
github
for
okay,
of
course,
so
there
you
go.
L
G
Yeah,
that's
that's
a
really
good
question.
What
I
would
say
you
know:
we've
been
four
months:
we
have
lots
of
customers,
we've
kind
of
grown
exponentially
overall
in
there
and
there's
one
core
validation
on
it,
which
is
you
know.
Project
tables
are
really
powerful
together
with
custom
fields
and
and
overall
the
kind
of
the
ability
then
to
have
these
views
that
are
for
each
perspective
that
you
want
to
have
so
like
that
has
been
taken
off
like
fire.
G
So
really
on
that
and
then
the
second
thing,
which
is
more
like
hey,
what
is
it
that
we
need
to
do
going
forward
is
hey.
This.
Is
this
concept
of
hierarchy
great
at
the
issue
level
and
task
list?
You
know
people
want
that
kind
of
infused
now
into
project
and
boards
as
well.
So
we
have
like
great
validation,
lots
of
people
using
the
product
at
the
moment
and
at
the
same
time,
some
things
that
we
know
we're
going
to
have
to
really
invest
in
the
future.
For.
G
All
right
yeah
definitely
so
let
me
use
out.
G
L
G
Number
one
what
I
would
say
and
we
could
share
my
screen
now,
so
we
have
a
feature
right
now
in
alpha.
Okay,
at
the
moment,
that
is
insights,
and
I
love
this
feature.
This
is
gonna,
be
one
of
the
most
powerful
features
actually
coming
in
the
in
the
next
six
months.
I
love
it
so
what
you're
seeing
over
here
is.
I
have
a
project.
The
project
is
collecting
all
of
this
data,
or
maybe
I
have
a
team,
and
I
want
to
set
up.
G
You
know
a
set
of
repos
that
feed
into
that
team
as
well,
and
then
I
want
to
just
ask
questions
and
get
insights
from
that,
and
what
we
want
to
do
is
just
kind
of
bring
the
power
of
reporting
into
it.
So
we
we're
starting
with
this
one,
that
we
call
burn
up,
or
sometimes
it's
called
cfd
out
there
in
the
industry
as
well.
You
can
see
this
is
a
real
team
inside
of
github.
This
is
real
data
by
them
as
well.
G
If
I
go
to
three
months
and
it
refresh,
you
could
kind
of
see
you
you
get.
So
if
we
just
do
this,
you
could
kind
of
get
like
a
burn
up.
At
that
moment,
you
can
see
kind
of
in
progress
and
done
and
how
the
team
has
been
doing
so
far
and
that
another
one
if
we
go
back
into
the
backlog-
and
I
do
the
exact
same
thing-
you
see-
we
used
a
lot
of
statuses
in
there
too
yeah
one
or
two
yeah.
G
So
again,
you
know
you
could
go
over
here
and
do
the
exact
same
thing,
maybe
not
in
progress,
but
you
could
get
a
burn
up
as
well,
but
we
have
a
lot
more
that
is
coming.
This
is
what
really
has
me
excited
are
the
inside
steam.
I
give
up
it's
really
hard
work
on
this
and
it's
going
to
be
amazing.
So
we
have
work
in
progress.
We
have
bug
trends.
G
We
have
the
ability
to
just
get
the
data
that
we
have
in
the
in
the
actual
project
and
then
visualize
it
in
lines
in
bar
charts
or
even
in
area
charts.
So
you
can
kind
of
see
anything
here.
So
that's
kind
of
one
okay.
That
has
me
like
really
really
really
excited
one.
More.
Maybe
okay,
okay,
one
more
maybe.
P
G
G
Didn't
enforce
it,
so
you
know
it's
never
been
seen
outside
of
github
more
or
less
so.
Here's
normal
project
normal
view,
but
what
about?
If
you
could
actually
see
it
as
a
timeline
yeah
and
you
could
kind
of
laid
out
things
there
in
a
roadmap
in
through
time
in
a
time
span
overall,
like
I
think
this
is
gonna,
be
huge.
So
that's
another
thing
that
you
should
expect
coming
and
then
the
last
thing
that
I
want
to
leak
is
really
hierarchy
coming
into
it.
Yeah.
Q
G
Of
the
customers
giving
us
that
feedback,
we
got
you,
we
got
your
back
on
this
and
you
know
we're
going
to
be
investing
a
lot
on
it
as
well.
So
there
you
go
so
this
insights
there's
a
lot
of
other
things
that
you
can
see
in
the
github
roadmap
as
well,
and
then
we
got
a
timeline
view
and
then
also
hierarchy
on
the
next.
L
I
love
it.
I
love
it
so,
mario,
it
looks
like
I'm
not
the
only
one
interested
in
this,
because
we've
got
a
handful
of
questions
actually
more
than
that.
So
I'm
going
to
read
a
couple
of
these
off.
If
you
don't
mind
answering
okay,
all
right,
so
this
is
from
again
I'm
sorry
for
mispronouncing
your
handles.
I
will
do
my
very
best
ly
becker.
Can
you
show
the
issue
task
hierarchy,
relationship
in
the
table
or
board
view
so.
G
We
cannot
yet,
but
this
right
here
if
we
show
the
screen
again,
this
is
what
what
we're
experimenting
with
you
can
see.
My
imagine
this
was
kind
of
the
feature
and
these
were
the
scopes
and
then
you're
going
to
be
able
to
actually
to
do
that.
So
that
is,
you
know
again
one
of
the
features
that
we
get
asked
a
lot
and
that's
you
know
high
in
our
backlog
as
part
of
of
the
public
beta
all.
L
Right,
I
got
another
one
for
from
you
from:
let's
do
it
from
bagatka.
Again,
apologies.
The
question
is
looking
through
the
repositories
and
their
issues.
Is
it
possible
to
find
a
project
for
open
source
activity
by
using
repo
underscore
url
slash
contribute?
Is
there
any
ui
for
that?
It
would
be
great
to
have
a
page
with
projects
that
can
be
interesting
for
you
by
filters
containing
good
first
issues.
Yeah.
G
So
I
think
that's
a
great
idea.
We
have,
by
the
way,
the
way
to
give
feedback
on
the
product.
We
have
a
feedback
discussion,
so
I
think
it's
github
feedback.
You
know
skill.com
github
feedback
and
then
there's
a
discussions
and
you
can
find
github
issues
there.
Please
put
any
type
of
thing
that
comes
into
your
mind
into
it.
We
love
engaging
with
our
customers
overall,
but
yeah.
I
think
that's
a
great
idea.
G
We
will
invest
more
in
the
index
pages
that
we
have
today
overall,
so
my
hope
is
that
to
be
able
to
just
kind
of
demo
it
next
time
yeah.
So
all.
L
G
Like
starting,
I
think
today,
if
we
already
turn
on
the
feature
flags,
you
should
be
able
to
use
it
for
github
apps
as
well,
so
give
it
a
try
and
again,
if
there's
anything
that
you
see,
that
needs
to
be
improved.
Please
let
us
know,
but
it
is.
L
L
Sure
great
question
look
you've
given
feedback
to
the
product
manager
and
you're
already
making
changes.
Thank
you
nick
all
right.
Next,
I'm
going
to
butcher
this
one
too
indiets.
Will
it
be
possible
to
have
multi-line
cards
and
new
projects
like
we
currently
have
in
old
projects.
G
That's
a
good
one.
I
don't
that
one.
I
don't
want
to
leak
yet,
okay,
so
what
I
would
say
it's
we
we're
kind
of
exploring
different
things
in
there
to
kind
of
take
it
to
the
next
level
on
it
and
I'm
really
excited.
G
I
just
saw
the
team,
the
design
team
of
github
issues,
extremely
talented
people
just
sent
me
right
before
this
keynote,
send
me
a
mock
of
it
and
I
was
kind
of
dancing
and
you
know
overall,
when
I
ended
up
when
I
saw
it
so
really
really
really
exciting.
All
right!
Well,.
L
G
So
also
in
the
roadmap,
you
will
see
it
as
one
of
the
high
kind
of
items
in
there
in
future,
that
is
shrank
very,
very
high,
so
we
have
right
now
a
little
message
on
it,
but
yes
repository
level,
you
know
projects
and
the
ability
to
find
them.
There
is
something
that
is
coming
as
we
continue
on
the
beta.
G
Oh,
that's
a
good
one.
I
don't
see
why
we
cannot
extend
the
metadata.
In
fact
today
you
could
add.
You
know
remember
when
I
said
that
you
could
add
prs.
Let's
go
back
into
this
over
here.
You
could
add
anything
over
here.
So
as
a
node
as
an
example,
you
know
this
is
a
note.
G
So
on
that
end,
yes,
you
end
up,
you
could
add
any
metadata
within
the
table,
then
the
real
trick
in
my
opinion,
is
then
start
actually
making
that
a
more
first
class
citizen
actually
interacting
with
the
pull
requests,
but
I,
but
I
think,
yeah.
I
think
this
is
kind
of
a
continuation
of
what.
L
We're
doing
for
fantastic,
that's
awesome,
so
for
all
of
the
people
whose
names
I
pronounced
correctly
and
incorrectly.
Thank
you
so
much
for
asking
them
keep
those
coming
all
day
today
and
all
day
tomorrow,
because
remember
you
tell
us
we
get
to
ask
the
speakers
here
so
mario,
thank
you
so
so
much
for
coming
up
here
and
talking
to
us
today
about
get
up
issues.
I
really
really
appreciate
it.
Thank
you
jerry
thanks
for
having
me
absolutely.
L
What
I
really
appreciate,
though,
is
that
we
were
able
to
walk
through
the
why
we
made
the
investments
into
the
future,
and
also
you
got
to
see
it
in
action
live
even
those
questions
that
were
asked
from
folks.
You
got
to
see
mario
walk
through
that
and
that's
amazing.
I
have
to
tell
you
that
I've
been
able
to
use
this
feature
for
months
and
I'm
pumped
that
y'all
get
to
use
it
today.
L
M
M
L
Speaking
of
ways
to
engage
check
out
our
tips
for
hosting
a
universe,
watch
party
grab
some
of
your
friends.
Your
colleagues
check
out
our
games,
icebreakers
and
conversation
starters
to
engage
with
your
crew
before,
during
and
after
the
live
stream,
and
if
you're
watching
solo,
you
can
still
use
the
kit
to
enhance
your
universe
experience.
You
can
also
find
the
kit
in
the
ways
to
engage
tab
in
the
upper
right
corner
of
your
screen
up
next
we're
digging
into
all
things:
github
enterprise.
Now
at
github.
L
Our
goal
is
to
be
the
home
for
all
developers,
not
just
hobby
developers,
not
just
open
source
developers,
the
home
for
all
developers,
and
that
means
being
there
for
you,
whether
you're
at
home,
a
coffee
shop
or
at
work,
and
that's
where
the
enterprise
piece
comes
in
so
up.
Next,
we
have
my
manager,
maya,
ross
senior
director
of
product
management
here
at
github
she's,
going
to
share
with
us
the
about
the
advancements
we've
made
for
companies
in
her
segment
called
github
in
the
enterprise.
I
Those
range
from
new,
innovative
startups,
as
well
as
many
of
the
world's
largest
organizations,
and
it's
having
a
huge
impact
on
their
businesses
as
well.
Let's
take
3m,
they
adopted
github
a
number
of
years
ago,
and
in
doing
so
they
came
to
us
wanting
to
speed
up
their
business.
They
were
able
to
increase
the
number
of
deployments.
They
were
doing
from
400
every
60
days
to
6
000.,
that's
over
a
15
increase,
but
you
know
results
like
that.
I
Don't
come
overnight
and
we've
been
working
hard
for
many
years
to
build
the
platform
that
enables
that
we're
excited
to
say
now
that
github
enterprise
is
actually
10
years
old
and
the
first
version
of
github
enterprise
was
actually
called
github
firewall
install.
It
was
all
about
running
github
behind
your
firewall
we'd
be
making
big
changes
in
that
time.
I
Recently
we
shipped
actions
and
advanced
security
to
enterprise
server.
We've
also
been
investing
in
the
small
things
that
make
a
difference
to
our
customers.
Things
like
the
addition
of
authenticating
with
hardware
security
keys
for
git
events,
which
ship
to
our
server
customers
just
a
few
weeks
ago,
but
you
know
with
building.
All
of
these
features
also
comes
the
need
for
reliability
and
stability,
and
github
enterprise
is
built
on
the
same
platform
that
supports
github.com,
which
today
holds
over
16
million
repositories
and
last
year
took
1.9
billion
contributions.
I
That
exact
same
code
is
what's
supporting
our
enterprise
customers,
no
matter
how
you
use
github
we've
been
making
huge
changes
specifically
for
enterprises
too.
One
example
is
the
investments
we've
been
making
in
monorepo
performance
over
the
last
few
months
that
enable
companies
running
huge,
mono,
repos
to
add
new
users
and
new
commits
to
those
without
any
problems.
I
Github
ourselves
has
benefited
massively
from
them.
We
run
a
mono
repo
with
over
15
million
files,
so
those
investments
we're
making
are
benefiting
you,
some
of
our
largest
customers,
as
well
as
ourselves
in
github
enterprise
server.
We've
also
been
investing
in
a
specific
release:
candidate
program
this
year,
which
launched
in
the
beginning
of
2021
that
enables
companies
to
try
our
releases
early
to
get
the
earliest
possible
access
for
new
features
and
give
us
feedback
on
whether
the
release
meets
your
expectations
so
that
we
can
iterate
on
it
and
improve
it.
I
This
year
we
have
worked
with
over
150
businesses
in
that
release
candidate
program
and
I'm
excited
to
continue
partnering
with
all
of
our
customers
out
there
to
continue
making
github
enterprise
better
so
github
enterprise.
Today,
really
very
much
is
a
complete
devops
platform,
one
that
optimizes
for
the
developer,
experience
and
one
that
increasingly
moves
that
developer
experience
into
the
cloud
and
one
that
also
provides
enterprises
with
the
security
and
governance
tools
that
they
need.
I
You
heard
about
that
in
the
keynote,
but
now
I'm
going
to
go
through
a
few
examples
of
how
that
actually
manifests
in
the
product
for
our
enterprise
customers.
So
let's
have
a
look.
First
of
all,
we
are
going
to
have
a
look
at
a
kind
of
typical
enterprise
developers
workflow
and
how
we
can
build
some
security
and
compliance
checks
into
that
workflow
in
a
way
that
doesn't
get
in
their
way
at
all.
Over
here.
I
Let's
say
we
have
just
come
out
of
our
stand
up,
and
this
is
our
team
stand
up
board
running
on
the
new
github
projects,
and
here
we
have
an
issue.
That's
been
raised.
First
of
all,
it
is
to
clean
up
some
internal
security
keys,
which
have
been
checked
in
this
has
been
found
by
github
code
scanning,
using
a
custom
pattern
that
we
have
defined
for
our
company
and
you'll,
see
here
that
I've
actually
already
got
a
branch
automatically
created.
I
For
me,
this
is
running
on
an
action
I
configured
to
create
a
branch
whenever
an
issue
is
raised.
The
purpose
of
that
is
to
enable
traceability.
So
we
know
it's
so
important
for
companies
operating
in
highly
regulated
industries
to
be
able
to
trace
code
from
idea
right
through
to
deployment
and
with
github
as
a
single
platform.
You
can
do
that.
So,
let's
go
into
this
branch.
I
We've
actually
already
made
some
changes.
We're
gonna
raise
that
pull
request,
create
the
pull
request
and
then
some
of
our
automated
checks
running
on
actions
are
going
to
start.
You
can
see
rci
our
build
checks,
our
code
scanning
checks
and
our
unit
tests
are
running
now
in
a
real
enterprise
environment.
Here
I
would
go
off
and
find
some
reviewers
for
my
pull
request
and,
of
course,
we'd
have
a
branch
protection
rule
set
up.
I
I
can't
merge
this
without
having
at
least
one
reviewer
today,
of
course,
I'm
actually
gonna
skip
that
step
just
for
the
brevity
of
a
demo
so
that
our
checks
have
run
I'm
going
to
merge
that
pull
request
and
automatically
again.
This
is
going
to
kick
off
our
deployments,
so
we've
said
it
is
now
going
to
be
safe
to
deploy
to
our
various
environments,
all
of
which
are
configured
in
github,
with
our
secrets
managed
directly
in
github.
I
I
Let's
have
a
look
at
that
workflow
and
you
can
see
it
has
already
gone
through
our
staging
deployment
run,
so
we
could
go,
have
a
look
there
and
it's
got
to
production
in
order
to
avoid
production.
I
do
need
somebody
again
to
review
that,
so
we
have
all
of
our
live
site
checks
built
in
here.
I'm
hacking
this
a
little
bit
I've
given
myself
the
ability
to
approve
that
deployment
I'll,
prove
it
and
there
we
go
we're
deploying
to
production.
I
So
there
with
github,
you
have
a
developer
experience
that
is
collaborative
that
is
automated,
and
that
also
has
compliance
and
security
built
into
that
developer.
Workflow.
Now
I
want
to
go
into
the
fundamentals
of
github
enterprise.
There
are
really
three
pillars
that
make
up
the
enterprise
administration
and
security,
offering.
The
first
is
access
control.
The
second
is
observability
and
the
third
is
governance.
I
Talking,
first
of
all,
about
access
control.
What
we
really
mean
here,
first
and
foremost,
is
that
private
means
private.
So
when
you
host
your
code
with
github,
you
can
be
assured
that
no
one
else
is
going
to
see
them
and
we
achieve
that
in
a
variety
of
means:
first,
through
role-based
access
controls;
second,
through
identity
management,
authentication
management
and
the
third.
We
won't
talk
about
too
much
today,
but
is
networking
controls,
so
you
can
configure
what
ip
addresses
can
access
your
corporate
repositories.
I
So
let's
go
ahead
and
have
a
look
at
some
of
this.
So
first
of
all,
we
are
going
to
hop
into
another
enterprise
that
I
have
set
up
over
here.
I
have
another
organization,
this
is
an
enterprise
organization
with
a
number
of
repositories
and
in
it
I
have
a
set
of
teams.
These
are
all
of
the
teams
across
my
business
who
need
access
to
those
repos.
I
All
of
those
repos
have
the
access
managed
by
roles.
So
let's
just
go
in
and
look
at
the
skyline
repo
again
and
how
we
have
set
up
our
roles.
But
here
you
will
see
the
five
roles
that
we
know
and
love
across
github.
We've
had
these
for
many
years
and
down
here,
you'll
now
see
a
new
section
custom
roles
whereby
we
can
define
custom
roles
specific
to
our
teams
and
our
business
and
assign
those
to
different
teams
or
engineers
for
each
repository.
I
Let's
have
a
look
at
that.
We
hop
over
to
manage
access
here.
We
have
our
security
operations
team
and
they've
already
been
given
that
security
ops
wrong,
that's
much
better
than
giving
them
full
administration
access
whereby
they
could
take
control
of
the
whole
repository
and
everything
that
governs
it.
Now.
I
Just
going
back
to
our
organization
teams,
we've
recently
added
the
ability
for
our
enterprise
power
customers
to
fully
own
their
users,
with
enterprise
managed
users
and
they're
all
authenticated
just
by
a
single
sign-on
from
your
identity
provider,
they're
provisioned
automatically
and
de-provisioned
automatically,
and
we
can
also
assign
those
users
to
teams
automatically.
Let's
have
a
look
at
that,
so,
let's
go
back
to
our
organization
and
our
teams.
I
Here
we
have
a
number
of
teams
set
up:
let's
take
our
product
team,
that's
our
excellent
product
team,
which
of
course
I
am
part
of
now
this
product
team.
The
membership
is
actually
governed
via
our
identity
provider.
Here
I've
set
it
up
with
our
support
engineering
group.
So
all
of
the
members
of
that
group
are
automatically
synced
into
this
team.
I
We
can
change
that.
Let's
actually
select
our
product
team,
this
time,
save
the
changes
and
immediately
the
membership
of
that
team
is
going
to
update.
Now,
let's
go
on
to
observability
with
github,
you
get
a
comprehensive
set
of
audit
logs
that
covers
every
project
repository
and
member
across
your
organization.
I
This
means
that
you
can
both
proactively
and
reactively,
detect,
threats
and
audit
everything
that's
gone
on
and
provide
that
to
your
auditors.
We've
also
made
some
improvements
to
ensure
that
those
audit
logs
are
available
in
the
security
tools
you
use
with
audit
log
streaming,
and
let's
have
a
look
at
this
briefly
so
over
here
we
have
our
enterprise
order.
Log
you
can
see.
We've
got
a
whole
set
of
events
that
have
happened
across
this
enterprise,
including
some
of
the
changes
that
I
recently
made,
and
we
can
also
stream
this.
I
So
we
can
stream
this
to
splunk
or
azure
event,
hubs
we're
going
to
be
adding
more
providers
over
time.
If
I
hop
into
slunk,
you
can
see
some
of
my
get
push.
Events
I've
gone
on
around
the
organization
recently
and
we
could
also
see
any
access,
events
or
team
membership
change
events,
pull
requests
issues.
Anything
will
go
right
into
the
tools
that
you
are
using.
I
I
If
you
want
to
find
out
more,
I
do
suggest
that
you
go
to
github.com
enterprise,
which
is
our
marketing
page
on
the
github
website,
and
my
colleague
and
our
host
today,
jared
mccree
is
also
doing
a
talk
on
what's
new
in
enterprise,
where
he
will
do
a
deep
dive
in
some
of
the
capabilities
that
I've
just
shown
you
and
how
you
can
get
started
with
them.
L
Security,
devops
and
collaboration:
these
are
the
three
foundational
pieces
on
which
github
enterprise
is
built.
The
focus
is
on
removing
any
roadblocks
to
adoption
for
enterprises
so
that
we
can
empower
developers
to
create
the
products
of
tomorrow
now
lorena
I
just
I
couldn't
be
more
thrilled
to
see
what
happens
next.
M
Well,
what's
really
exciting
is
we
have
a
lot
of
people
reacting
to
us
right
now,
right
here
in
discussions
we
have
folks
joining
us
from
ghana,
australia,
india,
poland,
portugal,
china,
guatemala,
amsterdam
and,
more
again,
all
in
discussions.
In
fact,
we
got
a.
We
got
a
comment
from
tom,
garcia,
p,
on
discussion,
saying
never
seen
coding
djs
before
this
is
awesome,
yeah
be
like
tom,
garcia,
p
join
us
in
the
conversation.
L
Coming
up
next,
we
have
a
block
of
short
sessions
for
you.
First,
we
have
the
always
fantastic
neha
batra
presenting
in
a
new
segment
called
meet
the
maintainers,
then
brian
douglas
known
worldwide,
as
b-dougie
will
present
our
latest
installment
of
inside
github,
we'll
discuss
how
we're
using
actions
at
github
and
to
close
out
this
section.
We
have
the
great
miles
barrens
hosting
a
session
called
releases
galore.
All
right,
that's
enough
from
us.
Let's
dive
in.
R
Hi,
I'm
neha
batra
and
I'm
an
engineering
director
here
at
github
and
I'm
so
excited
to
introduce
you
to
this
new
segment
that
we're
doing
where
we're
going
to
be
speaking
with
two
open
source,
maintainers,
paulus
and
sage,
and
we're
going
to
be
seeing
what
the
world
looks
like
from
their
seat
and
so
they'll
be
sharing
their
screen
and
they'll
be
doing
a
bit
of
a
show
and
tell.
And
so
you
can
see
what
it
looks
like
to
be
an
open
source
maintainer.
So
why
don't
the
two
of
you
introduce
yourselves
yeah.
Q
Awesome
so
I'm
paula,
schulze,
I'm
the
founder
of
home
assistant
home
assistant,
is
an
eight-year-old
open
source
home
automation
platform
that
you
can
run
at
your
home
with
a
focus
on
local
control
and
privacy.
So,
basically
you
can
install
it
on
a
raspberry
pi
and
then
take
control
of
your
home.
S
R
Q
So
what
we
do
in
home
assistant
is
that
we
have
a
notion
of
code
owners
and
so
with
code
owners.
It
means
that
we
certain
parts
of
the
application
and
we
actually
check
file
paths
for
that
we
say.
Oh
this
part
is
code
owned
by
this
group
or,
and
those
people
are
automatically
mentioned
in
a
pull
request
or
in
an
issue.
Q
So
that
means
that
whenever
something
in
the
core
is
touched
or
something,
then
it
will
automatically
say:
hey
home
system,
slash
core
as
a
team
will
be
mentioned,
or
it
can
happen
that,
like
individual
people
are
mentioned,
and
so,
for
example,
if
you
look
at
my
screen
here,
you
see
like
there's
a
team
mention
there's
a
personal
mention,
there's
stuff,
I
commented
the
answer
so
and
then
yeah,
I
just
go
through
it
and
I
just
kind
of
you
know
sometimes,
like
generally,
when
things
are
merged
and
like,
for
example,
here
I
see
that,
like
martin
has
looked
at
it.
Q
R
S
Just
want
to
be
able
to
focus
on
the
work
itself.
The
community
starts
to
drive
you
in
interesting
directions.
I
have
a
very
active
team
of
contrib
maintainers
that
are
all
there
to
support
the
community.
I'm
usually
not
active
most
of
the
time
in
the
community,
because
I
do
lots
of
the
maintaining
work
and
the
code
itself,
but
then
I
have
people.
I
have
close
to
three
different
people
assigned
to
just
help
the
people
in
the
community
and
just
get
just
give
me
some
feedback
or
give
me
like
a
quick
summary
of.
S
What's
going
on,
I
tend
to
check
pull
requests
first
before
going
into
issues,
because
I
mean
pull.
Requests
are
basically
solutions
to
existing
problems.
Issues
basically
is
more
problems,
so
you
just.
I
don't
want
to
spend
my
time
looking
at
more
problems.
I
just
come
here
to
see
like
what
what
what
are
people
trying
to
solve
or
fix
themselves,
and
how
can
I
help
them
get
to
the
finish
line
if
they
have
questions.
S
One
of
them,
basically,
is
to
know
sort
of
track
who
is
using
the
library
like
who
is
using
track
for
ui
just
come
there
and
sort
of
like
put
the
project,
your
company
and
a
link
to
the
website,
so
we
can
at
least
have
something
to
brag
about,
or
also
put
it
on,
our
showcase
page
on
the
website,
and
then
the
second
useful
one
for
me
is
one
of
our
core
community.
Maintainers,
basically
just
helps
us
like
compile
all
of
the
frequently
asked
questions
in
there.
Q
One
of
the
benefits
of
a
forum
like
github
discussions
is
that
it
can
actually
people
can
search
for
it
right,
like
anything
that
you
put
on
discord,
it's
just
like
a
black
box.
It's
gone
and
like
a
lot
of
knowledge,
is
actually
getting
lost
because
people
are
helping
one
another
and
people
are
not
writing
it
up
or
writing
it
out
in
a
way
that
other
people
can
process
it.
So.
S
So
right
now,
one
of
the
things
we've
been
spending
a
lot
of
our
time.
I've
been
thinking
about
is
how
do
we
build
or
design
accessible,
ui
components
in
a
way
that
is
not
tied
to
a
framework.
Q
Basically,
we've
been
trying
to
make
home
system
easier
to
use
ever
since
we
got
like
people
working
on
full
time,
because
that's
when
we
really
were
like
okay,
we
wanna
instead
of
our
technological
audience
of
like
system
administrators
people
that
can
run
python
applications
and
write
yammer
configuration
files.
We
wanna
get
from
that
group
to
home
automation,
enthusiasts
and
people
that
want
to
make
the
best
out
of
their
home.
R
Yeah
well,
thank
you
so
much.
I
feel
like
I
learned
so
much
from
the
two
of
you.
I
hopefully
you
two
learned
from
each
other
as
well.
What
I
really
wanted
to
do
is
kind
of
really
see
what
the
world
looked
like
from
your
seats
and
eventually
show
our
audience
what
it
might
look
like
from
a
maintainer's
perspective.
What
you
pick
up
on
how
you
try
to
solve
problems
within
your
community?
R
F
As
you've
seen
the
day
with
codespaces,
we
use
our
product
to
build
and
maintain
github.
What
I'm
going
to
show
you
today
is
how
teams
across
github
use
one
of
our
most
powerful
products
git
of
actions
in
ways
that
may
not
come
to
mind
when
you
hear
ci
cd
github
actions
makes
it
easy
to
automate
all
your
software
workflows
and
today
there's
over
10
000
in
the
github
marketplace,
and
what's
really
cool
about
that,
it's
really
about
flexible
automation.
That
allows
for
so
many
potential
use
cases
and
in
true
github
fashion.
F
F
F
Another
way
we
use
github
actions
is
automate
our
workflows
in
the
github
security
lab.
They
use
github
actions
to
track
secure
reports
in
github's
bounty
program,
but
also
the
track
vulnerabilities
that
we
find
in
open
source
components
that
we
use.
When
I
find
a
security
issue
in
open
source
projects,
I
can
go
here
to
report
it
and
fill
in
the
issue.
Form
template.
F
F
Okay,
so
we've
got
one
more
that
I
think
is
personally
amazing
and
you're,
probably
gonna
find
it
super
useful
if
you're
tuning
in
a
lot
of
teams,
use
actions
to
automate
the
handoff
in
on-call
rotation
and
here
on
the
committee's
team,
they
open
an
issue
that
tags
the
right
people
and
make
sure
the
right
knowledge
is
captured
on
the
new
on-call
rotation
for
the
necessary
context.
This
is
so
important
for
our
teams
across
time
zones
to
keep
work
moving
forward.
F
T
Hi
and
welcome
to
releases
galore
I'm
miles,
I'm
a
staff
product
manager
here
at
github
and
I've
been
working
with
a
number
of
hubbers
to
improve
the
github
releases
experience
for
our
developers
and
maintainers
across
the
platform.
You
may
be
wondering
what
is
releases
galore
releases.
Galore
right
now
is
about
four
different
things
that
we've
done
to
improve
releases.
The
first
is
introducing
automatically
generated
release
notes.
We
interviewed
a
number
of
maintainers,
and
this
was
the
number
one
request
that
all
of
them
had.
T
The
next
thing
that
we
did
was
a
big
refresh
of
the
ui
of
releases.
We
wanted
to
make
releases,
look
compelling
and
something
that
maintainers
would
be
proud
to
share
and
consumers
would
be
excited
to
read
some
people
like
to
write,
release,
notes
and
put
them
on
blogs.
We
wanted
to
make
it
so
that
people
could
do
everything
right
on
github
and
it
could
look
amazing.
T
We
also
want
to
make
sure
you
could
automate
all
of
this,
so
we
added
new
functionality
to
the
github
api,
to
make
it
easier
than
ever
to
automate
releases
and
have
done
a
bunch
of
tests
to
make
sure
that
it
works
right
out
of
the
box
with
github
actions
and
fixing
lots
of
paper
cuts
along
the
way,
making
it
a
better
experience
overall
and
leaving
things
better
than
we
found
it
so
here
at
github,
we're
all
about
demos,
not
memos.
So
let's
get
right
into
the
content
here
you
can
see
my
repository
node
osc.
T
This
was
actually
the
first
package
that
I
worked
with
when
I
got
started
with
node.js.
It
is
something
I've
been
maintaining
for
at
least
almost
10
years.
Probably
now
at
this
point
now
is
really
cool
about
it
is.
I
did
not
have
release
notes
for
the
longest
time,
but
with
this
new
release
notes
feature,
I
am
actually
able
to
go
through
and
get
release
notes
in
there.
So
if
we
go
to
the
pull
request,
we
could
see
that
I
do
have
a
pull
request.
I
haven't
landed
yet
to
add
caching
to
setup
node.
T
This
is
a
cool
new
feature
where
you
can
add
cache
npm
into
your
setup.
Node
instructions
and
all
of
your
workflows
that
are
running
will
share
a
cache,
so
everything
can
run
faster
now
squash
and
merge
this
pull
request,
and
now
I'm
ready
to
release
it
to
the
world.
Formally,
I
would
have
had
to
have
gone
in.
I
would
have
had
to
have
updated
my
repo
locally
with
all
the
changes.
T
I'd
have
to
run
a
command
locally
and
then
push
it,
but
instead
we're
going
to
go
in
and
we're
going
to
run
this
action
that
I've
got
called
bump
version
and
it's
a
manually
run
workflow.
So
it
can
go
here.
I
could
type
in
the
type
of
release
that
I
want,
which
is
patch
and
click
run
workflow,
and
this
is
great:
it's
going
to
kick
off
the
workflow
and
do
everything
to
create
this
release
and
take
a
quick
look
here
under
workflows
and
see
what
it's
doing
bump
version
is
checking
out
the
repo.
T
It's
then
setting
up
node.
It
is
then
running
install
and
then
it
is
pushing
the
tags
that
I'm
creating
by
running
npm
version
and
when
it's
done
it's
going
to
automate
creating
a
release.
Well,
it
goes
ahead
and
does
all
of
that
work
I'm
going
to
go
ahead
and
hop
into
this
other
repository
called
release.
Notes
test.
T
It's
a
little
bit
more
of
a
toy
repository
to
show
you
what
it
looks
like
to
make
releases
in
the
ui
one
of
the
really
cool
things
that
we're
taking
advantage
of
here
is
the
new
dot
github
slash
release
yaml
file,
where
we've
got
all
these
different
categories
that
I'm
creating.
So
we
could
organize
the
release,
notes
based
on
labels
to
pull
requests.
T
T
This
is
a
breaking
change,
so
I'm
going
to
go
v2
to
200.,
rather
than
clicking
create
new
tag,
I'm
actually
going
to
hit
enter,
which
I
don't
know
if
any
of
you
got
hit
by
that
before,
but
that
actually
used
to
publish
the
release,
and
I
would
accidentally
make
lots
of
releases
doing
that
and
now
we've
got
this
button
here.
Auto
generate
release,
notes,
I'm
going
to
give
it
a
click,
and
just
like
that,
we've
generated
all
the
notes
for
the
release.
T
We
can
see
that
we've
got
breaking
changes
bugs
fixes
and
other
changes,
including
docs,
and
it
even
was
nice
enough
to
recognize
that
it
was
my
first
time
contributing
to
this
repository.
So
you
can
go
down
here,
I'm
going
to
hit,
publish
and
there
we
go.
Here's
a
beautiful,
looking
release
with
all
the
things
that
we
want
in
there
ready
to
go
now.
T
T
It
has
my
pr
that
you
saw
me
land
right.
There
was
the
only
change
that
it
was
in
there.
I
can
click
on
the
full
change
log
and
I
could
see
all
the
commits
that
were
part
of
the
release
and
all
the
changes
that
came
with
it
and
we're
good
to
go.
It's
super
awesome.
I'm
really
really
happy
with
how
great
this
flow
is.
L
Don't
forget
that
you
can
ask
questions
to
us
or
any
of
the
speakers
you've
seen
by
using
github
discussions.
You
can
also
engage
with
us
on
twitter,
using
the
hashtag
getupuniverse
like
danielgarjones,
who
tweeted
at
us.
How
cool
is
showing
inner
real
usage
of
issues?
It
is
cooler
than
a
polar
bear's
toenails.
L
Yes,
that
is
an
outcast
quote.
Yes,
I
am
from
atlanta,
but
keep
those
tweets
coming
and
thank
you,
daniel
gar
jones,
for
your
comment.
So
once
the
main
broadcast
wraps
for
the
day,
we'll
have
a
boatload
of
live
sessions
on
a
wide
range
of
topics
for
you
to
see,
for
example,
if
you're
interested
in
hearing
more
about
github
enterprise,
specifically,
we
have
some
great
on-demand
sessions
that
you
can
view
at
any
time
at
githubuniverse.com.
M
We'll
be
back
tomorrow
for
day
two,
where
we
will
be
focusing
on
the
interconnected
community,
we'll
start
with
an
invigorating
keynote
from
erica
brusha
and
we'll
have
many
more
live
sessions
with
such
folks
as
mike
hanley
and
emily
freeman.
Additionally,
we
have
amas
and
interactive
sessions,
all
of
which
can
be
found
on
the
schedule
coming
up.
M
We'll
delve
into
one
of
github's
latest
features
copilot
a
tool
using
the
power
of
ai
to
help
us
write
more
intelligently
by
leveraging
the
collective
power
of
code
existing
on
the
public
internet,
we'll
learn
more
about
how
we
build
copilot
and
what
we're
doing
with
it
from
paige
bailey,
an
ai
expert
and
principal
product
manager
at
microsoft.
Without
further
ado
on
to
copilot.
U
U
It's
built
right
into
your
editor
and
it
gives
you
tailored
suggestions
for
the
code
that
you're
writing
bringing
the
collective
wisdom
of
the
world's
developers
straight
to
you
to
give
us
some
behind
the
scenes
insight
into
copilot
we've
brought
in
the
lead
architect
for
the
project,
agadamour
oga.
Why
don't
you
introduce
yourself
sure.
V
U
I've
been
able
to
use
copilot
for
the
last
several
months
and
I've
been
so
enchanted
by
how
well
it
works
most
of
the
time,
but
there
are
some
times
where
copilot
might
give
me
a
recommendation.
That
doesn't
quite
make
sense.
Could
you
talk
a
little
bit
about
why
that
might
be,
why
it's
so
good
and
then
also
sometimes
why
it
might
run
into
snags
or
misunderstandings.
V
V
Sanitize
or
use
olympic,
it
will.
A
V
So
we
do
recommend
that
you
use
the
standard
tooling
standard
safeguards
things
like
github,
advanced
security,
to
check
all
the
suggestions
and
make
sure
about.
There's
no
unwanted
problem
set.
U
I
I
often
find
that
copilot
helps
me
better,
articulate
the
kind
of
work
that
I'd
like
to
have
happen
in
my
code,
because
in
order
to
get
it
to
have
these
super
accurate
responses
and
super
accurate
suggestions,
you
have
to
be
very
very
clear.
Whenever
you
have
a
power
tool
that
you
know
you're,
perhaps
using
to
build
a
house,
you
can
implement
safety
guards
or
some
sort
of
feature
that
helps
protect
people
from
potentially
falling
into
those
those
dangerous
situations.
U
V
V
U
So
another
thing
that
I've
observed
frequently
when
using
copilot
is
that
sometimes
I
get
feedback
that
feels
almost
verbatim
from
documentation
or
from
tutorials
or
examples
of
code
that
I've
seen
on
github.
I
especially
run
into
this
when
looking
at
machine
learning
framework
suggestions
as
an
example.
V
Many
people
think
that
the
model
behind
co-pilots
somehow
stores
the
dreams
out,
and
it
just
picks
snippets
that
are
maybe
relevant
to
the
new
situation.
That
is,
in
fact
not
the
case.
They
see
these
examples
that
seem
too
close
to
existing
code.
It's
typically
because
there's
not
enough
context.
If
you
show
a
lot
of
contacts,
a
lot
of
things
that
are
special
to
your
application,
deeper
down
in
a
file,
you
will
see
that
it.
V
Indeed,
nevertheless,
we
do
want
to
protect
our
users
against
potential
problems
with
this
sort
of
thing.
For
that
purpose,
we
built
a
duplication,
tracker,
it's
not
yet
out,
but
it
will
be
soon.
That
index
is
all
public
source
code
and
it
will
actually
suppress
suggestions
that
have
too
much
overlap
with
existing
code.
U
So
the
model
behind
copilot
was
trained
on
all
the
public
code
and
the
internet.
How
is
this
different
than
other
models
that
might
have
been
created
before
I
believe
copilot's
base
model
was
gpt-3
correct?
How
is
copilot
very,
very
different
from
those
previous
instances
of
source
code,
understanding
and
generation.
V
So
I
think,
as
you
said,
what
is
different
is
the
sheer
scale
are
the
fact
that
it
has
been
trained
or
most
of
the
perfect
source
that
currently
exists
in
the
world.
Personally,
I
find
this
very
exciting.
It's
in
a
way
our
co-pilot
embodies
the
collective
knowledge
of
the
entire
programming
community.
U
V
U
V
V
What
is
possible
with
this
type
of
technology,
coconut
as
it
is
today,
does
that
helps
you
create
a
new
code?
Your
writes
on
our
comments
in
english
and
as
we'll
write,
the
quote
the
codes
to
come
with
it
for
you,
but
talk
about
the
other
way
around.
You
write
some
code
and
you
ask
the
ai
to
explain
it
to
you.
It
actually
writes
the
comments.
It
writes
the
explanation.
V
V
P
Suggest
maybe
a
better
way.
V
Of
implementing
this
particular
function-
or
indeed
perhaps
you
want
to
include
some
extra
comments
here,
because
this
is
a
little
bit
difficult
to
read.
So
we
see
applications
of
artificial
intelligence
everywhere
in
the
development
process
and
we
released
a
first
example
of
what
can
be
done,
but
much
more
instagram.
U
V
U
It's
so
good
to
have
spoken
with
you
today
and
I
learned
a
ton
thank.
U
You
know,
co-pilot
is
something
that
I
wish
I
had
had
when
I
was
first
learning
how
to
program
as
a
planetary
scientist
and
I'm
confident
that
it
will
unlock
superpowers
and
create
opportunities
for
folks
who
might
not
necessarily
see
themselves
as
developers
today.
Copilot
is
under
heavy
development
and
the
improvements
are
driven
by
every
single
developer
that
uses
it
and
you're
helping
us
make
it
safe
so
sign
up
today
for
the
preview
on
copilotub.com.
L
So
folks
we're
wrapping
up
the
live
broadcast
but
day
one
is
not
over.
Yet
we
have
live
sessions,
starting
in
about
30
minutes.
We
also
have
loads
of
on-demand
sessions
available
for
viewing
so
head
over
to
the
schedule
to
see
all
of
that
great
content.
So
we've
had
some
pretty
amazing
talks.
Today
we
have
the
great
keynote
led
by
nat
this
morning
to
share
our
vision
and
show
the
future
of
software
development.
R
M
What
a
great
day
one
we've
had,
if
you
enjoyed
our
session
on
github
actions,
today,
be
sure
to
check
out
these
on-demand
sessions
available
to
you
anytime,
once
you
register,
and
if
actions
isn't
your
thing,
we
have
a
lot
of
other
live
content
for
you
to
explore
all
of
day
one's
main
broadcast
material
as
well
as
any
other.
On-Demand
content
is
available
for
re-watch
at
githubuniverse.com.
M
If
you
sign
up
for
one
of
our
live
interactive
sessions,
they'll
be
starting
in
about
30
minutes
after
an
awesome
live
coding.
Performance
space
in
our
interactive
sessions
is
very
limited,
so
as
a
favor
to
your
fellow
attendees,
if
you
can't
attend,
please
remember
to
remove
yourself
from
the
session
to
open
up
seats.
M
Also,
don't
forget
to
use
the
watch
party
kit
to
maximize
your
experience
at
universe.
It
includes
trivia,
prompts
and
an
octo
catapults
challenge.
You
won't
want
to
miss
yes,
octo
catapults,
and
if
you
would
like
to
get
your
hands
on
some
limited
edition
universe,
2021
swag,
head
over
to
the
github
shop
at
thegithubshop.com,
we've
got
a
thrilling,
lineup
plan
for
you
tomorrow
around
the
theme
of
the
interconnected
community.
Well,
where
we
will
be
opening
with
a
keynote
from
erica
brusha
and
have
talks
exploring
devops,
github
actions,
developer
experience,
security
and
more.
M
L
So
y'all
I
am
terrible
at
goodbyes,
but
fortunately
today
all
I
have
to
say
is
hasta
manana,
because
tomorrow
is
day
two
of
get
up
universe
2021,
but
just
because
we're
signing
off
doesn't
mean
universe
stops.
Remember
we
have
a
giant
library
of
demand
on
demand
sessions
available
now
and
we
have
our
live.
Interactive
sessions
happen
in
about
30
minutes,
so
we
talked
today
about
how
github
is
committed
to
both
the
big
and
small
things
to
make
developers
work
life
better.
L
We
also
care
about
the
big
and
small
ways
that
we
can
make
universe
better
for
you
too.
So
please,
please,
please
just
take
a
few
minutes
to
complete
our
super
short
day.
One
survey
that
you
can
find
in
discussions.
Let
us
know
how
we're
doing
and
how
we
can
raise
the
bar
and
now
to
entertain
you
before
the
live
sessions
kick
off.
We
have
our
wonderful,
live
coding,
artist,
justine
and
r
tyler
thanks.
So
much
folks
and
we'll
see
you
tomorrow
for
day
two
of
get
up
universe,
2021.