►
Description
Presented by Jarryd McCree, Senior Product Manager at 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, 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
Lo,
how
are
y'all
doing
today?
I
love,
excitement
in
here
alright
folks,
my
name
is
Jared
McCree
and
I'm.
A
senior
product
manager
here
at
github
and
today
we're
gonna
do
a
deep
dive
into
some
of
the
newest
features.
We've
released.
I
was
able
to
do
this
talk
last
year,
so
I'm,
incredibly
fortunate,
excited
and
happy
to
do
it
again.
A
So
in
my
professional
career,
I've
been
a
developer,
I've
been
a
product
manager
been
a
start-up
founder
and
a
consultant
I
got
to
tell
you
I,
love
being
a
product
manager,
I
love
diving
into
the
UX,
with
a
design
team
and
then
going
through
the
day-to-day
with
my
engineering
team.
But
all
this
starts
out
with
my
favorite
part
of
the
job,
which
is
talking
with
customers
like
you.
Fortunately,
here
at
github
I've
been
able
to
work
with
a
wide
array
of
different
customers.
A
A
Product
managers
are
storytellers
too,
and
it's
probably
what
attracted
me
to
being
a
product
manager
in
the
first
place,
because
I've
loved
I've
loved
stories
since
I
was
a
kid
video
games,
movies,
fiction,
nonfiction
loved
them
all
I
remember
when
I
was
in
elementary
school
and
the
Scholastic
Book
Fair
came
around
I
always
asked
my
parents
for
a
bunch
of
money,
so
I
could
get
a
big
stack
of
books
and
somehow
they
always
had
enough
money
for
that.
But
I
really
think
that
laid
the
groundwork
for
me
being
a
storytelling
PM.
A
So
again,
we're
gonna
go
into
a
bunch
of
our
newest
features
and
when
I
thought
about
how
to
shape
this
talk,
I
thought
about.
What's
the
most
coherent
story,
I
can
tell
you
what
is?
How
can
I
present
this
material
in
a
logical
manner,
so
that
you're
able
to
have
actionable
steps
when
you
walk
away
because
the
goal
of
this
speech
and
what
I
want
you
to
all
to
be
able
to
walk
away
with
is
having
actionable
steps.
That'll
help
you
and
your
project
or
your
business.
A
So
I'm
gonna
tell
you
a
series
of
stories,
a
series
of
stories
on
the
features
that
we've
made,
how
we
built
them
and
why
we
built
them.
So
the
name
of
this
talk
is
deepest
dive
into
our
newest
features
and
we've
released
a
hundreds
of
things
in
the
past
year,
so
I
can't
go
through
them
all.
So
when
I
was
thinking
about
which
ones
to
choose
I
thought
about
who's,
gonna
be
here
in
the
audience.
A
You
know,
we've
got
press
we've
got
developers,
we've
got
executives
and
because
it's
github
I
know
someone's
dog
is
stuffed
around
here
somewhere,
but
for
today,
I'm
gonna
talk
about
three
distinctive
people:
three
specific
personas,
the
developer,
the
project
manager
in
the
enterprise
owner
now
many
of
the
features
that
I'm
gonna
walk
through
they
apply
to
more
than
one
persona,
that's
okay.
What
I'm
gonna
talk
about
is
how
this
particular
feature
applies
to
this
particular
persona
and
I'm.
Gonna
start
off
with
the
developer.
A
Now
you
probably
heard
in
the
keynotes
and
the
speakers
before
our
goal
is
to
be
the
home
for
all
developers,
not
just
hobby
devs,
not
just
architects,
not
just
security
minded.
Folks,
the
home
for
all
developers-
and
everyone
in
this
room
is
a
developer,
whether
you
code,
right
now
or
not
now
I
get
to
talk
with
a
lot
of
new
developers,
and
it's
it's
always
sobering
for
me
to
do
that.
You
know
some
are
in
school,
some
are
trying
to
create
a
new
product
or
first
startup,
and
some
are
looking
for
a
career
change.
A
Now
all
of
them
have
the
exact
same
question:
where
do
I
even
start
now
we
have
40
million
developers
who
work
who
use
github,
and
it
would
be
very
easy
for
us
to
think
that
everyone
knows
git
or
github
and
that's
absolutely
not
the
case.
Github.
We
have
a
responsibility
to
help
you,
regardless
of
your
skill
level.
We
want
to
help
new
developers.
Take
that
first
step
I
mean
the
four
things
we
want
to
teach
especially.
Are
you
know?
How
do
you
use
git?
A
What's
the
correct
merging
flow,
how
do
you
use
pull
requests
and
comments?
How
do
you
set
up
an
IDE
or
what
is
an
ID
even
so
github
desktop
is
an
open
source,
cross-platform
application
that
brings
github
into
your
local
device
environment
and
it's
available
for
the
low
low
price
of
free
today
and
you
can
download
it
at
desktop,
die
github,
calm
now
get
up
desktop,
isn't
a
replacement
for
get
up
calm.
It
just
meant
as
a
tool
to
allow
you
to
be
more
productive.
A
We
understand
that
git
can
be
intimidating,
especially
for
new
developers
and
github.
Desktop
is
designed
to
make
interactions
with
get
more
approachable
and
easier.
Now
the
Godot
desktop
desktop
team
has
been
doing
a
lot
of
research
and
do
their
research.
They
learn
that
most
people
learn
get
from
a
buddy,
be
it
a
friend,
a
co-worker,
a
professor
or
even
a
youtube
video.
A
Now,
based
on
that
feedback,
we
created
a
git
and
github
tutorial
to
be
your
buddy,
and
so,
let's
take
a
look
at
it
right
now,
when
you
download
get
up
desktop
for
the
first
time,
you're
gonna
see
a
little
button
on
top,
it
says,
create
a
tutorial
repository
at
this
phase.
We're
focused
on
two
things:
one
creating
a
repository
and
two
connecting
an
editor
there's
many
tools
that
you
need
to
get
set
up
encoding,
but
getting
an
IDE
getting
a
code
editor
set
up.
A
Is
it's
one
of
the
first
things
you
need
and
if
you
needed
a
any
advice
on
one
I
highly
recommend
Adam
this
little
company
called
github
made
it
and
maintains
it.
So
I
highly
recommend
that,
after
that,
we're
gonna
walk
you
through
the
github
flow.
It's
a
branch
based
workflow
that
supports
collaboration
and
the
steps
that
you're
gonna
go
through
after
that
are
creating
a
new
branch,
making
a
change
to
a
file
committing
it
and
then
pushing
it
up
to
github.
Now.
A
All
of
this
is
leading
up
to
the
beautiful
thing
that
we
like
to
call
the
pull
request
now.
I
know
we
all
mostly
probably
know
what
a
pull
request
is,
but
just
as
a
quick
refresher,
refresher,
a
pull
request
provide
a
forum
to
discuss
proposed
changes
on
a
branch
before
you
merge
them
in
now,
before
pull
requests,
you
know
it's
actually
getting
new
code
into
a
branch
was
kind
of
a
pain
in
the
butt.
If
you
worked
on
a
team,
you
had
to
bring
your
changes
and
locally
you
had
to
test
them
find
out.
A
If
what
changes
you
needed
go
to
a
meeting
in
real
life
with
your
team,
discuss
them,
go
back
to
your
computer,
make
those
changes
and
do
that
whole
cycle
again
before
you
actually
were
able
to
commit
that
branch
to
master
now.
Meeting
with
your
team
is
in
real
life
is
wonderful,
but
you
lose
a
lot
of
productivity
and
the
benefits
of
pull
requests
are
you're
able
to
assign
and
make
reviews,
add,
integrations
and
we're
remotely
it's
a
great
tool
for
for
a
remote
team
and
to
be
a
very
distributed
team.
A
Now
all
features
evolve
and
pull
requests
have
been
out
for
a
long
time
and
the
natural
evolution
of
pull
requests
were
work
in
progress.
Prs
now
work
in
progress,
pull
requests
there
I
mean
there's
a
couple
different
reasons.
People
did
that
you,
you
would
open
them
to
show
progress
on
on
work,
but
not
necessarily
need
feedback.
You
may
be
experimenting
with
something
and
you
don't
intend
to
merge
it
or
you
open
a
PR
with
no
code.
You
know
just
to
start
a
discussion
now.
A
The
problem
with
you
know:
work-in-progress
PRS
is
you
always
have
to
tag
it?
You
always
have
to
add
that
WIP
in
the
top
and
a
title,
if
you
have
code
owners
on
a
pull
request
as
soon
as
you
open
that
PR
they're
getting
paint,
and
at
that
time
you
don't
need
them
to
review
so
once
you
need
them
to
actually
perform
a
grouper
view,
you
have
to
ping
them
again
and
if
you
have
CI
running
it
can
be
a
very
expensive
and
you
don't
necessarily
need
it
at
that
time.
A
So
we
wanted
to
save
you
time
here
at
get
up,
so
we
created
draft
PRS.
Now
these
are
available
right
now
on
comm,
as
well
as
github
and
a
price
server.
There's
many
wins
and
many
advantages
to
this.
But
there
are
three
specific
big
wins:
I
want
to
talk
about
for
work-in-progress
PRS
one.
They
automatically
tag
it
and
you're
automatically,
showing
your
team
that
this
is
in
draft
status,
and
this
is
something
that
you
can.
You
can
use
throughout
every
team
if
you
use,
if
you're
in
multiple
teams
or
multiple
orgs.
A
Some
may
put
WIP
in
the
top.
Someone
may
say:
do
not
merge,
but
having
draft
PR
is
a
common
practice.
Did
you
be
able
to
use
throughout
all
your
organizations?
It
also
prevents
accidental
merging.
You
cannot
merge
a
draft
PR.
It
has
to
go
into
ready
for
review
status
and
it
obviously
reduces
unneeded
notifications.
So
change
is
good.
The
change
is
also
very
hard
and
we
wanted
to
reduce
the
friction
to
adopt
in
this
feature.
So
we
put
it
directly
in
the
same
button
as
regular
PR.
A
Just
click
on
that
drop
down
on
the
right,
select
draft,
PR
and
now
you've
opened
your
draft
pull
request
and
again.
This
is
a
repeatable
pattern
that
you
can
use
throughout
all
your
different
orgs
and
your
teams.
Now
this
doesn't
break
how
you
code
it
doesn't
break
how
you
commits
all
of
that
is
exactly
the
same
as
soon
as
you're
ready
to
use
a
mark
that
draft
pull
request
is
ready
for
review.
You
just
click
on
ready
for
review
and
that's
when
the
the
feedback
starts
now
I
want
to
pull
request.
A
As
you
all
know,
there's
there's
many
types
of
feedback.
You
get
sometimes
people
come
in
and
say
this
is
great
or
you
need
a
test.
Sometimes
they're
saying
this
is
great
approved,
and
sometimes
it's
not
so
positive,
I
think
my
favorite
pull
request
comment
I've
ever
gotten.
That
was
up
to
like
three
in
a
morning
coding
one
time
and
I
woke
up,
and
the
PR
comment
was
at
Jared.
A
This
is
the
hottest
of
garbage
smiley
face
emoji
yeah,
but
that's
what
happens
now,
sometimes
as
a
reviewer
when
you
come
in,
you
know
exactly
what
needs
to
be
changed
like
sometimes
it's
a
typo,
sometimes
it's
linting.
Sometimes
you
actually
know
what
code
needs
to
be
added
in
now,
adding
these
changes
can
be
cumbersome.
You
you
have
to
copy
that
line,
put
it
in
a
comment
and
then
the
author
actually
has
to
come
back,
go
into
their
local
environment,
paste
that
code
snippet
and
then
push
it
back
up.
A
A
What's
great
is
that
the
reviewer
is
added
as
a
co-author.
So
in
your
contribution
graph,
you
actually
get
credit
for
making
that
suggested
change,
and
this
is
available
today
on
enterprise
cloud
as
well
as
github
Enterprise
Server
for
all
those
Enterprise
folks
out
there.
This
doesn't,
it
doesn't
break
any
existing
workflows.
It's
just
a
great
painkiller
feature.
This
saves
time
for
both
developer
and
the
reviewer.
A
Now
again,
as
I
talked
about
earlier
features
evolved
and
based
on
that
feedback
that
you
all
gave
us,
you
said
that
you
love
this,
but
you
want
more
now
the
feedback
said
that
there's
a
lot
of
noise
when
accepting
a
lot
of
different
changes.
For
example,
if
you
have
30
different
suggested
changes
in
a
pull
request,
that's
30
different
commits
and
the
universal
feedback
was
that
you
wanted
to
batch
all
of
those
together.
A
So
we
we
added
the
ability
to
add
suggestions
to
a
batch
this
way,
if
you
have
multiple
suggestions,
or
maybe
three
or
four
that
actually
need
to
be
added
at
the
same
time,
so
you
can
have
clean
history,
you
can
do
that.
One
of
the
people,
one
of
the
pieces
of
feedback
we
got
was
that
for
certain
functional
programming
languages,
if
you
only
commit
one
suggested
change,
but
not
to
others,
it
actually
breaks
the
application
so
now
you're
able
to
add
them
all
to
a
batch
and
then
commit
them
as
one
single
commit.
A
So
at
this
point
we
talked
about
get
a
desktop
using
PRS,
reviewing
getting
them
merged,
you're
doing
work
now
for
any
developer.
You
need
to
be
able
to
track
that
work
and
you
do
that
using
user
owned
project
boards.
Now
why
the
heck
am
I
talking
to
you
about
project
boards?
There's
plenty
of
apps
out
there
to
do
it.
Project
boards
aren't
new.
Well,
the
feedback
we
got
was
that
our
project
boards
weren't
enough,
for
example,
you
need
to
manage
your
own
work.
Sometimes
it
originally
project
boards
were
only
tied
to
a
repository.
A
So
if
you're
working
on
projects
across
multiple
repos,
it
wasn't
very
easy
to
use
that,
especially
if
you're
in
multiple
teams
and
also
the
piece
of
feedback
we
got
was
that
you
wanted
to
manage
in
your
own
style.
If
you're
in
a
repo,
not
your
own
personal
project,
you're
kind
of
tied
to
whatever
style
they
want.
You
want
to
be
able
to
manage
that
work
in
your
own
way.
Now
the
solution
that
we
made
makes
it
so
you
don't
need
to
be
tied
to
a
repository.
You
can
organize
and
plan
in
your
own
style.
A
You
can
do
this
all
within
github.
We
want
to
be
the
home
for
all
developers
and
if
you
have
to
go
to
an
outside
application,
to
track
your
work
you're,
not
at
home
anymore,
so
this
is
available
on
comm
as
well
as
Enterprise
Server.
It's
super
easy
to
set
up
go
to
your
profile
page,
which
is
get
up.
Comm,
slash
your
handle
click
on
the
projects
tab
on
the
very
top
from
there
you're
able
to
make
your
project
boards
private.
You
can
make
them
public.
A
You
can
add
in
automation,
with
Kanban
or
Kanban,
depending
on
how
you
like
to
say
it,
but
you
can
also
link
to
any
repository
that
you
have
access
to.
This
makes
it
easier
to
add
issues
and
pull
requests
which
are
related
to
the
repositories
you
you
work
in
and
you're
able
to
track
this
work
for
both
the
open-source
work
you
do
as
well
as
the
enterprise
work
now
project
boards
aren't
meant
to
track
everything
you
get
pinged
on
something
in
a
comment.
A
There's
a
new
feature
that
you
found
in
a
repo
that
you
want
to
use.
There's
a
person
you
want
to
follow
like
you're,
not
gonna,
put
all
that
out
and
then
in
a
project
port,
that's
not
scalable!
So
how
do
you
track
that
you
have
90
million
tabs
open
and
personally
there's
a
huge
problem
for
me:
I
have
intricate
setups
in
Gmail
to
highlight
stuff.
I've
got
too
many
chrome
windows
and
Firefox
windows
with
a
bunch
of
tabs,
and
what
this
told
us
is
that
we
didn't
have
what
you
needed.
You
need
it
home.
A
You
needed
something
better,
so
we
needed
to
overhaul
our
notification
process
now.
My
my
colleague
Becca
talked
about
this
in
the
keynote
earlier,
but
we've
released
this
and
beta
now
the
benefits
of
our
new
notification
program,
our
new
diffic
notification
feature
or
that
it's
a
consolidated
view
for
triaging
and
context
gathering.
You
can
also
similar
to
email.
You
can
mark
things
as
read:
unread,
unsubscribe,
archived
and
even
save
them.
You
can
also
filter
by
project.
A
We
have
a
bunch
of
filters
that
are
available
by
default,
but
you
can
also
create
your
own
custom
ones
to
track
what
you
want
to
now.
Let's
take
a
look
at
what
this
looks
like
so,
as
you
can
see,
this
is
very
similar
to
email
that
you've
seen
before.
If
you
look
on
the
top
left,
you
can
see
with
what's
unread.
What's
in
your
inbox,
you
can
also
save
notifications
to
come
back
to
them
later.
A
We
have
five
default
filters
added
by
straight
out-of-the-box,
but
you
can
add
those
custom
ones
as
you
want
again,
this
is
made
to
help
you
eliminate
tabs
and
hope
you
triage
your
notifications
better.
Now.
This
is
the
first
project
that
I've
mentioned
that
is
in
beta,
and
we
have
a
good
amount
of
features
in
beta.
So
how
do
you
enable
this?
This
is
something
you
have
to
opt
into,
so
what
we
did
for
this
and
it's
a
little
bit
different.
We
created
a
feature
to
enable
this
feature
called
feature.
A
Preview
now
feature
preview
we
added
and
about
two
weeks
ago,
and
we
did
this
to
allow
just
to
have
like
a
very
consolidated
list
of
all
the
features
that
are
in
beta
right
now,
and
what
this
is
enables
you
to
do
is
actually
give
more
consolidated
feedback
on
to
humans.
Like
me
and
other
product
managers
on
the
features
that
we've
released
in
beta,
if
you're
happy,
we
want
to
hear
it
if
you're
unhappy.
We
also
want
to
hear
it
because
we
want
to
make
things
better
here,
get
up.
A
We
staff
staff
ship
everything,
so
we
test
all
of
it
internally,
but
we
also
do
early
access
programs
for
maintainer,
x'
and
such,
but
we
wanted
to
cast
a
wider
net.
We
wanted
to
get
more
feedback
from
all
of
you
users.
So
how
do
you
set
this
up?
You
go
to
your
homepage.
Click
on
the
top
right
on
your
avatar
and
navigate
down
to
feature
preview
from
there.
A
You'll
see
a
list
of
everything
in
beta,
including
the
notifications
that
I
just
mentioned,
you're
able
to
opt
in
turn
it
on
turn
it
off
and
you're
also
able
to
provide
feedback,
and
that
goes
directly
to
our
our
product
team
and
our
engineering
teams,
and
this
gives
a
centralized
place
for
all
that
feedback.
I
was
talking
with
Katie,
who
was
the
product
manager
for
this,
and
she
had
a
great
line
for
that.
I
wanted
to.
Let
you
all
know
when
we
released
stuff.
A
It
matters
to
our
community
and
we
want
to
make
sure
you
have
a
voice.
This
feature
is
here,
so
you
know
that
when
you're
actually
giving
feedback
on
a
particular
feature,
it
goes
directly
to
the
product
manager,
so
that
is
for
the
individual
developer.
Now
we're
going
to
talk
about
the
project
manager
and
what
we
strive
to
be
the
home
for
all
developers.
We
know
that
more
than
just
coders
work
here
and
for
project
managers.
A
We
need
to
make
sure
that
we're
making
tools
to
help
them
now
the
duties
of
the
project
manager
a
little
bit
different
than
the
developer,
and
the
project
manager
you're,
dealing
with
resource
planning,
budget
monitoring,
risk
management
and
organizing
and
managing
a
team,
organizing
and
managing
a
team
on
github.
You
do
that
through
roles
and
permissions.
Now
we
only
had
three
roles
that
you
use
to
manage:
to
manage:
github
who's,
we
read/write
and
admin-
and
you
all
told
us,
that's
not
good
enough.
We
need
more
than
that.
A
We
need
more
fine-grained
permissions,
and
so
it's
satellite.
We
introduced
two
new
roles:
the
triage
and
maintain
rules
which
we've
actually
g8
now
for
both
enterprise
server.
As
well
as
on
cloud
now,
the
triage
role
can
be
thought
of
as
read.
Plus
users
with
this
role
are
able
to
triage
a
repository
without
having
right
access
to
it,
they're
able
to
open
and
close
PRS
and
issues
request,
reviews
from
developers
as
well
as
manage
milestones.
A
On
the
other
hand,
the
maintain
role
can
be
thought
of
as
right,
plus
these
particular
users
are
able
to
manage
the
entire
repository
without
having
access
to
potentially
destructive
capabilities.
Like
deleting
a
repository,
they
can
manage
the
entire
software
development
lifecycle
for
that
repo,
including
pushing
the
protected
branches,
locking
conversations
and
managing
interaction
limits,
and
it
fits
directly
in
the
current
workflow
to
get
it
set
up.
A
You
go
to
the
Settings
tab
on
your
repository
and
then
click
on
collaborators
and
teams
on
the
left
from
there
you're
able
to
apply
these
roles
to
both
teams,
members
and
actually,
as
well
outside
collaborators
and
very
soon
in
the
next
couple
months,
we'll
be
releasing
this
ability
to
add
this
as
a
base
role,
so
that
any
new
members
who
come
into
your
org
automatically
get
that
role
now.
Another
duty
of
the
project
manager
is
project
planning
and
github
issues
are
a
super
powerful
feature
to
help
with
this.
A
You
use
them
to
communicate
requirements,
deadlines
and
even
ask
for
help
on
particular
subjects,
and
here
at
github
we
use
get
up.
We
use
github
issues
for
everything.
One
of
the
problems
with
issues,
though,
is
that
there's
no
standard
way
to
add
issues,
and
this
leads
to
a
lot
of
unneeded
cleanup
for
project
managers.
It
would
be
great
if
github
automated
that
so
we
did.
We
did
that
using
issue
templates
now.
Issue
templates
help
guide
users
through
the
correct
path
when
creating
users.
The
benefits
of
this
are
when
creating
issues.
A
Now
the
benefits
of
this
you
get
a
higher
quality
content,
you've
reduced
the
triaging
for
the
project
manager,
and
you
also
have
better
onboarding
for
new
users,
because
they
know
the
style
that
they
need
to
be
writing
their
issues
in
now.
How
do
you
use
this
very
simple?
You
navigate
to
the
settings
tab
on
your
repository,
scroll
down
and
click
on
issue
templates.
Now
we
give
two
standard
issue
templates
from
the
beginning.
Those
are
bug,
reports
and
feature
requests,
but
you're
able
to
customize
these
as
much
as
you
want.
A
The
things
you
can
customize
are,
you
can
add,
suggested
titles
for
these.
For
these
issues
you
can
also
customize
the
markdown
format
in
the
body.
You
can
automate
what
labels
get
assigned
to
these,
as
well
as
who
gets
assigned
to
those
particular
issues.
This
is
another
way
to
further
automate
your
software
development
lifecycle
process.
Now,
issue
templates
live
in
your
repository
and
the
dot
github
slash
issue
template
folder.
A
Now
this
is
great
because
if
you
have
multiple
replot
and
repositories-
and
you
want
to
use
those
same
templates
throughout,
you
can
just
copy
that
folder
from
one
put
it
in
the
other,
and
it's
gonna
have
the
exact
same
issue
templates
for
all
of
them
again
all
features
evolved
and
based
on
your
feedback,
there's
two
major
ones
that
we
we
needed
to
change.
A
very
common
use
case
for
for
maintainer
x'
is
someone
will
come
in
and
write
a
question
in
an
issue?
A
There's
nothing
wrong
with
that,
but
it
would
be
better
suited
to
be
asked
in
a
slack
question.
There's
gonna
be
a
slack
channel,
so
you
all
asked
us:
how
would
can
we
direct
our
users
to
our
slack
workspace
or
channel
another
common
thing
that
happens?
Is
someone
will
go
into
a
repository
and
create
an
issue
and
it'll
be
blank?
It'll
just
have
a
title
thanks
to
super
cool,
but
that
doesn't
help
anybody
and
that
just
leads
to
the
project
manager.
A
I'm
gonna
go
back
and
ask
more
and
more
questions,
so
we
added
more
control
with
issue
templates
and
a
llamó
file,
so
this
yellow
file
lives
within
the
issue
template
directory
and
it
gives
you
more
control
over
your
issue
templates.
So
you
can
see
here
on
the
top
left.
I've
turned
off
blank
issues,
so
people
are
have
to
use
issue
templates
or
one
of
the
provided
templates.
You
had
and
there
can't
be
any
more
blank
issues.
You
can
also
link
to
X
Journal
resources.
A
What
I
have
shown
here
is
linking
to
the
get
up
community
forum,
as
well
as
the
bug
bounty
program,
but
you
can
link
to
a
slack
slack
workspace
as
well
and
being
that
all
of
this
is
and
get
its
version.
So
you
can
audit
this
as
well
as
any
whoever
changes
it.
Another
problem
that
we
have
and
we
ran
into
is
duplicate
issues.
A
So
what
you're,
seeing
here
on
the
right
is
I'm
going
in
to
the
rails,
org
and
I'm
gonna
add
in
a
bug
report
Grails
uses
issue
templates
to
shout-out
to
them,
but
what
I'm
doing
right
now
is
I'm
trying
to
add
in
a
bug
for
an
invalid
argument
as
soon
as
I
start
typing
invalid
argument,
what
shows
below
is
a
about
four
different
other
bugs
that
have
already
opened
up
been
opened
up
for
that
invalid
argument.
Now
what
the
benefits
of
this
are?
It
helps
users
find
existing
issues
that
already
have
pertinent
details.
A
If
you're
gonna
open
a
bug
report-
and
it's
already
been
made-
you
actually
may
be
able
to
find
a
workaround
and
help
you
and
you
don't
actually
have
to
log
that
bug
report.
So
second
thing
again
helps
project
managers
and
maintainer
Xand
triaging
duplicate
issues.
So
that's
another
problem
that
we
help
solve.
Something
else
is
is
incorrectly
filed
issues
so
a
lot
of
project
managers.
They
have
multiple
different
repositories
and
as
much
as
you
try
and
get
issues
in
that
right,
repo
they're
not
always
going
to
do
it
and
for
the
project
manager.
A
What
you're
having
to
do
is
delete
one
issue
copy.
The
content
here,
put
it
in
another
repo.
Tell
people
to
go
to
this
issue,
not
that
one
and
it's
just
a
lot
of
wasted
time.
So
we
wanted
to
reduce
those
manual
steps.
It
takes
to
transfer
an
issue
and
that's
why
we
created
transfer
issue
now.
Transfer
issues,
don't
just
navigate
the
content
of
the
issue,
but
in
it
migrates
all
the
associated
metadata
as
well,
the
assignees
the
labels.
A
A
Now,
how
do
you
use
this
super
easy
navigate
to
the
issue
that
you
want
to
transfer
and
click
on
that
beautiful
button
on
the
right
that
says,
transfer
issue
from
there
you're
able
to
choose
a
repository
that
you'd
like
to
transfer
it
to
you
can
transfer
it
to
any
repository
that
you
own
or
any
one
that
you
have
right
access
to
once
you've
done
that
click
on
transfer
issue,
and
we
take
it
from
there
in
terms
of
migrating
all
that
content.
This
is
just
something
another
thing
that
just
saves
time
for
the
project
manager.
A
Now
that's
all
I'm
going
to
talk
about
with
issues
right
now.
Another
another
duty
of
the
project
manager
is
setting
up
new
projects
and,
typically
something
that
we
find
with
a
lot
of
organizations
is
that
they
have
a
quote/unquote
blessed
scaffolding
for
a
particular
for
room
for
how
they
want
repositories.
They
know
how
they
want
the
file
and
directory
structure
to
be
set
up.
They
have
the
issue
templates
they
want,
but
a
lot
of
time
is
spent.
Getting
that
set
initial
scaffolding
set
up.
A
It
would
be
great
if
github
could
automate
it,
so
we
did
and
we
did,
that
with
repository
templates
now,
repository
templates
allow
any
user
with
right
access
to
a
repo
to
mark
it
as
a
template,
after
that,
any
user
that
has
read
access
to
that
particular
repository
can
come
in
and
use
it
as
a
template
and
it'll
have
this
exact
same
files
and
directories
as
its
base.
This
is
available
on
github.com
as
well
as
Enterprise
Server
and
setting
it
up
super
easy
navigate
to
this
settings.
A
So
folks,
we've
talked
about
now.
The
developer
we've
talked
about
the
project
manager
and
now
I'm
going
to
talk
about
the
needs
of
the
enterprise
owner,
so
the
needs
of
the
enterprise
owner
a
little
bit
different
because
your
responsibilities
are
different.
The
enterprise
owner
is
thinking
about
effective
DevOps
automation,
security
and
compliance,
continuous
integration,
they're.
A
Now
here
github
what
we
do
focus
on
enterprises,
getup
was
built
on
open
source
and
the
needs
of,
and
while
the
needs
of
enterprises
differ
from
the
open
source
community,
there
are
concepts
that
can
be
applied
to
enterprises
to
drive
innovation
now
new
applications,
regardless
of
where
they
are,
are
made
up
about
80
to
90
percent
open
source
software.
So
enterprises
are
reliant
on
open
source,
whether
they
know
it
or
not.
A
A
common
issue
for
organizations
is
working
in
silos
now
silos
prevent
collaboration
both
internally
within
your
teams,
but
also
externally
within
the
community
and
your
community,
and
an
enterprise
being
your
enterprise
team.
Now
the
open
source
community
teaches
us
to
foster
more
collaboration
and
a
concept
that
we
call
inter
sourcing.
Now,
inter
sourcing
applies
the
the
lessons
of
open
source
to
all
software
engineering.
It
does
this
to
increase
quality,
speed
and
developer
joy,
and
the
fundamentals
of
inter
sourcing
are
open
communication,
transparency
and
internal
collaboration.
A
Now,
internal
collaboration
isn't
simple,
you
know
it's
often,
multiple
teams
working
across
multiple
projects
can
become
disconnected,
and
this
results
in
duplicative
work,
a
loss
of
cross
team
communication
and
a
loss
of
knowledge
sharing
now
at
best,
this
creates
a
drag
on
productivity,
but
in
the
worst
case
it
creates
security,
exploits
there's
a
very
common
one.
That
happened
where
a
bug
was
found
in
a
team
and
they
fixed
it,
but
didn't
tell
the
other
team
that
they
worked
with,
and
this
actually
created
a
very
large
exploit,
which
we
all
have
had
to
deal
with
now.
A
Get
up
has
been
known
to
help
distributed
teams
collaborate
for
a
long
time
and
we're
trying
to
do
that
to
just
better
drive
innovation
within
the
open-source
community,
as
well
as
within
enterprises.
Now
we're
continuing
to
enable
enterprises
by
building
this
very
cool
feature,
we
called
internal
repositories
now
internal
repositories.
Add
the
ability
to
see
the
same
repository
across
any
organization
you
can
search
for,
discover,
reuse
code
and
contribute
to
those
high-value
projects
all
within
your
enterprise
for
the
enterprise
owner.
A
This
gives
you
peace
of
mind,
because
no
outside
contractors
will
be
able
to
see
these
internal
repositories.
None
of
your
IP
will
be
released
and
it's
very
simple
to
set
up
a
new
repository
with
a
setting.
Click
on
new
repository
you'll
see
a
third
setting
called
internal
and
you'll
set
it
right
there.
This
is
all
done
through
the
enterprise
account
now.
The
enterprise
account
gives
administrators
a
single
point
of
view,
a
single
point
of
visibility
into
the
management
of
their
of
their
organization
and
a
big
thing
for
the
enterprise
owner
and
the
enterprise.
A
Admin
is
managing
policies
and
you
can
manage
policies
at
this
level.
You
can
set
the
repo
creation
permissions.
Do
you
want
people
to
be
able
to
create
public
repositories,
private,
internal
or
combination
of
both?
Do
you
want
forking
on
your
organization?
Do
you
want
your
users
to
be
able
to
fork
from
private
and
internal
repositories?
You
can
also
control
invitations.
If
you
don't
want
outside
collaborators.
In
your
org,
you
can
set
this
at
that
and
set
this
policy
at
this
level
as
well
as
repo
and
issue
deletion.
A
You
can
turn
this
on
or
off
at
this
level.
Now.
Security
is
also
managed
at
this
level.
You
can
enforce
two-factor
authentication
throughout
your
entire
organization.
You
can
set
up
sam'l,
either
your
own
custom,
one
or
a
proprietary
one
as
well
as
view
the
audit
log
data.
We
have
a
very
cool
little
GUI
that
actually
shows
you
where
your
your
instances
are
being
accessed
from
now.
A
We
have
this
concept
called
enterprise
fundamentals.
It
means
that
we
actually
need
to
be
that
we
need
to
deliver
certain
functionality
to
our
enterprises
to
allow
them
to
innovate
and
through
that
feedback,
and
through
the
conversations
we've
had
with
enterprises,
you
said
that
we
needed
an
IP
filtering,
so
an
alpha
today,
we've
allowed
IP
allow
lists
now.
Ip
allow
list
allows
github
enterprise
cloud
customers,
the
ability
to
filter
traffic
from
specified
IP
addresses.
You
can
filter
the
log
in,
of
course,
but
also
sam'l
SSO.
A
It
also
filters
private
personal
access
tokens
as
well
as
that's
a
sage
keys.
All
done
all
done
through
the
enterprise
account
it's
very
easy
to
enable
this
go
into
your
enterprise
account
and
click
on
settings
on
the
left
from
there
navigate
down
to
security
and
you'll,
see
IP,
allow
us
in
the
very
bottom,
from
there
you're
able
to
restrict
or
filter
IP
addresses
individual
IP
addresses
or
an
IP
range,
as
well
as
adding
in
a
description
now.
A
This
is
available
in
alpha
and
we'll
be
releasing
it
in
beta
in
the
next
couple
weeks,
but
if
you'd
like
to
actually
get
involved
in
that
beta,
there's
a
gentleman
right
there
in
the
hoodie,
you
can
talk
to
him
and
you
can
get
on
the
beta
list.
Now
we've
talked
a
lot
today.
We
talked
about
a
couple
of
different
things.
So,
let's
review,
we
talked
about
the
developer,
the
project
manager
and
the
enterprise
owner
for
the
developer.
We
got
you
started
with
github
desktop,
and
then
you
open
your
first
draft
pull
request.
A
Once
you
made
that
pull
request,
your
reviewer
gave
you
some
suggested
changes
and
you
track
your
work
on
your
project
board
from
there.
You
are
actually
triaging
notifications
that
you
enabled
through
feature
feature
preview
for
the
project
manager.
We
gave
you
more
fine-grained
permissions
with
triage
in
the
main
chain
chain
rule
you
set
up
issue
templates
the
guide,
your
users
better
and
how
they
want
to
start
and
how
you
want
them
to
set
up
their
issues.
A
You
reduce
duplicate
issues
with
similar
issues,
and
then
you
transfer
it
issues
with
issue
transfer
and
it
gets
started
up
with
projects
better.
You
have
repository
templates
for
the
enterprise
owner.
We
talked
about
the
concepts
of
inner
sourcing
and
how
internal
repositories
drive
that
now,
it's
all
controlled
through
the
enterprise
account
I
told
you
about
our
new
feature.
A
Ip
allow
us
to
help
enterprises
more
folks,
I
told
you
a
series
of
stories
on
the
features
we've
built
and
how
we
built
them
to
help
you
all
and
what
I'd
like
you
to
think
about,
as
you
walk
out
of
here
is:
what's
gonna,
be
the
story
on
the
features
you've
built
the
build
now
and
build
in
the
future
and
in
the
spirit
of
open
source.
Whatever
you
end
up,
building
github
will
be
there
for
you,
thanks
for
your
time.