►
Description
In this video Andrew Connell (Voitanos) is showing how to contribute to official SharePoint developer documentation hosted at http://aka.ms/spdev-docs. These docs are maintained in GitHub and we do welcome edits on them as you notice any areas which should be updated.
Presenter - Andrew Connell (Voitanos) @andrewconnell
More details on the SharePoint developer community from http://aka.ms/sppnp.
A
Hi
I'm
Andrew
Connell
from
boitano's
and
in
this
quick
little
screencast
I,
want
to
show
you
how
you
can
submit
some
changes
to
the
SharePoint
framework
documentation
by
submitting
a
pull
request
to
the
official
github
repository.
So
let's
pick
an
example
out
here,
what
I've
done
is
I
filter
for
some
issues
that
are
assigned
to
me
and
I'm
gonna
find
one
where
someone
has
that
left
a
comment
and
saying
that
there
is
a
little
bit
of
some
error
on
the
page
and
how
things
should
change
what
they
suggested.
A
The
changes
so
I've
assigned
this
to
myself.
What
I'm
gonna
do
is
I'm
gonna
go
find
the
piece
of
content
that
they're
talking
about.
So
it's
this
page
that
we
see
right
here,
avoid
being
throttled
and
they're
talking
about
this
paragraph
about
sporadic
traffic.
So
if
I
just
do
a
quick
little
search
for
that,
they
are
saying
that
this
sentence
right
here
is
a
little
confusing.
So
here's
what
we
have
to
do,
what
I
need
to
do
is
and
when
you
create
a
change,
you're
submitting
a
change
to
a
github
repository.
A
The
general
process
is
that
you
want
to
create
a
copy
of
that
repository
in
your
github
account.
You
then
make
the
changes
in
your
copy.
We
call
that
your
copy
a
fork
once
you've
made
the
changes
in
your
copy.
You
then
submit
your
changes
as
a
pull
request
to
the
originating
repository,
the
Microsoft
repository
and
effectively.
What
that's
doing
is
you're
submitting,
what's
called
a
pull
request
that
is
telling
the
owner
of
that
repository,
you're,
saying
I'm,
requesting
you
to
pull
changes
from
my
copy
of
your
repository.
A
So
let
me
show
you
how
to
do
this,
so
what
I've
done
we're
inside
of
this
repository,
so
it's
called
the
SP
dev
Doc's.
That's
where
all
the
content
lives
inside
the
SharePoint
documentation.
So
what
I'm
gonna
do
is
I'm
gonna
click
home
fork
over
here
now.
What
that
does
is
that's
gonna
say:
where
do
you
want
to
create
this
fork
and
I
already
have
an
instance
of
it,
so
I'm
going
to
use
my
existing
instance.
A
So
here
is
my
existing
copy,
and
what
I
want
to
do
is
I
need
to
get
a
copy
of
this
down
on
my
machine,
where
I
can
make
my
edits
so
I'm
going
to
come
over
here
and
click
clone
or
download,
and
this
is
the
standard
process
for
creating
a
github
repository.
You
go
ahead
and
clone
it
if
you're
not
sure
how
to
do
that.
There's
all
this
documentation
on
github
that
show
you
had
to
do
it
now.
I've
already
gone
ahead
and
done
that.
A
So,
if
I'm
gonna
come
over
here
to
my
command,
prompt
I've
already
created
a
copy
of
my
of
the
repository
right
here.
So
if
I
open
it
up,
I'm
showing
you
this
on
Mac
OS,
but
I'm
gonna
do
all
the
github
commands
or
all
the
git
commands,
I'm
gonna.
Do
them
all
the
command
line,
so
it
you
know
that
you
can
copy
those
exact
same
commands
on
your
machine,
but
just
know
that
you
can
also
use
any
of
the
different
GUI
tools
for
working
with
git
and
github
I'm.
A
Just
not
gonna
do
that
in
this
case,
to
be
more
universal,
for
what
I
show
you
now,
one
of
the
things
I've
noticed
on
my
machine.
Alright,
then
I
have
an
issue
on
my
machine.
Is
that
I
have
an
issue
and
I
notice
here
where
it
says
that
my
current
branch,
my
master
branch,
is
11,
commits
behind
the
SharePoint
master
branch,
which
is
that
when
it
says
SharePoint
here,
you
can
see
that
I
forked
from
SharePoint,
and
so
it's
saying
that
their
master
branch
I'm
Way
behind
it.
A
So
what
I
need
to
do
is
I
need
to
update
my
copy
to
be
at
the
same
level
as
what
the
SharePoint
copy
is
and
if
I
don't
do
that,
then
there's
a
chance
that
my
edits
aren't
gonna
be
accepted
because
they
may
contradict
what
somebody
else
has
done
now.
If
you
adjust
for
to
your
repository
you're,
not
gonna,
have
this
issue
you're
gonna,
be
even
so
what
I'm
about
to
show?
A
You
is
only
if
you've
done
one
of
these
in
the
past,
so
here
I'm
gonna
jump
back
over
to
my
machine
over
to
my
command
prompt
and
what
I'm
going
to
do
is
I'm
gonna,
say
get
remote
V
and
what
I'm
doing
is
I'm
asking
I'm
saying
show
me
a
list
of
all
the
remote
references
in
my
current
repository
that
are
pointing
to
other
repositories.
So
in
this
case
here
the
origin,
the
name,
the
remote
called
origin,
is
pointing
to
my
copy
of
it.
A
That's
the
one
when
I
did
a
clone,
it
automatically
created
origin,
I
created
another
one
here
called
upstream
and
I
point
to
the
I
point
to
the
Microsoft
copy
of
the
SP
dev
Docs
issue
list.
So
if
you
don't
have
that
which
you
probably
don't
by
default,
here's
how
you
create
that
go
back
to
the
SharePoint
document,
the
SharePoint
repository
and
go
get
a
reference
to
his
his
URL
for
this
for
this
item,
so
you're
gonna
grab
either
I'm
using
SSH
on
my
machine
for
authentication.
A
If
you're
use
HTTP,
you
grab
that
one
I'm
just
gonna
grab
the
ssh
one
and
I'm
gonna
come
over
to
my
machine
and
let's
say
I'm
gonna
do
a
git
remote
add
this
is
new.
I'm
gonna
give
it
a
name
called.
This
is
new
and
then
just
paste
that
in
so
what
does
that
do?
What
that
did?
Is
that
just
created
another
remote
right
here
for
my
machine
now?
Why
am
I
doing
that?
I'm
gonna
show
you
why
I'm
doing
that?
Just
a
second.
A
So
what
I'm
gonna
do
is
I'm
gonna,
clear
the
screen
to
kind
of
clean
things
up
a
bit,
so
I'm
gonna
say
get
fetch
and
remember.
Ours
is
called
upstream.
So
what
it's
doing
is
I'm
saying
go,
make
sure
you
have
a
copy
or
in
memory
you
understand
everything.
That's
living
on
your
remote
on
the
remote
repository
that
just
don't
already
know
about
so
here
it's
grabbing
all
the
commits
that
we
have
for
master.
A
What
I'm,
then
gonna
say
is
I
wanted
to
say
make
sure
that
my
master
has
everything
that
the
remote
master
has
so
I'm
gonna
say:
get
pull
in
and
we're
gonna.
Do
a
command
called
rebase
that
basically
says
take
everything,
that's
all
mine
and
put
it
on
top
of.
What's
already
there
well
I,
don't
have
anything,
that's
new,
so
it's
not
gonna
do
anything
but
just
really
sink
mine
up
with,
what's
already
in
the
Microsoft
repository,
so
I'm
going
to
say,
pull
from
the
remotes
ups,
the
remote
called
upstream
get
his
master
branch
so
effectively.
A
What
I'm
doing
is
go
grab
all
the
Microsoft
stuff
that
that
they
have
that
I,
don't
already
have
and
add
that
to
my
local
copy
here,
I
can
see
that
this
little
arrow,
pointing
up
on
my
machine,
is
telling
me
that
you've
got
more
stuff
than
what
is
in
your
origin,
so
I'm
just
gonna
say,
get
push
and
what
you'll
see
here
if
I
now
go
back
over
to
the
browser
and
I?
Look
at
my
copy
of
this
see
where
it
says
11
commits
when
I
refresh
the
page.
A
It's
now
gonna
show
me
that
I'm
even
so
now
this
is
in
great
shape
now
I've
prepped
my
machine
for
doing
a
good
pull
request.
So
now,
let's
go
back
over
to
the
machine
I'm
going
to
go
ahead
and
launch
vs
code,
where
I
can
make
the
changes
to
that
article.
So
here
in
vs
code
I
have
found
the
file
in
question
that
we
wanted
to
make
an
edit
to,
and
here
again
here's
that
sentence
that
we're
talking
about
where
it's
a
little
confusing.
A
So
what
I'm
gonna
do
is
I'm
gonna
make
a
little
change
to
it
right
about
here,
but
before
I
make
those
changes.
Let
me
show
you
a
good
practice
that
you
should
do.
You
should
always
create
a
branch
inside
of
your
repository
that
is
going
to
include
the
changes
related
to
the
issue
or
to
the
update
that
you're
applying,
and
the
reason
for
that
is
because
you
want
all
of
your
changes
that
you're
supplying
for
the
specific
documentation
change
or
when
you're
fixing
an
issue.
All
of
those
should
be
completely
isolated
from
anything
else.
A
That
is
in
that
repository
so
and
first,
let's
go
find
out
with
the
nut.
Would
that
issue
number
was
we
see?
It
was
issue
4106
right
here,
so
the
process
I
like
to
do
is
I
like
to
say:
git
branch
create
a
brand
new
branch,
so
I'll
say
git,
you
can
say
branch
or
I'm,
gonna,
say
get
check
out.
B
says,
create
a
branch
and
call
it
doc
fix
issue
4106.
So
you
can
see
right
now.
A
The
new
issue,
a
new
branch
here-
called
doc-
fix
issue
4106
now
I'm
gonna
come
over
here
and
let's
make
our
change
to
the
code.
So
what
it's
trying
to
say
here
is
it's
basically
saying
that
these
apps
are
going
to
include
synchronization
engines,
backup
providers,
search
index,
there's
classification
engines
and
data
loss
prevention
tools
and
any
other
kind
of
a
tool
that
would
attempt
to
look
at
all
the
data
in
its
entirety
and
make
some
changes.
A
A
So
here
it
says:
hey
the
branch
that
you're
on
right
now,
there's
nothing
inside
of
your
origin
repository.
Do
you
want
me,
create
one
I'll,
just
say
yes
go
ahead
and
do
it
it
says:
where
do
you
want
to
create
it
and
I
want
it
to
go
in
my
origin?
I
don't
want
to
create
it
inside
the
SharePoint
repositories.
I
want
to
create,
in
my
repository
my
fork
so
I'll.
A
Let
this
thing
finish
and
now,
let's
finish,
let's
come
back
to
the
browser
and
let's
look
at
my
copy
here
so
I'm
over
here
in
my
copy-
and
here
we
can
see.
Look
we
just
submitted
doc
fix
issue
4106,
so
I'm
gonna
go
over
here
and
say,
compare
and
create
a
pull
request.
So
here
it's
doing
Korean
pull
request.
It's
going
and
I'm
making
a
request
to
this
repository
to
pull
from
this
repository.
Use
it
from
this
branch
into
that
branch
right
here.
So
here
I'm
going
to
come
down
this
figure
you
can
see.
A
The
comment
was
already
added:
I'm
rephrasing,
a
statement
to
be
more
clear.
So
here
we're
gonna
come
over
here,
I'm
gonna
say
this:
is
a
content
fix
so
I'm
just
gonna
put
a
little
cross
right
there
and
I'll
get
rid
of
this.
Let's
see,
let's
scroll
down
a
bit
farther,
we
can
delete
this
entire
section
because
we
don't
need
it
as
the
instructions
say
and
then
it
says
what
are
the
related
fixes?
Well,
let's
grab
the
comment
up
here
this
fixes
and
we
will
put
that
right
here.
A
There
we
go
so
we
fix
this
like
right
here,
I'll
go
through
and
close
this
out
and
then
I'm
going
to
give
a
little
description
on
what
is
inside
this
pull
request,
rephrased
a
sentence,
a
statement
to
be
more
clear.
That
was
phrased
a
little
confusingly
there.
We
go
we're
all
good,
so
I'm
gonna
go
ahead
and
then
say
create
a
pull
request.
Now
I've
submitted
my
first
pull
request
here
to
the
SharePoint
dev
Doc's
issueless
notice.
A
Here,
if
I
go
back
over
to
the
issue
that
we
were
just
on
by
clicking
on
it
and
if
I
scroll
down,
what
you
will
see
is
that
it
will
reference.
It
has
a
reference
here,
because
my
issue
that
I
had
created
had
a
comment
in
there.
That
said
that
it
was
for
the
4106
issue,
4106
so
automatically
in
this
statement
to
it,
and
my
poll
request
was
automatically
added
as
well,
because
it
had
a
it
had
a
comment
in
there
as
well.
A
That
says
it
fixed
number
forty
106
and
there's
the
pull
request,
and
that's
it.
That's
all
you
have
to
do
to
go
ahead
and
to
submit
documentation,
fixes
our
updates
to
the
SharePoint
documentation.
From
this
point
here
we
just
wait
for
somebody
from
Microsoft
to
approve
our
change
and
merge
it
into
the
docs.