►
From YouTube: Community Demo - Getting started on using GitHub to contribute to SharePoint dev community
Description
This community call demo is taken from the SharePoint General Development Special Interest Group recording on 7th of February 2019. In this video Andrew Connell (Voitanos) shows how to get started with using GitHub and how to contribute to the SharePoint dev community.
Presenter - Andrew Connell (Voitanos) - @andrewconnell
More details on the SharePoint dev community calls from http://aka.ms/sppnp.
A
A
Sometimes
we
see
questions
that
we
kind
of
wish
had
been
asked,
and
so
my
goal
today
is
to
run
through
and
show
you
kind
of
walk
through
like
how
do
you
go
about
getting
help?
How
do
you
go
about
submitting
questions
or
filing
bugs
or
even
contributing
back
to
the
community?
There's
a
couple
things
I
want
to
cover
here,
but
before
we
get
started
just
let
me
say
one
thing
just
to
keep
in
mind:
I
do
not
work
for
Microsoft.
A
Some
of
the
things
that
I'm
going
to
say
may
not
be
the
exact
same
thing
that
they
would
want
to
say.
I'm
going
on
I
make
an
community
contribution
person,
as
are
most
of
the
people
who
are
working
in
the
github
issue
list
for
the
SP
dev
Docs
issue
list.
Most
of
the
people
you
can
see
there
are
contributing
community,
I
can
say
this
community
contributors
and
so
they're
doing
this
in
their
own
time.
This
is
not
part
of
their
day.
A
A
I'm
gonna
try
to
avoid
watching
anything
in
the
chat,
because
we
want
to
make
sure
that
we
have
a
good,
solid
demo
of
this
stuff
that
we
can
take
this
video
and
we
can
post
it
on
the
the
YouTube
channel
for
everybody
else
to
take
a
look
at
here.
First
of
all,
so
let's
say,
for
example,
that
you've
got
an
issue.
You
got
a
question
so
the
best
place
to
go
these
days
for
SharePoint
development
questions
is
the
SP
dev
Docs
issue
list
or
the
SP
Doc's
repository.
A
A
So
when
I
go
and
click
new
issue
here,
what
we've
done
is
we've
set
up
a
template
here
for
what
the
issue
would
look
like
when
you
first
go
to
create
and
there's
a
bunch
of
stuff-
that's
already
here,
but
if
you
take
a
second
to
read,
what's
here,
you're
going
to
notice
that
a
lot
of
stuff,
you
really
don't
want
to
you're
not
going
to
want
to
keep
this
stuff
here.
In
fact,
we
have
a
lot
of
explanations
here.
A
They
even
say
delete
this
paragraph
after
you
read
it,
and
this
is
not
delete
this
paragraph
for
the
person
you're
submitting
it
to
this.
Is
you
is
the
one
that's
submitting
the
issue,
so
we
just
give
you
a
little
bit
of
information
here
and
you
want
to
make
an
easier
way
to
see
this
up
here
at
the
top.
If
you
click
on
preview,
this
gives
you
a
really
good
idea
of
what
things
you
should
be
getting
rid
of
really
anything
in
blockquote.
That's
the
stuff
that
you
should
delete
so
here.
A
A
The
idea
here
is
that
we
have
this
check
box,
looks
list
of
the
different
types
of
questions
or
issue
that
you
could
be
submitting
either
a
question
a
typo,
a
bug
etc,
and
it
even
says
what
you're
supposed
to
do
now
check
this
out.
If
you
go
in
here,
most
people
are
just
putting
an
X
inside
of
these
box
here.
Thinking
that
that's
what
the
these
instructions
are
saying,
but
they're
not
they're,
saying
that
if
you
go
put
an
X
in
and
remove
the
space,
that's
there.
A
So,
instead
of
having
a
space
like
you
see
here,
I'm
just
replacing
it
with
an
X
when
you
do
that
check
it
out,
it
makes
a
little
checkbox
right
here.
If
you
don't
do
that
and
if
you
end
up
just
putting
an
X
in
like
that,
well,
if
you
do
that,
it
gets
rendered
out
all
funky.
So
don't
do
that,
be
a
good
community
country
contributor
and
get
rid
of
the
space,
and
you
may
wonder:
well
then,
why
don't
you
guys
just
don't
put
the
spaces
in
there?
A
Initially,
it's
like
well,
because
things
get
all
funky
on
the
rendering
as
well.
So
you
put
a
space
in
there
when
you
don't
want
it
checked.
You
put
an
X
in
there
when
you
do
want
to
check.
So
that's
step
one,
and
it
even
tells
you
that
in
the
instructions
so
once
I
figured
that
out,
I
come
over
here
and
I
blow
this
paragraph
away.
A
I,
don't
need
it
same
thing
with
this
one
I
blow
it
away,
I,
don't
need
it
the
expected
or
desired
behavior
if
you're
doing
something,
and
it
didn't
work,
the
way
that
you
thought
it
was
supposed
to
work
or
the
way
the
documentation
says.
It's
supposed
to
work
say
that
if
it's
a
bug,
tell
us
what
you
expect
to
see
happen
or
a
picture
that
you'd
expect
to
see
happen
and
then
tell
us
what
happened,
but
the
observed
behavior
is
when
you
start
going
through
to
start
submitting
these
different
issues.
A
There's
a
couple
things
I
want
you
to
think
about.
First
of
all,
most
people
who
are
helping
us
already
talked
about
these
people
are
all
written
unity
contributors
we're
doing
this
in
our
own
time.
So
you
want
to
keep
in
mind
that
hey
these
people
that
are
I'm
asking
questions
too
and
probably
90%
people
they're
going
to
respond
to
me-
are
doing
this
off
the
clock.
They're
not
getting
paid
for
this.
A
So
when
you
post
an
issue,
be
respectful,
the
more
information
that
you
can
share
with
us,
the
better,
the
information
that
you
can
share
with
us,
the
easier
it
is
to
help
you
and
thus
the
people
who
are
helping
are
probably
more
motivated
to
jump
in
and
to
give
you
a
hand
hosting
an
issue.
That's
like
this
is
so
stupid.
A
Let
me
show
you
a
couple
examples
and
I'm
gonna
apologize
right
off
the
bat,
because
I'm
gonna
be
calling
out
a
couple
of
issues
here,
but
let
me
show
you
what
a
bad
issue
looks
like
here's,
a
bad
issue
right.
This
is
one
that
google
submitted
just
says
I'm
getting
this
access.
Is
this
error
here
and
then
I'm
saying?
Let
me
get
their
name
off
of
it
so
that
we
don't
see
that
well,
I!
Guess
that's
not
going
to
work.
They
post
their
error
right
here.
A
They
show
a
picture
just
say
somebody
please
help,
but
then
look
at
this.
We
have
all
this
additional
stuff
is
still
here
and
we've
got
to
scroll
through
this
and
see
what
we
had
all
these
sections
here.
For
a
reason,
and
no
one
even
took
it,
you
know
paid
any
attention
to
it
and
then
deleting
these
paragraphs,
please
don't
do
that.
Here's
another
one
that
I've
got
that
I'm
going
to
show
off
here.
This
one
came
in
this.
A
What
we
got
the
other
day
this
one,
the
problem
is
just
in
the
title:
they
took
the
time
to
actually
get
the
checkbox
right,
but
then
they
didn't
do
anything
else
any
of
this
other
stuff.
That's
not
a
good
issue.
Come
on
people.
Is
this
so
simple,
here's
a
good
issue.
This
is
an
issue
by
Alex
that
Alex
posted
check.
This
out
he's
got
a
question
and
potentially
a
Bugsy's
check
things
off
the
right
way.
He
got
rid
of
all
the
extra
junk
that
we
have,
therefore
the
helpings
for
the
helper
stop.
A
He
also
went
there
in
the
observed
behavior
he.
This
is
what
I
expect
to
see.
This
is
what
happened
now
is
how
his
code
is
being
formatted.
Let
me
show
you
how
he's
doing
that
now?
I'm
gonna
be
able
to
do
this,
because
I've
got
edit
rights
on
the
repo
but
check
out
what
he
did.
He
did
this
concept
called
code,
fencing
and
you're.
Using
these
little
back
ticks,
that's
the
look!
That's
the
the
key
or
the
the
character,
just
at
least
on
a
u.s.
keyboard.
A
Isn't
the
top
left
of
your
keyboard,
it's
above
the
tab
or
next
to
the
one
key,
and
so
you
got
three
of
those
back
ticks
followed
by
the
the
language
that
you're
using,
so
it
could
be
JavaScript
or
jas
or
TS
cs4.csf,
whatever
that
is
formatting.
It
makes
it
heck
of
a
lot
easier
to
read
his
code
instead
of
just
past
pasting,
stuff
and
power
show
it
you
can
do
it
too,
just
but
PS
will
do
it
or
I.
Think
posh
will
do
it
as
well.
A
A
If
you
submit
a
request
for
a
new
feature
or
for
something
to
change,
we're
probably
gonna
close
your
issue
pretty
quick,
but
we're
going
to
tag
it
as
a
user
voice
request,
because
requests
for
new
features
don't
go
in
the
issue
list.
They
go
into
user
voice
place
and
then
use
our
voice
site
and
the
link
for
it
is
right.
There
we've
got
these
other
ones
here
for
the
status
that
we
can.
You
can
see
where
things
are.
A
If
someone's
asked
a
question
we've
answered,
it
will
say
that
if
something
is
working
the
way
it's
supposed
to
will
say
that
if
we
are,
if
there's
an
issue
that
is,
has
been
acknowledged
by
Microsoft,
but
we
don't
have
a
timeline
on
when
it's
going
to
get
released,
we
put
working
on
it
on
there
and
then,
if
we
know
when
it's
going
to
get
released,
we'll
say
it's
fixed
in
the
next
drop
or
we'll
say
it's
fixed
and
then
we'll
close
it
now.
There's
one
that
I
do
want
to
highlight
here.
A
That
is
that
people
are
noticing
is
coming
up
a
lot
more
so
that
you're
aware
of
what
this
is.
So
these
purple
ones.
What
happens
when
an
issue
is
created?
We
have
a
bot,
that's
watching
the
issue
list
and
when
a
new
issue
is
submitted
to
the
issue
list,
it's
automatically
going
to
get
tagged
with
triage
and
that's
effectively
telling
those
of
us
who
have
the
ability
to
it's
tough
in
the
list
in
this
issue's
list
to
say
we
need
to
take
a
look
at
this.
This
is
a
new
issue
that
was
submitted.
A
We
will
remove
that
once
it's
been
triaged
and
we've
either
categorized
it
or
we've
done
some
sort
of
action.
That's
been
set
on
it
now
another
one
that
you
may
have
seen
is
this
author
feedback
and
attention
now.
The
way
this
works
is
that
when
you
submit
an
issue
and
then
we
respond
to
you
and
we
are
waiting
for
you
to
come
back
and
respond
to
us,
we
tag
it
with
author
feedback.
A
If
this
person
hasn't
responded
in
seven
days,
we're
gonna
consider
this
issue
stale
and
we're
going
to
tag
it
as
no
recent
activity.
If
they
continue
to
be
unresponsive
for
another
seven
days,
we're
gonna
automatically
close
the
issue.
Now,
that's
the
bot
doing
it.
We
can
always
reopen
it.
Maybe
somebody
got
sick.
Maybe
somebody
couldn't
get
back
to
them.
That's
fine,
but
we're
trying
to
make
it.
A
Is
this
still
an
issue,
because
we
have
a
lot
of
updates
since
then,
and
this
may
have
already
gotten
fixed
and
so
it'll
be
flagged
as
as
it
needs
author
feedback.
And
if
you
don't
do
anything,
it's
just
gonna
get
closed
all
right.
So
the
next
thing
is
well.
How
do
I
go
through
and
make
contributions
to
this
I'm
gonna?
Try
and
do
this
as
quick
as
I
can
in
ten
minutes,
but
we'll
see
how
well
I
can
do
with
this.
A
Now,
if
I
back
up
I'll
see
that
there
it
is
right
there,
there's
that
there's
the
or
is
a
context
just
context
definition:
oh
I
had
it
earlier.
Where
is
it
it's
actually
well,
here,
I
cheated
a
little
bit
my
link
I
have
here.
Here's
word
should
be
pointing
to.
It
should
be
pointing
to
this
link,
so
let's
go
fix
that
so
what
I'm
gonna
do
is
I've
got
this
issue
right
here,
where's
that
3378.
A
So
let
me
go
over
to
the
issue
list
or
let
me
go
to
the
repository,
which
is
this
repository
right
here
too
many
things
open.
Let
me
close
in
these
tabs.
I
can
keep
track
of
where
I
am.
Okay,
the
first
thing
I
do
is
I'm
going
to
click
Fork
and
what
that's
gonna
do
is
that's
gonna,
create
a
copy
of
this
repository
in
my
github
account.
So
if
I
come
over
here
to
SP,
the
docs
apologies
for
the
ugly
picture.
A
If
I
come
over
here,
you
can
see
that
this
is
for
now
I
notice
in
this
case
that
it
shows
that
my
Fork
is
18
commits
behind
the
what
we
call
upstream
the
Microsoft
one.
That's
at
share
point
right:
my
master
branch
is
fit,
is
18
commits
behind
their
master
and
that's
not
good.
You
should
never
be
making
any
changes
to
the
master
branch
treat
that
is
read-only.
You
should
also
make
sure
that
your
master
branch
is
as
current
as
it
can
possibly
be.
So
how
do
I
do
that?
A
So
I'm
gonna
jump
over
here
to
my
command,
prompt
and
I'm,
going
to
show
you
a
little
trick
that
I
do
so
I've
gone
through
an
to
go
to
a
CD
repos,
a
CSP,
Doc's,
okay.
So,
let's
get
check
out,
let's
jump
over
to
the
master
branch
now
this
may
go
kind
of
quick
for
you,
because
I'm
kind
of
short
time,
but
just
understand
conceptually
what
it
is
and
there's
tons
of
documentation
shows
you
how
to
do
this
conceptually.
A
What
I
have
to
do
think
about
this
as
three
levels
of
a
git
repository
at
the
very
top?
Is
your
grandparent,
the
grandparent?
That's
the
Microsoft
repository,
that's
the
one
that
we
want
to.
We
want
to
make
a
change
to
the
next
step
down.
Is
your
parent?
That's
my
fork
of
that
same
repository
and
github,
and
then
the
child
is
the
one
I'm
currently
on.
That's
the
clone
of
my
fork
on
my
laptop.
A
The
next
thing,
I'm
going
to
do
is
I'm
going
to
say:
I
want
to
pull
in
I'm
gonna
do
a
rebase,
and
that
basically
says
take
my
existing
branch
that
I'm
on,
which
is
master
rebase
it
off
of
upstreams
master
branch,
and
what
that's
gonna
do
is
that's
gonna.
Take
all
the
changes
from
the
one
up
from
Microsoft
and
I'm
going
to
push
that
stuff
into
my
repository
and
then
I'm
gonna,
say
git
push.
This
shows
me
that
I
just
had
a
bunch
of
additional
things
that
were
added
to
my
local,
my
local
fork.
A
So
now
that
what
they
do
that
push
if
I
do
a
refresh
now
you
can
see
in
my
Fork
is
now
even
with
masters
now
I'm
current
I
can
get
going
with
this.
So
now,
let
me
jump
back
over
to
my
the
project
here.
Let's
go
fix,
let's
go
fix
that
problem
that
we
have
that
document.
So
let
me
find
where
that
broken
link
was
that
broken
link
is
in
Doc's,
schema,
declarative
context,
definition,
group
elements.
Let's
super
remember
their
docks
already
forgot.
It
docks,
schema,
declarative
context,
schema
declarative.
A
Declarative
which
one
we
declared
a
definition
group
context
definition
of
declarative
context.
Definition
group
element
is
that
right
element-
extensions,
yeah,
okay,
long
thing
there
right,
so
we're
looking
for
a
link
and
we're
looking
for
the
link
for
this
word
context
definition.
So
it's
fine
context,
definition
where's
our
link
scrolling
down.
What's
fine,
it's
not
third
is
there's
that
MSD
end
link.
So
let's
grab
the
correct
link,
which
is
right
here
and
let's
paste
that
in
we'll
save
our
changes.
Now
that
I've
saved
my
changes
with
this,
and
of
course
you
can
use
your
own.
A
A
I
strongly
recommend
you
should
only
have
one
commits
per
thing:
you're
fixing
make
things
atomic
one
commit
for
issue
that
you're
fixing,
so
I'm
gonna,
say
get
add
everything
that
I
have
and
the
new
get
commit
and
I'm
gonna
give
it
a
nice
descriptive
message
here:
I'm
gonna,
say
doc
fix.
Oh,
no,
sorry,
I'm
screwed,
that
up,
let's
go
I,
get
check
out,
beat
and
then
I'm
gonna
do
a
doc
fix.
A
A
The
reason
I'm
doing
this
is
that
I'm
I
should
never
be
making
changes
on
master
I
broke,
my
own
rule,
so
I
just
jumped
back
over
to
I've
created
a
new
branch
set.
This
up,
I'm
gonna,
say
now,
git
commit.
What
am
I
doing.
This
is
a
documentation
fix
for
issue
3378
and
then
I'll
come
down
here
and
I'll
say
this
fix
is
number
33
78.
Now,
if
you
do
it
like
that,
if
you
actually
say
fixes
and
put
the
number
there
when
this
issue
gets
committed,
its
gonna
automatically
close
the
associated
item.
A
So
now
I'm
gonna
say
get
push,
it's
gonna
say
hey!
You
don't
have
that
in
your
upstream
or
in
your
your
up
in
your
origin
and
I'll,
say
no
problem
now
I'll
go
ahead
and
push
it
in.
So
that's
what
that
just
did
that
last
command.
I
did
is
that's
creating
a
brand
new
branch
there
we
go
so
just
create
that
brand
new
branch
right
here
with
that
one
change,
so
I
can
now
say,
compare
and
do
a
pull
request.
I'm
gonna
take
this
branch
from
my
fork
and
push
it
to
the
SharePoint
repository.
A
His
master
branch
and
I
can
just
say:
fixing
broken
link
from
issue
3378
and
again
I
can
see
where
it
says,
fixes
I'm,
just
gonna
clean
this
up
a
bit
and
I'll
move
it
down
here
again.
There's
a
lot
of
explanation
on
how
to
do
this.
I'm
doing
it
like
that
and
I'm
also
gonna
say
like
this:
it
fixes
3378-
and
this
is
a
content
fix
right
now,
when
I
do
that,
I
can
preview.
What
I
did
but
check
this
out.
A
There's
a
cool
little
thing
you
can
do
with
this
I'm
gonna
say:
pull
request,
create
a
pull
request.
Now,
that's
gonna
go
to
through
this
whole
process
of
being
checked
here
by
Microsoft
to
make
sure
that
this
is
cool
and
that's
when
Microsoft,
that's
gonna,
look
at
this
stuff,
but
check
this
out
when
this,
when
this
PR
gets
merged.
If
I
hover
over
this
notice,
it
says
it
will
automatically
close
3378
and
if
I
go
over
to
the
actual
issue,
you
can
see
it's
even
blinking.
My
PR
over
here,
that's
really
important.
A
A
So
the
big
things
to
keep
in
mind
here
always
make
sure
that
your
fork
is
current,
or
at
least
his
master
branch
is
current
with
the
Microsoft
upstream
one.
That's
a
big
thing.
If
it's
not,
you
won't
look
at
that.
Thanks
to
us,
you
just
merged
it.
I
was
awesome,
so
best
I
just
went
ahead
and
I
checked
this
out.
Let's
go
to
the
issue
and
see
if
it
closed,
it
cut
off
boom
automatically
closed
and
it
was
closed
because
bested
it.
A
Thank
you
very
much
pretty
cool
right
and
see
how
nice
that
it
have
to
do
anything.
We
just
closed
an
issue
for
us,
so
it's
really
easy
to
contribute
this
stuff.
If
you
have
a
question,
ask
ask
a
question
about
this
stuff:
we'll
have
this
posted?
If
you
want,
we
actually
try
to
write
up
a
doc
on
this.
If
you
think
it's
helpful
and
we'll
put
it
in
the
wiki
on
how
to
how
to
contribute
and
stuff
and
how
to
how
to
keep
your
get
repository,
nice
and
clean,
so
cool,
that's
all
I've
got.