►
Description
Dan Cundiff will present Target¹s journey going from no git to GitHub Enterprise with 3,000 users in less than 3 years. He¹ll explain anecdotes to overcoming large organization barriers introducing and growing GitHub Enterprise in a company, and share useful administrator pro-tips they¹ve learned over the years. He¹ll also share how we make GHE an awesome experience for its users so they love it just as much as they do github.com.
About GitHub Universe:
Great software is more than code. GitHub Universe serves as a showcase for how people work together to solve the hard problems of developing software.
For more information on GitHub Universe, check the website:
http://githubuniverse.com
B
The
first
part
is
about
kind
of
how
we
leveled
up
at
Target,
and
that
involves
bringing
in
github
enterprise
and
second
part,
is
about
how
to
be
a
good
admin
or
github
enterprise
and
how
to
make
all
those
users
happy.
So
I'll
have
a
whole
list
of
pro
tips
and
stuff
to
talk
about.
So
let's
talk
about
that
first
story,
so
this
is
the
timestamp
for
the
very
first
user
on
github
enterprise.
B
It
also
happens
to
intersect
at
the
same
time,
whenever
I
feel
like
target
was
going
through
a
transformation
to
level
up
and
compete
in
the
marketplace,
and
that
meant,
for
you
know
at
least
of
my
project,
which
was
API
target
com.
We
needed
to
level
up
on
a
whole
lot
of
different
different
aspects.
One
of
those
was
version
control,
so
that's
kind
of
where
this
story
begins.
So
let
me
give
you
some
context,
though,
for
a
piada
target
com.
It's
literally
targets
API,
so
you
know
think
about
as
an
outsider.
B
What
type
of
things
would
you
use
our
API
for?
We
might
pass
in
a
product
to
look
at
upper
location
and
look
up
the
details
about
of
locations,
hours
of
opening
its
address,
etc.
Well,
if
I'm
creating
all
these
api's
and
I
have
about
80
of
them.
They've
all
involved.
Lots
of
change
and
I
want
to
be
able
to
ship
and
release
really
quickly
and
stuff,
like
that,
and
the
way
target
was
doing
things
before
versus
how
we
wanted
to
do.
Things
was
very
different,
so
you
know
get
help
with
get
AB.
B
So
right,
like
a
lot
of
things
to
do,
maybe
in
your
own
company
it
started
a
you
know
to
server
under
my
desk
me
and
a
guy
named
Bobby
Warner.
We
wanted
to
bring
get
up
enterprise,
so
we
had
a
server
literally
under
the
desk
and
we
installed
it
and
start
using
it
for
our
team
and
just
like
anything
like
this,
it
starts
to
have
some
success.
Stephen
with
our
own
team,
other
teams
will
started
to
use
it.
So
that
was
really
nice
right.
B
It
was
sort
of
a
confirmation
that
we
were
making
the
right
moves,
so
more
teams
started
to
use
it
they're,
really
interested
sort
of
viral.
Other
people
wanted
to
start
using
it,
but
as
soon
as
that
starts
to
happen,
it
also
draws
the
other
camp
too,
which
is
the
ones
telling
you
you
should
use
our
existing
tools
or
hey.
Now
you
should
try
to
do
it,
this
way,
etc.
So
this
is
not
a.
You
know,
a
unique
thing
that
you
would
do
here
in
this
next
step.
Here.
B
It's
sort
of
a
part
of
the
disillusionment
curve
of
any
type
of
change
right,
so
I
do
recommend.
These,
though,
is
if
you're
bringing
anything
in
that's
sort
of
disruptive,
something
like
github
enterprise
seek
protection,
so
make
sure
you
get
sort
of
a
stakeholder
or
a
sponsor
as
sort
of
a
higher
level.
Just
give
you
some
protection
sake.
Listen
everybody
chill
out.
Let's,
let's
try
this
out
and
see
if
it
works
out,
get
allies
so
buffer
yourself
as
much
as
possible
to
get
people
who
are
also
fans
of
github
to
sort
of
stand
with.
B
You
help,
sell
the
key
message
and
stuff
like
that,
and
then
any
objectors
that
are
in
the
way
get
them
out
of
your
way,
but
don't
do
in
sort
of
a
force
hold.
You
know,
stick
approach
instead,
just
convert
them
right,
get
them
to
be
allies
and
that's
a
difficult
part,
but
that
goes
along
with
selling
anything
inside
of
a
big
corporation,
or
you
know,
hey
small
companies
to
right,
so
right
started
out
on
a
server
at
the
desk.
The
next
step,
once
team
start
adopting,
is
to
get
on
to
proper
infrastructure.
B
Just
a
brief
story
about
it:
weas
and
for
those
of
you
who've
been
running,
get
up
enterprise
he
might
giggle.
At
this.
We
were
running
on
VirtualBox
on
that
server.
Under
my
desk
and
virtualbox,
even
in
the
github
documentation
was
strongly
recommended
not
to
run
it
as
we
still
did.
We
pushed
for
quite
a
while
at
some
point
that
I
think
we
were
just
like
okay,
well,
I
mean
I'm
still
working
on
a
piada
target
com.
We're
running
this
thing
for
a
whole
bunch
of
people.
B
We
should
level
it
up
and
actually
make
it
scalable
and
on
resilient
infrastructure
and
stuff
like
that.
So
we
followed
all
the
github
recommendations
in
that
case
and
if
you
want
to
know
more
about
that,
just
follow
up
with
me
afterwards.
I
can
tell
you
some
details
about
that,
so
it
at
some
point,
though,
when
you've
got
sort
of
your
objectors
chilled
out
and
you've
got
some
good
adoption
and
growth.
B
You
start
to
reach
a
point,
though,
where
you
you
want
other
teams
to
adopt
it
because
hey
you
have
to
work
with
him
and
you'd
love
to
see
their
code
on
there.
So
you
end
up
start
to
have
to
sell
it
a
little
bit
actually
right.
So
I
think
at
this
point,
whenever
I
think
we
maybe
had
three
hundred
users
at
this
point,
but
to
get
to
3000
is
a
different
story,
so
you
need
to
sell
the
benefits.
You
need
to
start
telling
people
about
it.
B
Now
there
was
obvious
people
using
the
real
world,
but
hey
if
you
say
like
listen,
we've
got
it
here.
It's
it's
super
stable!
It's
great!
You
should
use
it
to
hear
for
things
that
I
think
we're
key
to
us
and
I
bet
they're
similar
inside
your
the
company.
You
work
for
two.
The
first
one
is
very
obvious.
B
Even
if
you're
interviewing
someone
and
they're
sort
of
interviewing
you
as
the
company
just
being
able
to
say
like
yo
you
totally,
we
use
github
Enterprise,
you
know
work
and
that's
all
you
have
to
say
and
they're
like
well
sweet.
It's
a
tool
use
at
home,
so
I
can
use
it
inside
the
four
walls
of
the
company
as
well.
In
obviously,
if
they're
going
to
join
your
team,
they're
going
to
be
productive
instantly,
you're,
not
using
some
obscure.
B
Rarely
used
version
control
system
or
something
old,
it's
github
right,
everyone
knows
it,
and
so
that's
that's
a
big
benefit.
The
social
coding
aspect.
Obviously
that's
what
this
gift
would
get
up
was
built
on.
We
heard
Chris
talked
about
that
yesterday,
but
it's
really
valuable,
actually
riding
me
I
think
maybe
before
if
you've
worked
in
a
bigger
company
and
they
were
sort
of
going
through,
this
transition
code
was
locked
up
in
weird
places.
You
couldn't
find
it
easily
that
kind
of
his
segway
to
this
next
one.
B
Here
we
were
able
to
just
discover
code
share,
it
I
mean
before
just
even
simple
scripts
were
difficult
to
find
with
other
teams.
So
you
know,
obviously
it's
a
huge
benefit
to
be
able
to
see
other
people's
code
and
share
it
and
reuse
it
right.
That's
that's
a
big
return.
Whenever
you
do
those
type
of
things
and
then
the
last
one
is
integration
to
have
everything.
B
I,
don't
know
the
total
count
of
hooks
and
services
the
github
has,
but
it's
a
lot
of
them
and
whenever
I
told
you
about
in
the
beginning
how
we
were
just
leveling
up
cross
the
boards
and
starting
to
continuous
integration
wanting
to
achieve
continuous
delivery
and
striving
for
it.
Those
hooks
into
all
those
systems
really
are
powerful.
It
just
makes
get
up
Enterprise
a
slam
dunk
to
run,
and
so
it's
really
compelling
that
was.
B
You
basically
got
this
thing.
It's
smooth
sailing,
it's
reached
a
point
where
you
don't
even
really
have
to
sell
it
anymore,
becomes
a
default
you're,
going
to
get
a
lot
of
users
being
on
the
size
of
your
company
and
you're
going
to
want
to
make
them
happy.
So
as
an
admin
having
run
it
since
january
of
2013,
we've
learned
a
lot
of
things,
and
so
that's
kind
of
what
this
next
part
is
about.
B
So
this
is,
this
is
nice.
I
this
is
one
of
the
things
I
saw
yesterday
and
I
talked
about
github
enterprise.
Is
that
if
first
step
to
making
users
happy
he's
doing
very
simple
things
so
start
with
a
simple
URL,
don't
make
it
something
as
skier
that
people
can't
remember
just
make
it,
for
example,
get
target
com?
The
other
part
is
just
have
one
instance.
If
you
can,
I've
talked
to
a
couple.
B
People
have
multiple
instances,
and
that
just
means
your
code
is
in
two
separate
repositories:
they're
not
connected
at
all-
and
that's
probably
not
good,
but
I
understand
there's
reasons
for
it.
But
if
you
can
do
this,
you
should
do
this
so
really
consider
it
so
member,
it's
about
being
able
to
search
through
code
being
able
to
find
stuff
easily
put
it
in
one
place
right.
B
You
right,
you
have
a
spectrum
of
users
who
may
be
no
github,
maybe
they
don't.
Maybe
they
want
to
learn
how
to
get
access.
Maybe
they
want
to
know
more
about
it,
how
it's
the
infrastructure
setup?
You
should
document
those
things.
If
you
have
like
an
internal
wiki
like
we
do,
we
literally
run
mediawiki
inside
of
target
and
it's
kind
of
a
go-to
place
where
people
can
search
for
things.
You
literally
search
get
github
get
AB
enterprise.
It's
going
to
take
you
to
a
page
that
tells
you
everything
about
how
we've
got
installed
in.
B
If
people
are
really
interested
in
this,
let
me
know
afterwards,
but
I
could
probably
take
that
wiki
page
abstract
it
out
and
just
probably
put
it
on
github
or
something
like
that
and
share
it.
It's
a
think.
It's
a
really
well-thought-out
wiki
page.
So
let
me
know
if
you're
interested
in
that
it
all
sort
of
motivate
me
to
publish
it
as
open
source
or
something
like
that,
but
here's
the
things
to
put
on
your
weaker
page.
B
If
you
want
to
do
this,
how
to
get
access,
it's
that's
number
one
thing:
you
probably
have
some
odd
systems
inside
your
company
that'll
bring
you
access
to
things.
In
our
case,
it's
ldap
right,
so
you
get
a
part
of
an
ad
group
and
you
get
added
to
this.
But
you
know
people
don't
know
how
to
navigate
those
things
put
that
in
there
how
to
set
up
your
profile.
B
Some
people
just
log
in
the
first
time-
and
it's
got
some
generic
IDs
and
stuff
like
that
telma
fell,
get
an
avatar
in
there
get
some
face
behind
the
code
right.
The
other
part
of
that
is
not.
Everyone
has
used
github.
So
tell
them
like
hey,
no
listen.
If
you
use
github
pages
in
the
real
world,
you
can
also
use
them
and
get
up
enterprise
how
to
use
emojis
how
to
use
issues
right.
Maybe
you
don't
even
need
a
separate
issue
system,
just
use
github
issues,
because
it's
so
awesome.
It's
right!
B
Next
to
your
code,
how
to
integrate
with
those
things.
I
was
telling
you
about
before.
So
we
have
sections
in
our
wiki
pages,
say:
here's
how
to
integrate
jenkins.
Here's
a
ten
great
with
JIRA,
etc,
because
every
team
that
you
know
target
wants
to
do
those
things,
give
them
an
easy
way
to
do
it.
Post-Mortems
I'll,
talk
more
about
that
here
in
just
a
minute
how
to
reach
the
admins
people
got
issues,
they
see
a
glitch
or
something.
B
How
do
I
talk
to
somebody
I'll
show
you
I'll
share
about
what
we
do
for
that
too,
and
then
just
link
to
github,
Doc's
they're,
pretty
awesome,
actually,
Google's,
probably
a
first
step,
you
probably
doing
some
stuff
and
stack
overflow
getting
answers,
but
honestly
github
doctor
awesome
just
linked
to
that.
If
people
don't
know
about
it,
it's
in
your.
We
keep
age
right
also
as
admins.
B
It's
kind
of
about
transparency,
I
recommend
any
decision
you
made
from
a
stack
perspective,
the
infrastructure,
whatever
document
that
in
a
separate
wiki
page,
it's
about
transparency,
give
you
yours,
users,
some
confidence
to
know
exactly
how
your
infrastructure
is
set
up
for
get
up
enterprise
again
just
about
building
trust
and
transparency
and
stuff
like
that,
they
you
ever
look
at
a
tool
that
you
use
it.
Someone
else
runs
inside
your
company,
you're
like
well.
How
are
they
running
it?
Is
it
backed
up?
Is
it
stable?
B
B
B
This
is
covered
almost
ninety
percent
of
our
needs.
Here
it
is
literally
a
it's.
We
use
a
tool
called
run
scope,
Brent
scope,
just
does
a
HP
synthetic
transaction,
every
five
minutes
to
get
our
go
calm
and
it
does
three
assertions.
It
makes
sure
the
response
time
is
less
than
ten
thousand
milliseconds
ten
seconds.
It
checks
for
a
two
hundred
HTTP
code
and
it
does
some
assertions
to
the
response
body
like
looking
for
certain
words,
and
it
turns
out
if
that
is
up.
Your
github
instance
is
probably
up
just
in
general.
B
Now
we
monitored
this
on
the
inside
and
outside
of
target.
So
this
is
externally
exposed.
We
have
a
that
agent
running
on
the
outside
and
inside
it
turns
out
based
on
our
network
works.
Sometimes
it's
down
for
the
inside,
but
up
for
the
outside.
Isn't
that
kind
of
odd,
but
so
yeah.
That's
actually
covers
nine
percent.
Your
needs
now,
if
that
monitor,
fails
triggers
paigey
duty
pedro
duty
wakes
us
up.
We
go
take
a
look
at
it
and
literally
I'm
telling
you
in
almost
three
years.
This
is
really
covered,
almost
all
of
our
needs.
B
If
you
need
to
dig
in
further
obvious
there's
lots
of
ways
you
can
do
that.
There's
you
probably
heard
yesterday
about
the
ways
you
can
send
all
these
logs
to
log
stash
or
other
your
tool
of
choice,
except
there's
all
kinds
of
things.
This
covers.
Ninety
percent
of
your
needs-
this
is
pretty
strongly
recommended
stuff,
but
I'm
going
to
mention
nonetheless,
because
I
still
hear
other
customs
like
customers
of
Gabe's
not
doing
this,
but
there
is
the
active
passive
arrangement
you
have
I
think
they
introduced
this.
B
It
feels
like
a
year
ago,
or
it's
almost
real-time
replication
to
a
hot
standby
in
a
way,
make
sure
you're
doing
this
practice.
Failing
this
over
to
because
hey,
you
might
have
some
dns
settings
that
are
kind
of
wonky
or
whatever
make
sure
you
test
this
out
and
even
further
dr
step
here
is
doing
your
offline
backups.
B
He
sure
get
up
admins,
maybe
three
years
ago,
remember
that
she
had
to
write
your
own
backup,
utils
and
all
kinds
of
stuff
like
that:
hey
they've
got
them
figured
out,
make
sure
using
backup
utils
from
github
they're
sweet.
It's
super
simple
and
ship
those
off
to
a
place
where
you
know
they're
safe,
so
in
case
of
a
situation
we
need
to
recover.
You
can
do
it.
B
This
one
has
an
asterisk
by
it,
because
I
was
talking
to
some
people
last
night.
Who
don't
do
this,
but
I
recommend
upgrading
frequently
it's
about
setting
expectations
with
your
users,
who
are
champing
at
the
bit
to
use
the
new
features
that
github
is
rolled
out,
turns
out
my
users,
all
three
thousand
my
users.
Actually,
some
of
them
watch
the
release,
notes
and
they're
say:
hey
wins
a
new
feature
coming
you
guys
going
to
do
the
upgrade
set.
The
expectation
is
you're,
an
upgrade,
often
don't
fall
behind.
That
said,
the
asterisk
is
apparently
I.
B
Think
some
customers
have,
they
say,
wait
a
week
because
there
are
some
glitches
in
it,
but
honestly
github
shipping,
github
Enterprise.
It
feels
like
every
two
weeks
and
that's
if
you're
waiting
a
week
well
then
you're
just
sort
of
backing
up
and
queuing
up
whenever
you
should
upgrade
so
I
say
just
upgrade
as
quick
as
you
can
thing
is,
though,
upgrade
in
a
dev
instance,
so
make
sure
you
have
a
non
pradhan
of
github.
In
our
case,
it's
dev
get
target
com.
B
You
can't
see
it's
obviously
behind
the
firewall,
but
you
just
upgrade
that
first
run
some
like
you
know,
maybe
some
functional
tests
against
it.
An
automated
way
see
what
things
break
at
least,
should
cover
most
of
things,
but
I
set
the
expectation
with
your
users.
Keep
him
happy
upgrade.
Often
in
and
I
was
an
admin.
You
get
all
the
great
benefits
to
security
upgrades.
Do
you
do
those
really
quick?
The
obvious
one
I
think
was
last
year,
if
felt
like
was
heartbleed
I
believe
there
was
shell-shocked
to
I.
B
Remember
there
was
a
series
of
upgrades,
but
this
the
story,
but
this
is
kind
of
funny.
I
was
at
a
soccer.
My
son
soccer
game
and
I
was
on
my
phone
was
flipping
through
feedly
and
sort
of
recap.
In
the
day.
Reading
about
this
heart
bleed
thing:
I
was
like
wow.
That
sounds
really
bad
and
occurred
to
me.
It
was
the
timing.
It
was
pretty
funny.
I
was
like
oh
well.
B
What
about
what
about
github
I
wonder
if
it's
vulnerable
they
using
that
openssl
version,
it
was
vulnerable
and
then
I
mean
it
was
literally
like
maybe
30
seconds
later
the
email
from
github
came
out
like
listen.
You
need
to
shut
down
your
instance,
call
your
firewall
guy
or
something
and
get
it
off
the
network
that
was
literally
I.
Think
what
the
email
said:
I
called
Danny
Parker,
who
is
my
co
admin
and
he
saw
the
exact
same
thing
he's
like
literally
I'm
running
home,
I'm
running
home.
So
we
can
go
upgrade
this
thing.
B
I
got
in
the
car,
went
back,
we
upgraded
it.
You
know.
The
key
thing
is
here,
make
sure
you're
paying
attention
to
release,
notes
that
you're
set
alerts
for
yourself.
You
know
if
you're,
using
something
like
hipchat
or
slack,
get
those
are
getting
RSS
feed
or
something
or
if
this,
then
that
type
thing
to
alert
you
whenever
their
upgrades,
because
one
of
them
might
be
a
security
upgrade,
and
you
get
your
tail
in
there
and
upgraded
right.
So
what
does
this
look
like
four
targets?
B
Three
part-time
admins
it
started
out
is
me
and
then
Danny
Parker
came
along
and
we
just
kind
of
spin,
maybe
one
or
two
hours
of
a
week,
and
it's
not
much
of
our
cycle
to
do
this.
Another
guy
named
jay
klein
on
a
team
that
does
a
bunch
of
handles
a
lot
of
developer
tools
at
target
he's
kind
of
joined
in,
and
we
got
great
coverage
here.
I
mean
it's:
it's
not
that
difficult,
especially
not
that
difficult.
If
you
automate
a
lot
of
your
admin
tasks,
so
I
mean
obviously
backup
utils
is
big.
B
I
made
automation
that
made
our
time
a
lot
simpler,
making
sure
backups
were
automated
grooming
users.
You
know
a
three
thousand
users.
People
are
coming
and
going
from
target
make
sure
you're
grooming
that
yeah
just
automate
wherever
you
can
it's
a
good
idea
to
do
that
right,
part
of
making
users
happy
to
is
just
plain
speaking
and
friendly
communication,
I'm
literally
talking
about
if
you're
sitting
out
emails
and
stuff
like
that,
it's
very
tempting
and
a
company
to
want
to
be
soulless
and
faceless.
For
some
reason
you
don't
put
a
face
behind
it.
B
Just
be
plain
speaking
with
your
users-
and
you
know,
you
know,
tell
them
about
upgrades,
what's
actually
happening,
don't
try
to
hide
and
mask
things.
So
what
a
ways
we
provide
support.
The
first
one
is
simple
and
pretty
straightforward
is
just
quick
email
help
you
can
literally
email
our
help
address
and
users
get
pretty
fast
responses
from
us.
We
would
basically
we're
just
checking
throughout
the
day,
and
we
respond.
This
lets
pretty
basic
right.
Better
is
chat
help,
so
we
use
HipChat
at
target.
B
We
actually
have
a
hip
chat,
room
called
github
enterprise,
and
so
that's
great,
because
people
can
come
in
there
and
ask
questions
in
real
time.
We
can
chat
with
in
real
time
and
give
them
answers,
but
even
better,
because
I
feel,
like
we've
done
a
good
job.
Making
users
happy
is
that
we
have
community
helping
there,
and
so
the
your
people,
users
have
get
or
github
or
of
the
community
mindset
anyways
they're
inside
the
company,
and
they
want
to
do
good
things.
They
take
pride
in
their
work.
B
B
So
you
know
it's
difficult
to
foster
that,
but
give
it
a
shot,
because
it's
worth
it,
we've
got
I'd
say
about
15
users,
who
were
just
really
like
very
prolific
in
that
in
that
room
there
and
help
out
people
which
is
great,
makes
my
workload
a
lot
lower
right
and
then
the
last
one
is,
and
this
is
kind
of
small
tip.
Well,
you
can
kind
of
read
it.
B
So
there
is
a
worst-case
email,
because
member
we
want
to
be
able
to
make
sure
we
provide
put
our
users
in
a
situation
where
they
feel
safe
and
if
an
emergency
they
can
contact
us.
We
have
an
email
address
and
not
obviously
can
tell
you
what
that
one
is,
but
it's
kind
of
like
a
you
know:
the
sky
is
literally
falling
tightbeam
address,
you
can
email
it
and
basically
will
do
what
Pedro
duty
does
to
us
anyway.
So
wake
us
up
and
I
interrupt
our
dinners
etc.
B
The
cool
thing
about
this
is,
is
that
you
think
oh
I
would
never
provide
this
in
a
company
right
because
people
abuse
it.
We
have
never
had
this
happen.
No
one
has
used
this
yet
and
we
know
that
it
works
as
we
test
it
every
once
in
a
while.
So
I
mean
I
think
that
maybe
that's
more
about
make
sure
you're
doing
the
other
things
good
first
make
make
it
people
feel
like
they
can
reach
you
through
the
normal
channels.
B
You
want
them
to
have
this
there,
though,
as
just
as
a
as
a
safety
net
last
safety
net
right
as
an
admin
github
support
his
first
class.
There
have
been
a
couple
times
where
I've
been
so
ecstatic
when
I
have
emailed
them
and
I
was.
It
was
urgent.
I
went
to
Twitter
and,
like
said
like
hey
like
this,
this
is
a
sport
guy.
He
was
awesome
like
here's,
why
you
should
use
this
they're
really
great,
though
they
respond,
they're,
very
thorough,
they're,
very
interested
in
the
issue
you
have,
and
you
should
lean
on
them.
B
It's
very
very
good
and
in
the
same
way
that
you
know
all
this
is
about
here
trying
to
figure
what
your
users
one
always
ask
for
user
feedback
whenever
you're
doing
an
upgrade
say.
Let
us
know
if
you
have
any
issues,
please
tell
us
or
just
occasionally
ask
that
github
Enterprise
room
and
hipchat
like
hey:
do
you
have
any
feedback
for
us?
What
can
we
do
better,
always
listen
and
many
times
they
do
get
feedback
and
it's
better.
B
There
was
one
time
I
think
we
were
sending
out
notices
based
on
their
their
ID
they
used
to
log
in,
and
that
was
not
as
good
people
are
saying,
but
you
know
what
I
have
multiple
you
my
address
is
on
my
profile:
will
you
email
those
that
I'm
absolutely
reached
so
stuff
like
that
as
a
basic
example,
but
make
sure
you're
listening
to
your
users
in
the
same
way
that
you
want
to
listen
to
other
users?
Github
wants
to
listen
to
you.
I.
Do
recommend
that
too.
B
Even
if
you
see
something
as
an
admin
or
even
as
a
user
I
suppose
you
could
improve
about
getting
of
enterprise.
Let
them
know
because
they
actually
implement
these
features.
Half
the
things
I
think
I've
seen
come
across.
They
are
always
one
step
behind
the
problem
you
have
it
feels
like,
and
they
only
know
about
those
things
if
you
can
communicate
to
them.
So
yeah
you'll
find
someone
to
github
or
open
up
issues
whatever
it
is.
B
You
want
to
do
is
get
up
and
let
them
know
just
make
sure
your
proactively,
letting
them
know
don't
just
assume
someone
else
is
doing
it
for
you.
I
am
post-mortems
so
right
so
etsy
you
had
this
wonderful
blog
post
years
ago.
How
to
do
post-mortems,
I
personally,
think
they're
very
important
to
do
and
whenever
I
run
something
I
get
a
better
prize.
I
want
to
do
them
so
that
whenever
we
do
have
problems
I'm,
never
the
target
of
you
know
blame
or
I'm
blaming
someone
else.
B
I
think
it
just
makes
for
a
good
culture
and
a
better
place
to
work
right.
So
we
do
them,
and
we
have
enough
issues
where
we
want
to
publish
these
for
posterity.
We
actually
have
a
repo
and
get
AB
enterprise.
We
publish
each
of
those.
You
know
markdown
files
of
each
post
mortem,
so
we
can
go
back
and
look
at
them
or
if
people
find
in
fact,
I've
had
people
inside
of
targets
say
you
know
what,
when
I
did
a
search
for
post
mortem
I
saw
yours
first,
not
that
they
were
great
examples.
B
But
so
let
me
give
you
an
example
of
a
real
real
one
and
you're.
This
will
be
difficult
to
read,
but
this
is
literally
a
message
that
we
send
out
and
you
when
I
talk
about
it
friendly
communication,
hopefully
you'll
kind
of
see
that
here
a
little
bit
the
top
and
the
bottom
of
it.
But
what
we
do-
and
maybe
it's
not
a
pure
post-mortem,
but
it's
literally
saying
we
had
a
problem
today.
Here's
what
happened!
Here's,
what
we
want
to
do
better
and
learn
from
to
keep
from
happening
again
so
right.
B
It
says
from
now
on
orla
stay
here.
Well,
what
happened
is
embarrassing.
Noob
mistake.
We
think
it's
still
important
to
talk
about
it
and
learn
from
it
and
right.
That's
the
key
message
here
and
then
it
just
at
the
end
of
it
like
we
really
mean
this
and
we
tell
our
all
our
users
this.
We
say
we
always
want
to
make
this
thing
better
write
this
thing
better.
We
just
want
to.
We
want
to
make
sure
you're
happy
and
it
means
a
lots
of
people.
B
So
we
get
really
good
feedback
whenever
we
do
these
things
and
it's
these
things
are
like
gold
when
we
get
them
because
it
makes
us
one
of
me
better
Adam
it
so
I'm
just
going
to
share
a
couple
of
them
with
you,
so
so
here's
one
this
was:
these
were
actually
responses
to
that
email
that
I
sent
there
and
by
the
way
we've
had
about
10
or
so
of
these
post
mortems
over
since
2013,
so
anyways
right.
This
is
nice.
This
feels
good
as
an
admin
to
hear
this.
B
What
this
is
is
this
guy
is
inspired
to
do
a
better
job
on
the
things
he
owns
and
wants
to
see.
Other
people
do
the
exact
same
thing,
so
that
I
mean
that's.
Like
I
said
when
I
say
this
is
gold.
This
stuff
is
like
brings
you
to
tears
whenever
you
read
this
stuff,
this
guy
is
like
washed
with
pragmatism.
Here,
he's
like
hey,
when
at
least
it
happened
in
a
good
time,
love
my
get,
let's
get
makes
us
feel
pretty
good
right.
That's
pretty
awesome!
B
This
guy
had
a
wave
of
emotion.
I
just
see
him
crying
at
his
hands,
but
then
he
smiles
when
he
moves
his
hands.
Ii
he's
a
this
is
a
I
know
this
guy
personally,
so
I
was
like
really
nice
to
get
this
message
from
him,
so
encouraging
words
for
sure
this
one's
sort
of
like
is,
after
my
own
heart,
with
the
use
of
y'all
there
but
easy.
You
know
he's
basically
saying
like
thanks
for
the
making
sure
you
sharing
all
the
bad
news
with
us
very
cool
stuff.
B
This
is
something
you
put
on
a
one
of
those
like
inspirational
posters.
You
know,
I,
don't
know
what
the
cat
and
there's
something
like
that,
but
it's
really
cool
this
guy
sent
that
one
and
this
last
one
here
this
is
a
in
a
big
company.
If
someone
tells
you
you've
done
awesome
communication,
that's
probably
the
most
sublime
that
you
can
hear,
because
it's
not
often
that
that
happens,
so
that
was
cool
and
then
I
have
to
make
a
plug.
B
C
B
Obviously,
users
have
a
profile,
and
so
this
is
kind
of
selfish.
But,
for
example,
you
can
obviously
see
how
prolific
a
user
is
on
developing
and
maybe
there's
somebody
you
want
on
their
team
so
and
by
the
way,
the
question
was:
what
do
you
use
the?
How
to
use
the
social
features
on
your
github
Enterprise
instance?.
C
A
B
It's
I
will
confess
it's
pretty
basic.
We
do
a,
we
have,
it
basically
take
pride
and
we
restore
the
data
to
dev
and
we
just
do
some
cursory
tests.
We've
talked
about
having
some
like
selenium
tests
or
something
or
Jeb
tests
that
run
against
it
to
do
those
things,
but
we
just
literally
take
it's
quite
simple.
We
just
take
about
15
minutes
and
we
use
the
most
common
features,
we're
certainly
not
presenting
on
it
kind
of
load
to
it
or
anything
like
that.
B
But
yeah,
like
I
said
it's
I
mean
this
isn't
really
useful
to
say
I
guess,
but
it's
really
well
developed
software
I
feel
like
they've
done
most
the
testing.
For
me,
I'm
just
doing
smoke
test
to
make
sure
the
basic
and
essential
things
didn't
break,
and
only
a
couple
of
times
that
we
caught
some
things
but,
for
example,
here's
what
literally
things
we
do.
We
search
for
gists.
We
try
to
create
gists,
we
use
ssh
and
HTTP
to
do
the
cloning
and
pushes
and
stuff
like
that.
B
Try
to
create
some
repos
create
a
user,
a
couple
of
bad
and
in
things
you
know
just
stuff
like
that.
Basically,
15
minutes
of
doing
that
type
of
stuff.
Those
are
all
things
we
should
automate
when
I
talk
about
the
automated
part,
which
you
just
do
that,
but
we
do
upgrades
happens
so
infrequently
why
every
two
weeks
said:
that's
something!
Maybe
we'll
do
something
now
I'm
talking
myself
into
it,
so
yeah
other
good.
B
D
B
So,
in
the
beginning
of
API
to
target
a
common
subsequently
lots
of
other
parts
of
target,
it's
it
depends
on
which
area
you're
in
at
least
for
us,
so
JIRA,
for
example,
although
github
issues
are
and
where
that's
really
compelling
we're
thinking
about.
Switching
to
that,
that's
one
thing:
that's
kind
of
nice,
Jenkins
so
being
an
office
e
to
trigger
job,
a
pull
request.
Builder
plugin,
that's
very
nice
as
well
to
obviously
when
you
got
a
pull
request,
not
only
reviewing
the
code
with
your
eyes,
but
you're
able
to
see
ya
did
that
is
this.
B
Is
this
pull
request
of
breaking
the
build
in
some
way
trying
to
get
hipchat?
Obviously,
we
want
to
be
able
to
see
all
the
changes,
so
that's
publishing
to
that
I
think
there
are
some
more
esoteric
ones.
That
may
be
small
parts
of
my
team
use,
but
those
are
the
big,
hitters
I
believe
other
teams,
though
hey
whatever
tool
they're
using
you
know
they
integrate
with
it.
So
it
makes
me
want
to
run
a
report
see
if
I
can
figure
out
what
all
of
them
are
so
yeah.
E
B
Is
free
for
all,
so
we
thought
about
that
at
first.
We
said
well
we're.
How
does
the
pendulum
swing
on
this?
Should
we
try
to
encourage
teams
to
hey
you
you're,
a
part
of
supply
chain?
You
should
have
the
supply
chain
Oregon
here
the
repos
you
should
create
in
there,
but
I
think
we
like
debated
that
maybe
for
like
a
week,
but
we
just
thought
sure.
So
if
you
know
what
just
let
people
sort
of
organically
figure,
this
out,
they're
going
to
figure
it
out
and
it
turns
out,
nothing
is
permanent.
B
I
mean
any
of
that.
Stuff
needs
to
move
around
administrative
Lee
as
admins.
You
know,
behind
the
scenes
you
have
the
ability
to
detach
repos
move
them
around
change,
parents
of
forks
and
stuff
like
that
or
just
move
repos
entirely
right.
These
are
all
wonderful
functions
that
just
make
that
a
non
problem
for
us,
I
guess
and
not
many
people
need
that
anyways.
They
sort
of
have
figured
it
out
and
it
goes
back
to
that.