►
Description
Presented by Satish Kumar Nankani, Staff Engineering Manager @ GitHub
GitHub uses GitHub for building GitHub! In this session, Satish Nankani, the Staff Engineering Manager at GitHub, will provide a walkthrough of how GitHub uses GitHub for collaborative development, and how your teams can do the same in order to build and ship faster than ever.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Namaste,
everyone
welcome
to
github.
Satellite
github
is
a
place
where
people
build
software
every
day.
Millions
of
developers
use
github
to
create
things
that
touch
billions
of
people
to
be
at
github
is
an
awesome
responsibility
and
elite.
The
chat,
ops,
integration
theme
in
github
building
products
like
slack
and
teams
github
with
a
goal
to
amplify
engineering
productivity.
A
Let's
start
with
numbers
chat,
ops
is
a
team
of
nine
engineers
and
the
team
has
done
80
deployments
in
last
four
weeks,
making
the
average
to
four
deployments
per
working
day.
It
is
truly
awesome
from
a
devops
metrics
point
of
view
I'll.
Let
you
all
guess
what
the
other
phone
numbers
are
and
post
your
answers
in
the
github
discussion.
A
There
is
a
story
behind
these
numbers
that
makes
them
magical
and
absolutely
motivating
for
my
team.
The
story
of
emotions
started
last
year
in
march
2020
and
I
still
remember,
sitting
in
a
conference
room
with
leadership
team,
pitching
the
idea
to
build
the
vision
of
building
a
unified
chat,
ops
platform.
A
Coming
back
to
present,
we
are
just
a
couple
of
weeks
away
from
shipping,
our
fourth
deliverable
and
making
the
vision
a
reality
in
april.
In
next
couple
of
weeks,
I
am
super
excited
to
share
the
journey
of
unified
chat.
I'm
super
excited
my
team's
journey
and
give
a
walkthrough
of
how
github
uses
github
for
collaboration.
A
I
mean
inclusive
collaboration
and,
along
the
way,
share
practices
and
processes
in
engineering
that
help
us
shift
faster,
whether
we
work
from
home
or
office
in
simple
words,
collaboration
means
working
with
others.
By
end
of
this
session,
we
will
learn
about
eight
key
elements
to
enable
an
effective
and
inclusive
collaboration,
collaborative
culture
in
organization
using
github.
A
The
code
that
powers
github.com
mostly
resides
in
a
mono
repo,
it's
surprising,
but
that's
the
facts,
and
to
enable
team
academy,
every
team
own
repository
setup,
specifically
for
the
issues
and
team
documentation
allowing
them
to
tune
their
day-to-day
process.
There
are
also
teams
which
maintain
their
code
in
dedicated
repo.
A
I
have
got
a
picture
of
slack
repository,
which
stores
the
chat,
ops
code
and
the
team
has
enabled
almost
all
the
features
of
github.
Structurally.
Everything
in
github
organization
starts.
With
the
repository
there
is
a
repository
for
everything
literally
for
onboarding
job
posting
benefits,
values
even
entitlements
are
maintained
in
a
repository.
A
A
A
An
epic
is
a
group
of
features
captured
as
task
list
inscription
and
task
list
has
clickable
check
boxes.
We
just
go
and
select
and
unselect
this
check
boxes
to
track
the
progress
of
if
a
feature
is
complete
or
not,
and
these
help
us
to
track
the
progress
easily
with
minimal
follow-ups,
and
if
you
see
there
are
milestones
set,
which
sets
the
right
expectation
with
the
steel
stakeholders
on
when
this
epic
is
going
to
be
shipped
and
the
same.
Epic
shows
up
in
multiple
project
dashboards
for
tracking
at
different
management
levels.
A
If
you
see
the
c
chat
of
project
dashboard
is
the
dashboard
owned
by
my
team.
Apart
from
that,
this
epic
is
also
getting
tracked
into
two
other
dashboards
moving
to
feature
a
feature,
acts
as
a
unit
of
work
for
around
two
weeks
and
anything
greater
than
two
weeks
is
moved
to
different
feature,
thereby
enabling
us
to
do
work
parallelization.
A
A
The
best
part
of
using
task
this
year
is
we
have
something
called
definition
of
done
and
capturing
a
list
of
tasks
to
be
completed
as
task
sets.
The
right
expectation
with
the
engineer
working
on
the
feature
in
terms
of
what
needs
to
be
completed
and
features
only
show
up
in
the
team
dashboard,
but
no
one
is
stopping
them
to
monitor
in
other
dashboards
too,
and
features
are
shipped
as
and
when
they
are
complete.
A
A
A
A
The
link
available
in
the
notification
come
back
to
get
our
issue
and
the
collaboration
starts
from
there
and
if
you
can
see,
the
bug
was
closed
in
the
same
day
and
primarily
because
the
entire
collaboration
started
from
github
issue
and,
apart
from
getting
things
done,
capturing
everything
at
one
place
in
github
issues
helps
us
to
maintain
the
context
and
the
history
of
actions
which
enables
information,
discovery
and
the
decisions
taken
can
be
referred
in
future
by
the
way.
If
you
are
wondering
what
all
goes
into
the
issue,
then
literally
everything
is
captured.
A
Every
detail
from
spec
clarification,
design,
proposals,
design,
chatter,
meeting,
notes,
decision
taken
literally
everything.
You
also
use
discussions.
Discussions
are
used
for
brainstorming
when
there
are
new
initiatives
and
when
we
know
it's
going
to
take
longer,
they're
also
used
for
team
building
like
how
was
the
weekend.
What
were
you
doing?
What's
your
plan
for
the
coming
weekend
and
all
these
gets
into
discussion
discussions?
Are
we
use
not
only
for
technical
but
also
for
fun
elements
and
increasing
the
collaboration
in
the
team?
A
A
Apart
from
that,
we
encourage
having
video
demo
video
links
and
these
demo,
video
links
can
be
from
anywhere.
It
could
be
a
small
working
prototype
coming
from
a
developer
environment
or
production
or
staging
they
don't
need
to
be
only
collected
or
recorded
in
production,
and
we
believe
in
demos
and
not
memos,
so
the
other
part
of
standard
status,
update
event
is
risks
and
mitigations.
A
A
Every
organization
or
most
of
the
organization
makes
use
of
slack
and
teams
for
day-to-day
interactions
in
chat
and
chat.
Ops
is
one
which
brings
all
the
tools
and
processes
into
the
conversation
where
the
engineers
are.
This
is
an
example
of
a
pull
request
created
by
an
engineer.
We
encourage
engineers
to
capture
design
changes
and
also
user
experience,
and
if
the
change
results
in
a
user
experience,
change
then
putting
before
and
after
experience
helps
the
reviewers
to
get
the
context
and
review
faster.
A
A
A
These
are
the
list
of
actions
available
in
my
team's
repository
and
to
give
an
example,
we
use
code
coverage
as
part
of
our
pr
workflow
and
as
soon
as
the
pr
is
raised,
the
code
coverage
tool
runs
and
post
the
outcome
of
that
in
a
tabular
format,
and
if
there
is
a
dip
of
even
0.5
percent
in
unit
testage,
then
the
pr,
even
if
it's
uprooted,
can't
be
merged.
Okay,
now,
let's
go
to
the
pr
workflow.
A
A
So
once
the
notification
is
received
by
the
reviewer,
they
navigate
to
the
pr
from
the
link
in
the
notification
reviews
the
pr
and
leaves
the
comment
for
changes,
and
once
the
comments
are
left
in
this
case,
the
reviewer
is
asking
for
a
couple
of
changes
from
the
author
and
then
the
author
receives
the
notification
and
modifies
comes
addresses.
The
pr
comment,
then
ed
mentions
the
reviewer,
since
the
comments
are
addressed.
The
reviewer
gets
a
notification,
goes
to
the
pr
reviews,
the
changes
and
approves
the
pr.
A
A
What
next
the
pr
is
approved,
ford
is
ready
to
get
births
deployed
in
production
and
deployment
in
one
way
is
a
complex
process.
If
even
there
is
a
new
engineer
in
the
team
right,
they
need
to
understand
a
lot,
but
in
github
deployments
are
simplified
right.
Now,
I'm
going
to
show
you
the
real
power
of
chat,
ops.
A
A
Almost
every
github
developer
interacts
with
you,
god,
literally
every
day.
Multiple
times
and
hubot
is
a
robot.
We
just
ask
the
huebot
to
do
the
deployment
with
a
single
command
and
the
job
is
taken
care.
The
deployment
is
done.
What
next
time
for
a
party?
The
engineer
is
super
happy
and
the
engineer
goes
to
the
channel
and
shares
the
completion
of
the
epic.
The
team,
the
team
starts
to
sparkle.
A
The
engineers
who
contributed
towards
team
goal
by
shipping,
their
epic,
the
dot
dot
sparkle
command
that
you
are
seeing
on
the
screen
is
a
huge
command
used
to
recognize
team
members.
Effort
cubot
not
only
does
complex
things,
it
plays
an
instrumental
role
in
bringing
fun
and
spread
joy
within
the
organization.
A
Let
me
decode
this
for
you.
I
said
80
deployments
by
team
in
last
four
weeks,
making
an
average
of
four
deployments
per
working
day.
The
rest
of
the
numbers
are
and
you're
able
to
achieve
this
80
deployments
by
working
on
66
issues
which
were
closed
in
last
four
weeks.
351
issue
comments,
which
shows
the
amount
of
collaboration
we
do
on
these
issues.
72
prs.
A
C
A
C
B
A
Yeah,
so
if
I
reconnect
correctly
to
be
very
honest
personally,
I
was
also
struggling
through
the
through
that
phase
right.
This
was
the
second
time
in
my
entire
professional
career,
where
I
was
feeling
helpless
and
out
of
control
to
help
my
team,
and
you
have
to
think
what
help.
Really
it's
not
a
big
thing,
but
I
think
the
weekly
check-ins
that
we
started
after
our
scrum
every
monday.
A
We
have
scrum
every
day
right
and
then
we
started
this
way
of
interacting
with
folks
doing
a
weekly
check-in
on
mondays,
where
we
used
to
share
with
each
other
how
everyone
is
go,
what
everyone
is
going
through,
just
speak
out
and
what
is
working
for
them?
That's
it
right,
and
this
whole
concept
made
everyone
realize
everyone
is
going
through
the
same
phase.
C
A
Interesting,
so
what
I
showed
was
eight
key
elements
of
collaboration,
see
in
simplicity,
collaboration
means
working
with
others,
but
that
is
not
that
easy.
When
we
work
with
like
2000
people
in
the
organization
or
even
when
we
work
with
10
people
or
when
we
have
five
people
at
phone
rights,
the
most
challenging
one
is
always
bringing
in
that
inclusion.
Part
in
the
whole
collaboration
story.
A
That
is
the
most
difficult
one.
We
talk
about
diversity,
a
lot
right,
but
if
there
is
no
inclusion,
it
is
very
difficult
to
make
the
diversity
successful
in
an
environment,
and
this
is
something
that
we
achieved
by
writing
a
lot
in
this
async
mode
and
we
started
sharing
and
putting
those
in
discussions
issues
everywhere,
where
the
team
was
able
to
see
who
is
doing
what
and
they
had
an
opportunity
to
come
back.
A
Read
about
the
proposals,
share
their
thoughts
and
contribute
and
share
the
diverse
opinions
in
this
way,
as
a
team
able
to
come
to
a
inclusive
and
conclusive
conclusion,
yeah.
But
it's
a
journey.
We
are
fully
not
there.
Yet
we
are
still
learning
it's
not
that
we
are
perfect,
but
I'm
extremely
happy
to
see
the
graph
the
way
it
went
up
and
you're
still
learning
and
there's
a
lot
to
learn
and
github
is
the
way
to
make
use
of
all
these
in
the
right
way
to
make
everything
successful.
B
Thank
you,
sateesh.
Thank
you
again
for
your
vulnerability
and
sharing
from
your
heart.
This
was
really
insightful
and
again
things
that
everybody
around
us
can
learn
as
well.
Again,
thank
you
for
a
great
session
and
remember
folks.
Satish
will
be
with
us
in
discussions,
so
you
can
have
your
heart
to
heart,
chats
with
him
there
as
well
and
ask
him
all
the
questions
folks
discuss
with
satish
on
discussions.