►
Description
Presented by Jarryd McCree, Senior Product Manager, Business (GitHub).
GitHub has shipped a lot of features in the past few months that you might not even know about. In this talk, I will show you some features that we’ve added to GitHub that you might not have known about, how you can use them as part of your day to day workflows, and dive a bit deeper into some of the new features we shared in our keynote.
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
A
Hello,
everyone:
how
are
you
today
there
we
go!
It's
good,
some
energy
in
here,
I'm
gonna,
be
honest,
I,
never
think
about
my
feet
more
than
what
I'm
walking
up
onstage,
because
I'm
always
expecting
to
fall
and
it
didn't
happen.
That
means
it's
gonna
be
great.
Today,
I
didn't
fall
all
right,
so
I
want
to
start
out
by
thanking
two
groups
of
people.
First,
all
of
you.
Thank
you
so
much
for
coming
out.
Thank
you
for
coming
to
universe.
Thank
you
for
coming
to
this
speech.
A
The
second
group
of
people
are
the
developers
behind
all
of
the
features
I'm
about
to
show
you
I'm
just
a
face.
I'm
the
one
speaking
about
this,
but
I
didn't
write
any
of
this
code.
It
took
hours
of
work
by
developers
by
QA
by
support
I,
don't
think
they
get
thanked
enough.
So
I
hope
if
you're
watching
I
want
to
thank
all
of
you
for
all
your
hard
work.
Thank
you
so
much
through.
A
So
my
name
is
Jared
McRae
and
I'm.
A
senior
product
manager
here
at
github,
I'm,
a
developer
by
trade.
I
remember
the
first
app
I
made
was
a
tic-tac-toe
app
in
C++
in
middle
school
and
as
soon
as
I
did.
That
I
was
like.
This
is
the
best
thing
in
the
world.
If
I,
if
I
code
it
right,
it
works.
If
it
doesn't,
then
I
failed.
I
can
accept
that
I
got
hooked
on
to
that.
I
got
hooked
on
to
creating
things
prior
to
joining.
A
Github
I
was
a
founder
and
CTO
of
multiple
startups
back
in
my
home
in
Atlanta,
and
they
were
in
multiple
industries
they're
in
social
media.
They
were
an
electronic
signature
they're
in
legal,
it's
across
the
board,
but
at
the
core.
Besides
people
who
are
the
most
important
part
of
any
company,
github
was
at
the
core,
be
it
making
it
easier
for
me
to
collaborate
on
with
my
distributed
team
or
integrating
with
all
the
services
I
needed
to
run.
A
My
company
github
made
it
easier
and
when
I
got
the
opportunity
to
join
their
company,
I
jumped
at
it
because
I
get
to
give
back
to
a
company
that
helped
me
create
so
many
of
mine.
Now,
when
I
started,
I
thought
I
knew
github
pretty
well,
like
I've
been
using
it
for
eight
years.
I'd
started
a
company
with
it.
I
thought
I
know
everything.
I
was
wrong.
A
There
are
so
many
features
out
here
that
I
wish
I
knew
about
that
could
have
helped
me
run
my
company
better
and
that's
what
I
want
to
focus
on
today
with
you
all
so,
hopefully
you
all
saw
the
keynote.
If
you
did,
you
know
we
released
a
ton
of
features
in
the
past
year.
I
can't
go
through
all
of
them,
but
I
do
want
to
focus
on
the
things
that
the
keys
to
success.
That's
what
I
want
to
focus
on
today.
I'm
gonna
do
that
in
three
specific
areas:
security,
scale
and
collaboration.
A
Now
security
is
essential,
whether
you're
a
small
project,
growing
startup
or
mature,
Enterprise
Security's
key,
and
we
all
know
certain
best
practices
out
there-
that
we
need
to
utilize
use.
Two-Factor
authentication
use
a
password
manager,
restrict
access
to
sensitive
data
to
a
small
group
of
people,
rotate
your
SSH
keys.
We
understand
that,
but
the
questions
we
ask
ourselves
here
at
github
are:
how
do
we
better
protect
your
intellectual
property?
How
do
we
better
protect
your
data?
How
do
we
prevent
fires
now
when
we
go
about
trying
to
tackle
this
very
large
question?
A
First
thing
we
think
about
are
what
are
some
common
developer
practices
used
for
security?
Don't
commit
your
secrets
to
source
control.
We
all
know
this.
This
is
drilled
in
by
every
tech,
lead
every
engineering
manager,
every
CTO,
but
accidents
happen,
and
we
commit
our
secrets,
are
tokens
or
keys
to
source
control.
When
you
do
that,
malicious
code
can
be
injected,
you
commit
a
secret
and
emails
are
now
leaked.
A
You
commit
a
secret
and
now
social
security
numbers
elite
here
in
the
bay
we're
aware
of
the
millions
and
millions
of
dollars
in
fines
that
have
happened,
because
these
tokens
were
committed
to
source
control.
Now
that's
money,
but
what's
the
further
impact
of
that
it's
a
loss
in
productivity,
it
is
a
it,
creates,
developer,
angst
and
angst
among
your
users
and
overall,
it's
a
complete
loss
of
trust
in
your
company.
Now
we
think
about
this.
A
Approximately
300
million
tokens
are
committed
every
single
month
at
17,000
a
day.
Now
that
sounds.
That's
that's
a
lot
of
little
fires
going
around,
but
while
we're
a
collaboration,
company
were
also
a
fire
prevention
company-
and
we
know,
is
this:
we
know
as
a
society
that
having
a
smoke
detector
prevents
you
prevents
a
house
from
burning
down,
and
what
we
want
to
do
is
give
a
smoke
detector
for
free
to
everyone
out
there
and
that's
why
we
released
token
scanning,
then
a
public
public
beta.
A
Today
we
want
to
reduce
the
risk
of
your
credentials
being
leaked
now.
This
is
not
only
helps
our
customers.
It
also
helps
our
providers
now
those
who
are
giving
out
these
keys,
because
it's
also
a
hassle
for
them
as
well.
Now,
what
keys
do
we
scan
for,
of
course,
the
github
ones,
but
we
also
deal
with
our
partners
now.
How
does
it
work?
First
thing
you
do.
A
You
we're
also
working
with
our
data
scientists
to
learn
more
and
better
predict
these
things
to
prevent
these
from
being
leaked.
Now
these
this
is
available
for
all
dot-com
plans
available
for
more
plans.
If
you
want
to
learn
more,
you
can
see
me
or
any
product
manager
after
this,
but
please
please
add
this
to
your
roadmap
today.
A
Now
speaking
of
roadmap,
this
probably
isn't
on
your
roadmap
to
add
token
scanning.
What's
probably
on
your
put
on
your
roadmap
right
now,
Oh,
probably
bugs
that
need
to
get
squashed.
We've
got
features
that
need
to
be
implemented.
We've
got
enhancements
that
need
to
be
made,
but
what's
probably
not
on
there.
A
The
very
very
sexy
dependency
upgrades.
No,
we
don't.
We
don't
add
that
on
there
a
modern
software,
the
majority
of
modern
software,
is
built
on
third-party
libraries,
open
source
libraries.
We
all
know
this
and
but
but
when
you
don't
upgrade
your
dependencies,
you
open
yourselves
up
to
security
vulnerabilities.
These
vulnerabilities
are
damaging
to
your
confidentiality
they're,
damaging
to
the
integrity
of
your
application
and
they're
damaging
to
the
availability
of
your
application.
It'd
be
great
if
we
could
automate
this
right,
but
why
is
that
important?
Why
should
we
automate
dependency
dependency?
A
Upgrades
organizations
that
use
tools
to
automate
dependency
management
have
60%
fewer
security
vulnerabilities
than
those
who
don't
now
identifying
these
vulnerabilities
isn't
enough
to
adequately
reduce
your
risk.
We
are
all
aware
recently
in
the
past
years
of
breaches
that
we've
released
Social
Security
numbers
personal
personally
identifiable
information.
Now
with
some
of
those
breaches,
the
security
vulnerability
was
found
months
ahead
of
time,
but
it
was
not
addressed.
A
How
do
we
fix
that?
What's
automated
automation
equals
peace
of
mind
and
when
you
think
of
github,
we
want
you
to
have
peace
of
mind
and
that's
why
we
released
security
vulnerabilities
last
year
we
released
it
for
JavaScript
and
Ruby.
Earlier
this
year
we
released
did
for
Python,
and
today
you
released
it
for
Java
and.net.
A
Now,
when
we,
when
we
do
this,
we
we
excuse
me.
How
does
this
work
well?
First,
you
need
to
enable
your
dependency
graph,
if
you
haven't
done
that,
please
go
do
that
after
this,
it
Maps
how
a
developer's
repo
depends
on
other
packages
other
repos
across
github.
Now,
when
github
receives
a
notification
of
a
new
vulnerability,
we
are
scanning
all
pub.
A
Now
this
was
released
last
year,
but
we've
also
made
a
ton
of
updates
to
the
UI
and
that's
what
you're
seeing
behind
me
right
now,
when
you
look
in
the
UI,
when
you
look
on
on
your
screen
and
your
repo,
we're
gonna
show
you
what
that
vulnerability
is
we're
gonna
show
you
where,
in
your
code,
that
vulnerability
is
and
we're
gonna
tell
you
the
severity
of
it.
Low,
moderate,
high,
critical
and
no
one
here
is
going
to
ignore
a
critical,
a
high,
a
moderate
or
a
low
dependency
or
a
low
vulnerability.
I'm.
A
Alright,
there
you
go
that's
what
I
wanted
here.
Also
we
made
some
updates
to
the
email,
the
weekly
email
digest
that
we
send
out
letting
you
know
of
the
security
vulnerabilities
in
your
applications
that
sends
out
weekly.
We
do
that
up
to
10
repos.
Now
you
can
update
the
notification,
so
you
get
a
email
every
single
day,
letting
you
know
of
your
security
vulnerabilities
at
github.
We
want
to
be
that
person
tapping
you
on
the
shoulder,
letting
you
know.
Please
fix
these
security
vulnerabilities.
No
more
data
breaches
alright.
A
A
Now,
let's
talk
about
scale
here
at
github,
we
have
a
responsibility,
no
matter
what
stage
your
company
is
in,
to
give
you
the
tools
to
succeed
at
each
stage
of
your
company,
we're
gonna.
We
need
to
address
your
needs,
so
kind
of
a
little
practice
we
went
through
is
to
understand
you
know
what
what
what
does
everyone
need?
What's
the
natural
progression
of
a
successful
company?
So
let
me
tell
you
a
little
story:
we've
got
an
early-stage
company,
the
project,
a
startup
started
in
a
garage
somebody's
office.
A
We
don't
know
it's
a
small
team,
one
team,
one
project,
they're
small
they're,
nimble,
they're
focused
because
they're
also
really
really
smart.
They
use
the
best
collaboration
software
in
the
world,
it
rhymes
with
flood
hub
and
that's
what
we've
done
so
they
keep
maturing
to
keep
grinding
they're
working
hard.
They
get
featured
on
product
I'm
really
exciting,
because
of
that
they
start
getting
a
bunch
of
new
users
that
come
in
now.
Those
users
give
them
a
bunch
of
feedback
and
that
feedback
leads
them
to
open
a
new
product
line.
A
Two
teams,
two
products,
two
orgs:
they
keep
working
harder
to
keep
grinding,
they
keep
learning
and
they
get
we
get
featured
on
TechCrunch
Oh
champagnes
popping
things
are
good
they're
getting
featured
everywhere
now,
they're
getting
money
thrown
at
them
from
left
and
right.
They
decide.
Let's
raise
that
first
round
of
funding
with
funding
comes
new
developers
with
funding.
They
were
able
to
increase
their
velocity
now
they're
able
to
app
open
another
product
line.
A
Three
teams,
three
products:
three
orgs
now
this
entire
time
did
they've
been
releasing
grindin
they've
had
a
rival
just
lurking
in
the
alley.
Every
time
they
release
a
feature
that
rival
copies
them,
they
release
a
bug,
they
jump
all
over
them
in
social
media.
That
was
a
rifle
of
bad
thing.
Batman
needs
to
joke.
Coke
needs,
Pepsi
waffles
need
pancakes,
but
eventually
you
got
to
eat
that
rival
and
that's
what
happens
they
eat
it.
They
acquire
them
for
teams
for
products
for
orgs.
A
Now
they've
been
working
hard,
this
entire
time,
they've
grinded
and
after
a
couple
years
they
look
like
this.
This
is
what
success
looks
like
for
a
lot
of
our
companies.
Multiple
orgs,
multiple
teams,
multiple
projects
with
success
comes
Champaign,
but
also
with
success
comes
some
challenges.
Some
difficulties,
it's
very
difficult
to
be
an
admin
when
you
have
X
number
of
orgs
and
product
lines,
it's
very
difficult
to
collaborate
when
these
instances
aren't
connected
and
it's
very
difficult
to
manage.
Now.
That's
why
you
heard
about
earlier
today
the
github
connect
initiative.
A
It
doesn't
matter
how
many
instances
you
have
on
business
cloud,
because
you're
successful
or
whether
you're
utilizing
the
benefits
of
ghe.
We
want
to
combine
them
together.
We
want
to
make
that
administration
easier
for
you.
We
want
to
unify
that
experience
for
developers.
We
know
that
innovation
happens
with
connection
for
admins
it's
easier
to
map.
We
want
to
make
it
easier
to
manage
your
org,
and
the
first
step
is
unified
business
identity,
which
we
released
today
in
limited
public
beta
for
for
business
cloud
for
admins.
This
makes
it
easier
to
manage
your
multiple
orgs.
A
It
makes
you
more
productive.
It
gives
you
better
visibility
into
your
multiple
organizations
now
the
firt.
This
is
the
first
step
towards
being
able
to
give
you
better
billing,
more
unique
billing
and
being
able
to
manage
your
permissions
and
policies
across
multiple
instances
easier
now,
I'm
talking
about
the
I'm
talking
about
the
admin.
What
about
the
developer?
A
We
know
the
collaboration
equals
innovation
and
innovation
equals
collaboration.
That
happens
because
of
code
reuse,
which
increases
your
velocity.
It
happens
because
of
knowledge
sharing,
which
increases
your
velocity.
It
happens
with
camaraderie,
which
just
makes
you
feel
good
and
increases
your
velocity.
Now
many
of
our
customers.
They
utilize
the
benefits
github
enterprise,
but
with
that
you're
not
able
to
see
you're
not
able
to
search
and
see
what's
happening
on
the
dot-com
side.
A
Now,
that's
why
we
introduced
unified
search,
which
is
available
today,
and
the
first
release
happened
and
get
up
to
14
and
now
we're
making
some
upgrades
in
215.
Now
we're
gonna
show
the
results.
If
you're
on
your
local
ghe
instance,
the
results
that
you
search
for
on
your
local
instance
will
show
up
as
well
as
what's
happening
on
on
github.com.
Now
we
have
two
flavors
of
this
right
now,
if
your
github
enterprise
user
and
you
do
a
search,
all
you
can
see
is
what's
on
that
particular
instance.
But
that's
2017-2018.
A
We've
got
new
stuff.
We're
gonna
do
the
first
delicious
favor
flavor.
If
you,
if
you
unified
search,
you
can
have,
you
can
search
everything.
That's
on
public
calmed,
github,
calm
public
and
your
ghe
instance.
That's
flavor,
one
with
flavor
two.
You
get
everything
in
flavor,
one
plus
you're,
able
to
see
everything.
That's
on
your
business
cloud,
business
cloud
instance
as
well.
A
Now,
how
does
this
work?
What
you're
seeing
here
is
a
user
or
a
knight,
an
admin,
who's
turned
on
unified
search
in
their
settings
now,
they're
searching
for
Hodor
rest
in
peace
and
he's
seeing
results
from
both
github
enterprise
and
github
calm.
What
you're
also
seeing
is
the
advanced
search
option
for
those
who
want
to
just
specify
I
only
want
results
from
my
ghe
instance
or
I
only
want
results
from
calm
you're
able
to
do
that
as
well.
Now,
what
we've
also
released
today
is
Advanced
Search
prefixes.
A
If
you
don't
like
using
advanced
search
your
power
user-
and
you
want
to
just
use
that
top
search
bar,
we
can
add
we-
you
can
have
prefixes
to
search
exactly
which
instance
you
want
what
libraries
you
want.
All
of
that,
and
you
can
read
more
about
that
on
the
help
Docs
or
talk
to
me
after
this
now
we're
talking
about
the
ghe
developer
and
I
I'm
gonna
share
another
story
with
you,
I
heard
about
this.
This
developer
she
had
been
working
at
this
company
like
five
or
six
years.
A
She
started
out
as
a
junior
worked,
her
butt
off
became
a
senior.
Did
she
stop
there?
No,
she
wants
to
be
full-stack,
so
she
came.
She
also
became
a
worked
on
the
services.
The
back-end
development
worked.
Her
butt
off
even
further
became
a
senior
dev
a
year
later
now
she's
an
architect.
Now
me
being
curious
and
nosy
I
want
to
learn
more
about
her
I'm
at
github.
I'm
gonna
go
check
on
her
profile.
I'm
gonna
see
what
she's
done
it's
empty.
It's
nothing.
A
Now
earlier
developers
demanded
that
contributions
made
in
private
repos
that
they
are
shown
on
their
public
profile.
We
didn't
want
to
stop
there.
We
know
how
many
people
are
common
in
coding,
reviewing
denying
for
requests
and
github
enterprise
and
they
want
their
contributions
shown
on
github.com
and
that's
why
we
released
unified
contributions
for
business
cloud
and
github
Enterprise.
There
are
so
many
developers
out
there
right
now
who
are
grinding
and
not
getting
credit
for
their
work
and
that's
what
we've
released
today.
A
Now,
what
have
we
talked
about
today?
We
have
talked
about
security,
token
scanning
and
security
vulnerabilities,
which
are
all
going
to
add
to
your
roadmap.
After
this
we've
talked
about
get
up
connect.
We
want
to
unify
that
experience,
regardless
of
which
instances
you
have
now
we're
gonna
talk
about
collaboration,
so
I've
talked
a
bit
about
collaboration
collaboration
today,
I've
said
that
it's
key
to
innovation.
What
I
haven't
talked
about
is
that
collaboration
is
really
hard
to
do
that.
You
have
to
have
good
documentation.
A
You
have
to
be
committing
code,
you
have
to
be
removing
code,
you
have
to
be
up-to-date
on
all
the
new
technologies
that
are
out
there
now.
We
know
these
are
questions
that
you
ask
yourselves
within
your
own
projects
within
your
own
companies,
but
these
are
questions
we
ask
ourselves
internally
here
at
github
as
well.
Github
is
65%
remote
employees,
so
collaboration
is
super
super
key
to
our
success.
Now
again
we're
developer
first
company.
We
want
to
think
about
what
are
the
things
the
developer
thinks
about
when
they're
using
github
when
they're
going
to
work.
A
Now
that
list
is
endless.
What
issue
was
I
working
on
yesterday?
Did
I
open
a
pull
request?
Did
I
deny
a
pull
request?
Do
I
need
to
update
my
dependencies
where's
that
where's,
a
cat
video
I
found
on
reddit,
did
I
get
that
mentioned.
Do
I
need
to
fix
that
bug
from
yesterday?
What
tools
do
I
need
to
use
now
did
I?
Oh
man
did
I
use
github
actions.
I
should
use
github
actions
to
have
a
merge
conflict.
Did
my
test
fail?
What
what's
the
news?
A
What's
that
new
open
source
tool
that
I
need
to
use?
The
questions
that
we
want
to
answer
are:
where
is
my
attention
needed
now,
whether
you're
starting
your
day,
coming
back
to
it
or
closing
out
and
that's
why
we
release
the
developer
dashboard,
which
is
available
today
for
free
for
everyone
on
dot-com
plans?
Now
how
do
you
access
that?
For
those
who
are
on
your
computer
right
now
go
to
github.com?
There's
this
beautiful
little
octa
kitten
in
the
top-left.
All
you
got
to
do
is
click
there
and
you'll
see
the
developer
dashboard.
A
Now,
there's
three
different
groups
that
I'm
going
to
focus
on
today
on
that
developer,
dashboard,
it's
recent
activity
started
repositories
and
it's
Activity
Feed,
so
recent
activities,
recent
activity,
I,
will
admit.
I
have
an
addiction.
I
didn't
want
to
do
it
publicly,
but
I'm
just
gonna
state.
It
I
have
far
too
many
tabs
open
on
my
computer
I'm,
really
hoping
I
take
that
out
before
you
see
I
have
before
the
developer
dashboard.
A
Add
a
tab
open
for
ten
pr's
for
twenty
issues,
for
that
video
and
reddit
I
told
you
about,
but
what
we
want
to
fix
with
that
with
the
recent
activity
board
is
for
those
who
have
that
tab
addiction
like
me,
we
want
to
make
it
easier
to
get
back
to
what
you
were
doing.
If
you
go
into
your
developer
dashboard
and
you
look
under
on
your
recent
activities,
what
we're
trying
to
show
you
is
the
most
relevant
content
to
you
right
now.
A
This
is
going
to
be
pull
request
and
simple
requests
are
ones
that
you
were
mentioned
in.
These
are
issues
that
you've
opened
or,
or
you
been
commented
on
anytime,
you've
been
at
mentioned-
we're
going
to
show
that
in
that
developer,
dashboard
in
the
recent
activity,
crew,
now
we're
continually
learning
and
working
with
our
data
scientists
to
make
sure
that
we're
presenting
to
you
the
most
relevant
content
by
right
now,
we're
showing
you
five
at
most,
but
this
is
expandable.
You
can
click
a
little
button
on
the
bottom
and
it'll
show
you
more
now.
A
The
next
is
starred
repose.
Now
we
added
the
ability
to
star
repose
earlier,
but
most
of
you
don't
have
five,
you
have
ten.
We
have
20,
we
have
a
hundred.
What
we
want
to
do
is
show
you
the
most
relevant
repose
here
now.
These
are
gonna,
be
based
on
the
amount
of
time
that
you
spend
in
them
and
by
time
we
mean
you've
done
actions
on
this
particular
repo
or
ones
that
have
had
recent
activity.
Your
coworker
at
mentioned
you
on
something.
A
Now
we
also
wanted
to
show
you
the
team
now
you're
out,
you're
gonna,
be
part
of
many
many
teams.
We're
gonna
show
you
the
most
relevant
once
here
again,
based
on
the
time
you
spent
and
recent
activity,
and
if
these
aren't
shown
you're
able
to
search
again
we're
trying
to
show
you
the
most
relevant
information
possible
now
the
last
is
the
Activity
Feed.
Now
we've
seen
activity
feeds
in
many
different
flavors,
but
the
last
thing
we
wanted
to
do
is
give
you
a
firehose
of
information,
that's
not
usable.
A
So
what
we've
done
is
group
these
events
into
what
we
feel
is
most
relevant
for
you.
You
got
a
stack
of
PRS
that
you
need
to
review
we're
gonna
group,
those
together.
You
have
issues
we're
gonna
group,
those
together
now,
we've
also
added
the
ability.
We've
had
this
for
a
while
to
follow
people.
Now,
people
use
this
to
stay
up
to
date
on
open
source
community
updates
to
just
stay
up
to
date
with
people
that
you,
your
colleagues
or
coworkers.
A
Want
to
talk
to
you
all
about
github
desktop,
so
we
redesigned
this
and
re-released
it
last
year
purely
an
electron.
The
reason
we
wanted
to
do
this
was
to
unify
that
experience
for
to
have
the
same
or,
as
you
would
expect
experience
in
both
on
both
Mac
and
Windows,
and
we
open
sourced
this
from
the
beginning.
Open
source
is
at
the
core
of
github
and
for
our
products.
We
wanted
to
make
sure
that
we
did
that
as
well.
It's
a
community
driven
project
and
400
PRS
have
been
open
from
people
who
are
not
github
employees.
A
250
of
those
have
already
been
merged
in
that
comes
out
to
1,000
commits
made
by
people
who
don't
work
at
github
to
this.
To
this
application
and
I
want
to
thank
all
of
them.
Now,
we've
released
a
ton
of
features
for
forget
or
forget
of
desktop,
but
I'm
gonna
highlight
a
couple
of
them
today.
So
most
of
you,
regardless
of
your
project,
if
you're
working,
a
small
project
or
an
enterprise
you've
had
a
situation
where
developer
is
training
a
junior
developer.
A
Now,
if
you're
smart
we're
going
to
use
Adam
with
teletype,
so
you
can
both
be
on
two
separate
computers
typing
on
the
same
file.
At
the
same
time,
it's
really
cool
and
you
all
should
use
it
now.
Let's
say
you're
working
through
your
you're
pairing
with
this
new
developer,
you've
been
working
on
a
couple
files,
and
now
it
comes
time
to
commit
who's.
The
author
of
that
commit
is
it
the
junior?
Is
it
the
senior?
A
Wouldn't
it
be
great
if
you
both
could
be
on
that
commit
and
that's
what
we've
added
with
co-authoring
now
what
you're
seeing
here
is
the
ability
directly
with
in
github,
desktop
to
write
your
commit
message
and
then
add
two
of
multiple
authors
to
that
particular
commit
message.
What
you're
also
seeing
here
is
ability
directly
in
github,
desktop
to
be
able
to
see
who
comma
you
can
see
the
commit
history
and
see
who
co-authored
it.
A
Now,
in
addition
to
that,
what
you're
seeing
in
the
lower
right
is
the
CI
status
you're
able
to
see
that
directly
from
github
desktop,
and
so
you
can
see
if
your
CI
is
pending,
you
can
see
if
it's
exceeded,
you
can
see
if
it
failed
and
if
it
failed.
You
can
blame
that
junior
developer
and
say
why
did
you
add
me
as
a
co-author?
A
Now
that's
awful
awful
don't
do
that.
One
of
my
favorite
features
of
github
calm
is
syntax,
highlighted
diffs.
I
love
regardless
of
what
language
I'm
putting
it
in
I'm
coding
in.
I
can
actually
see
the
difference
between
well
when
I
committed
and
when
I
didn't
now,
wouldn't
it
be
cool.
If
we
added
that
to
get
hub
desktop,
I
think
it
would,
which
is
why
we
did.
You
can
see
that
directly
in
github
desktop.
You
can
see
without
even
going
to
a
browser.
A
A
There
is
a
very
common
developer
practice,
which
is
called
commit
early
commit
often
now,
let's
go
through
the
typical
day
of
some
of
the
developers.
I've
talked
to
you
show
up
in
the
morning.
You've
got
your
three
cups
of
coffee
in
you
already.
You
love
caffeine.
You
start
working
on
that
first
feature
and
that
you
were
working
on
yesterday.
You
saw
it
in
the
developer
dashboard,
so
you
could
easily
pick
it
back
up.
So
you
go
to
your
stand
up.
Yatta
Yatta,
Yatta,
15
minutes,
you're
ready.
A
Now
you
have
a
bug
that
you
need
to
work
on
as
well.
Alright,
let's
fix
that
bug.
I'm
gonna
go
to
lunch,
grab
a
burrito.
You
come
back
now,
you're
working
on
another
feature.
Oh
man,
I
didn't
document
that
first
feature
I
did
earlier
this
morning.
Alright,
let
me
go
back.
We
go
back.
I'm
gonna,
go
document
that
now
you
got
one
more
thing
you
need
to
do:
oh
yeah!
Let
me
squash
that
bug
real
quick,
so
couple
lines:
okay,
it's
the
end
of
your
day.
Okay,
you
didn't
make
one
commit
all
day.
A
You
got
15
files,
each
so
you're,
gonna
stash
your
changes,
you're
gonna
commit
you're
gonna.
Make
sure
that
every
single
thing
that
you've
worked
on
every
bug
every
feature.
Every
enhancement
has
its
own
commit
right
right,
no
you're,
not
gonna,
do
that.
You
got
like
ten
episodes.
Aren't
you
DVR'd
you're,
making
one
commit
message
and
then
you're
gone
you're
done.
Wouldn't
what
can
get
up
help
me
with
this
yeah
yeah?
We
can
help
you
with
this.
What
we've
added
is
partial,
commits,
let's
say,
you're
working
on
20
different
files.
A
At
a
time
you
just
want
to
be
able
to
like
say
this
was
for
this
bug
commit
message.
This
was
for
this
feature
commit
message.
This
is
for
this
documentation.
You
can
do
that
all
from
github
desktop
now
what
you're
seeing
here
is
all
the
features
for
github
desktop
that
I
talked
about.
You
can
see
co-authoring,
you
can
see
syntax
highlighted
diffs,
you
can
see
partial
commits
I
lied.
You
can't
see
the
status
of
the
CI
I
should
have
added
this
here,
but
you
can
see
everything
else
now.
What
have
we
focused
on?
Today?
A
We
talked
about
security.
We
talked
about
scale,
we
talked
about
collaboration,
but
security.
Please
everyone!
Let
us
prevent
data
breaches.
Let
us
do
better
as
a
community.
Oh
use
token
scanning
use
security
vulnerabilities
today
or
tomorrow,
but
preferably
like
right
after
this
scale.
We
are
making
sure
that,
regardless
of
how
many
instances
you
have
no
matter
how
successful
you
are
and
you're
all
going
to
be
successful,
we're
gonna
unify
that
experience
with
unified
business
identity,
unified
search
and
unified
contributions
and
for
collaboration.
A
We
want
to
make
sure
that
whenever
you
come
back
to
github,
whenever
you
come
back
to
work,
you
were
able
to
pick
up
where
you
left
off.
Where
is
your
attention
needed
most?
That's
what
we
want
to
answer
and
last,
but
definitely
not
least,
use
github
desktop.
It
makes
things
so
much
easier,
so
everyone
I
want
to.
Thank
you
so
much
for
your
time
today.
Thank
you
for
coming
to
universe,
I'm,
happy
to
answer
any
questions
after
this.
Thank
you
all.