►
From YouTube: How to Test A Pull Request in The Core Issue Queue
Description
If you would like to get started contributing to Backdrop Core, helping to test some existing Pull Requests is a great way to start. You don't need to be able to write code to help test Pull Requests. This explains the process and shows you how to find a good issue and test a Pull Request.
A
Hello
friends,
my
name
is
tim
erickson.
I
am
with
simplo
by
triplo
today,
we're
doing
a
backdrop
cms
contribution,
video.
This
is
about
how
you
and
anyone
else
can
help
make
backdrop
better,
and
today's
topic
is
going
to
be
testing
core
pull
requests
to
start
out.
Let's
do
a
really
quick
definition
of
what
a
pull
request
is
when
a
member
of
the
backdrop,
community
or
any
open
source
community
or
any
open
source
project
user
decides
that
they
want
to
fix
a
bug
or
add
a
new
feature,
one
of
the
features
of
open
source
code.
A
What
they
do.
The
first
thing
they
do
is
they
create
a
fort
of
the
project
and
a
fork
of
the
project
just
means
they
take
a
copy
of
the
project
or
the
code
wherever
it
is
at
that
particular
moment
and
and
we
we're
going
to
be
using
github
today,
a
common
tool
there's
also
a
tool
called
bitbucket.
There
are
other
ways
to
do
this,
but
basically
within
bitbucket
or
or
github
you
copy
the
repo,
and
now
you
have
your
own
copy
of
the
software
in
theory,
you
could
run
that
and
maintain
it
yourself.
A
It
could
fork
the
project
and
never
go
back
to
the
original,
but
most
of
the
time,
especially
in
a
project
like
backdrop,
you
don't
want
to
have
to
keep
backdrop
up
to
date
by
yourself.
You
want
to
continue
to
use
the
core
repo,
the
main
repo,
because
lots
of
other
people
are
helping
fix
bugs
too
there
are
also
helping
fix
bugs.
So
what
you
want
to
do
is
fix
the
bug
that
bothers
you
or
add
the
feature
that
you
that
you
want,
and
then
you
want
to
get
that
back
into
the
main
repository.
A
So
you
make
the
changes
and
then
you
create
a
pr
a
pull
request
and
the
pull
request
is
basically
asking
a
maintainer
of
the
original
project.
Will
you
pull
my
request
or
my
excuse
me:
will
you
pull
my
change
back
into
the
main
project?
Then
the
project
maintainer,
of
course,
has
to
evaluate
one.
Do
they
want
that
bug,
fix
and
or
feature
in
the
main
project
and
two?
A
If,
if
they
do,
does
it
work
and
is
the
code
good
because
they
don't
want
to
introduce
confusing
or
poorly
written
code
that
might
cause
problems
down
the
road?
On
a
very
high
level,
the
pr
pull
request
process
in
backdrop
is
is
similar
to
what
I
just
said.
A
pro
any
member
of
the
community
that
finds
a
bug
has
the
ability
to
go
in
and
fix
it
and
they
submit
a
pull
request.
A
A
So
when
a
contributor
submits
a
poll
request
to
backdrop
core
in
particular
and
there's,
you
know,
there's
a
little
bit
of
a
culture
and
process
around
this.
That
varies
from
project
to
project,
and
even
the
project
varies
some
from
core
pull
requests
to
individual
contrib
projects.
In
the
backdrop
community,
what
we're
really
talking
about
today
is
mostly
focusing
on
core,
although
most
of
what
we
say
could
or
might
also
apply
to
contrib
projects
anyways.
If
you
make
a
once,
a
a
pull
request
is
submitted
to
core
it's
probably
in
one
of
two
stages.
A
Sometimes
pull
requests
are
just
proof
of
concept
where
somebody
has
an
idea
for
backdrop.
They
write
up
a
pull
request
and
they
submit
it
and
really
all
they're
looking
for
is
feedback.
It's
not
ready
for
final
testing
and
it's
not
ready
for
code
review.
They
just
want
to
know
people
like
the
idea
and
and
usually
they'll
say
so
in
the
issue
queue
but
oftentimes
and
most
of
the
time
I
think,
once
a
poll
request
is
submitted.
A
That
means
that
the
original
submitter
is
looking
for
someone
to
test
and
provide
feedback.
In
the
backdrop
core
issue
queue,
you
need
at
least
two
different
people
to
participate
in
a
pull
request.
You
need
the
original
person
and
at
least
one
other
person
to
review
and
or
test
the
pull
request
before.
It
then
gets
reviewed
by
a
core
committer
now,
sometimes
that
process
is
divided
into
three
people,
because
we
have
somebody
who
submits
the
pull
request.
A
Somebody
who
tests
it
then
somebody
who
else
who
re
reviews
it
the
tester
and
the
reviewer-
can
be
the
same
person,
but
they
don't
need
to
be,
and
this
is
a
lot
because
there's
a
lot
of
us
in
the
community
that
really
aren't
capable
of
of
providing
an
in-depth
code
review
to
determine
whether
or
not
the
code
is
ready,
but
we
are
completely
capable
of
testing
to
see
if
the
pull
request
does
what
it's
supposed
to,
and
this
video
is
all
about
how
you
you
can
test
just
about
anybody.
A
Who's
familiar
and
work
with
backdrop
has
the
the
skills
and
ability
to
do
testing
in
the
ish
core
issue
queue
anyways.
So,
finally,
so
a
contributor
has
submitted
a
pull
request.
A
A
Sometimes
the
the
core
committer
will
make
some
comments
and
push
the
the
pr
the
pull
request
back
and
say:
hey.
We
need
to
do
some
more
work
or
we
need
to
do
some
additional
testing
on
this,
but
anyways.
That's
the
basic
process
of
of
getting
a
pull
request
into
core.
A
So
what
we're
going
to
talk
about
is
how
you
can
help
us
test
issues
in
the
core
issue
queue.
So
to
start
out
here,
I've
opened
up
the
core
issue:
queue
which
could
be
found
at
github.com,
slash
backdrop,
slash
backdrop
issues
and
if
you
click
on
that
you'll
see,
we
have
over
2.3
000,
open
issues
and
look
in
the
backdrop
issue
cube.
A
Don't
let
that
number
scare
you
this
is
all
2.3
000
different
things
that
people
have
identified
over
the
last
six
years
that
they
would
like
to
change
or
fix
and
backdrop,
and
it
seems
like
a
lot
of
things,
but
it's
not
that
unusual
in
software
this
complicated,
if
we
click
on
this,
we'll
also
see
that
there
are
over
3000
issues
that
have
been
closed.
A
So
we've
got
over
a
fifty
percent,
close
rate
on
on
issues
that
have
been
opened.
Some
of
these
issues
that
are
open
might
be
meta
issues
which
are
issues
that
are
sort
of
larger
groups
of
issues.
Some
of
them
might
be
duplicates
that
haven't
been
caught.
Yet,
if
we
find
duplicates,
we
try
to
close
one
of
them.
Some
of
them
might
be
things
that
will
never
happen.
Some
of
them
are
might
even
just
be
questions
that
people
have
asked
in
the
issue
too.
A
But
the
point
is
there
are
a
lot
of
issues
in
the
issue,
queue
and
surprisingly,
there's
also
a
lot
of
pull
requests.
A
Actually,
if
we
go
back
to
the,
if
I
click
on
backdrop
or
the
I'm
sorry
the
backdrop
code
repository,
we
can
see
that
there's
over
600
there's
634
pull
requests
currently
submitted
to
backdrop,
and
some
of
these
are
probably
duplicates.
Some
of
them
are
proof
of
concept
that
maybe
are
just
something
somebody
submitted
it
sometime,
but
a
lot
of
these
are
waiting
for
review
and
can't
get
into
to
core
until
somebody
tests
them
and
reviews
them.
A
A
The
first
thing
you
want
to
do-
or
first
thing
you
probably
need
to
recognize-
is
that
by
default,
the
core
issue
queue
is
supported
or
sorted
into
the
most
recently
updated
issue.
We
can,
you
know,
sort
this
in
different
ways
over
here.
We
can
sort
by
the
newest
issue
that
was
created
if
we
want
to
see
what
hap,
what
the
most
recent
issue,
here's
one
that
I
created
earlier
today.
A
Anyways,
so
we've
had
it
looks
like
four
issues
have
been
opened
today
alone
and-
and
you
know,
that's
how
we
get
to
to
2000
open
issues
is
that
a
handful
of
issues
can
be
opened
in
any
given
day,
and
you
know
again,
some
are
closed
every
day
as
well,
but
unfortunately
we
tend
to
open
them
faster
than
we
close
them,
but
but
we
think
that's
not
a
bad
thing.
A
We
could
also
sort
by
the
oldest
if
we
click
on
that
we're
going
to
see
the
the
very
oldest
active
issue
in
the
core
issue.
Queue
is
from
september
11
2013..
A
So
this
is
almost
seven
eight
years
old
and
we
we
have
issues
that
are
this
old
that
do
get
fixed
and
added
into
core.
Some
of
these
are
feature
requests
like
I'm
just
noticing.
This
include
the
tour
module
in
core.
This
was
a
request.
Somebody
made
eight
years
ago,
and
I
don't
think
that
there's
really
a
an
overall
desire
to
include
the
court,
the
tour
module
in
core
but
nobody's
ever
closed
this
issue,
because
it
can
always
be
discussed
and
read
that
you
know
and
re-happen
but
anyways.
A
Just
because
there's
you
know
2
200
issues
open
a
lot
of
these
might
be
things
like
like
this.
This
request
for
a
particular
module
that
may
never
happen,
but
we
keep
it
open
so
that
the
the
possibility
is
always
there.
What
I
like
to
do
is
sort
by
the
most
recently
commented
on
or
the
most
recently
updated.
A
Here
we
go.
This
issue
was
updated
eight
hours
ago
this
one
eight
hours
ago,
this
one
10
hours
ago.
So
we
can
see
that
quite
a
few
issues
have
been
updated
today
alone,
maybe
10
to
could
be
even
20.
Issues
have
had
some
activity
today,
so
there's
a
lot
of
there's
a
whole,
a
fairly
decent
sized
group
of
people
that
are
active
in
the
issue,
queue
and
they
are
discussing
reviewing
each
other's
work
and
testing
issues
every
day.
A
We
have
some
projects,
don't
worry
about
those
milestones
thing
we're
going
to
focus
on
today.
Is
a
label
and
we're
going
to
look
for
the
label
that
needs
testing
pr
needs
testing.
That
means
this
issue
has
a
pull
request
right.
It's
not
just
an
idea.
A
A
One
might
argue
that
one
well
that
it's
it's
sometimes
good
to
test
ones
that
have
recent
activity,
because
if
they
have
recent
activity,
that
means
other
people
are
engaged
with
that
particular
issue,
or
we
could,
for
example,
see
go
to
the
least
recently
updated
issue
that
calls
for
testing,
and
we
could
start
testing
that,
as
I
look
at
that
one
use
database
independent
calls
to
initialize
the
testing
cache.
A
Well,
if
that's
giving
you
a
headache,
it
is
me
too.
I
have
no.
I
would
have
no
idea
how
to
test
that,
and
that's
probably
why
it's
been
there
for
a
long
time
is
that
we're
lacking
people
with
the
motivation
or
skill
to
test
that.
But
what
I
might
do
is
is
go
to
some
of
these
old
ones
and
look
for
one
that
that
might
like
fix
titles
of
menu
admin
pages.
That
seems
like
a
pretty
reasonable
one,
so
I
click
on
that.
A
The
first
thing
I'm
going
to
do
is
sort
of
read
the
issue,
see
if
it's
something
I
understand
and
think
I
can
can
test,
I'm
going
to
look
to
see
if
there's
a
pull
request
that
well,
there
should
be
if
it
has
the
needs
testing
tag,
although
it
isn't,
it's
not
impossible
that
sometimes
the
tags
are
incorrect
and
if
you
find
that
you
should
go
ahead
and
make
a
note,
you
know
anything
you
find
or
questions
you
have,
while
you're
browsing
in
the
issue,
you
should
go
ahead
and
contribute
them
and
you
can
help
move
issues
forward
in
a
lot
of
different
ways.
A
Okay,
I've
taken
a
minute
to
sort
of
scan
through
the
issue.
I
still,
I
don't
understand
it
exactly
other
than
what
I
think
is
happening
here
is
that
we
want
to
change
this.
The
the
title
of
this
administrative
page
from
something
like
my
menu
to
something
like
edit
menu
links,
bw
panda,
does
a
simple
pull
request
as
we
scan
through
the
history.
A
A
He
actually
submits
an
alternative
pull
request.
I
think
he
gets
a
little
bit
more
feedback
submits
another
pull
request.
We
can
see
the
last
pull
request.
Was
I
updated
the
pr
a
bit
to
also
remove
okay,
some
unnecessary
calls,
so
basically
he
makes
a
few
more
changes,
but
anyways
we
have
a
pull
request.
That's
been
sitting
here
for
over
three
years.
It
seems
relatively
simple
all
it
needs.
The
next
step
would
be
to
do
testing
and
then
a
code
review,
and
so
this
seems
like
a
really
good
issue
to
maybe
move
forward
in
the
issue.
A
Now
the
pro
we've
got
two
problems,
one
of
which
is.
We
have
two
pull
requests.
However,
we
can
see
that
one
of
these
was
made
by
bw
panda
when
I
hover
over
it.
I
can
see
that
it
comes
from
vw,
pandas
repository,
and
I
know
that
he
did
the
earlier
one
and
then
quick
sketch
updated
it.
So
as
I
hover
over
this,
I
can
see
that
that
this
is
quick,
sketches,
pull
review
and
this
one
is
more
recent.
A
So
that's
the
one
I
would
want
to
review.
So
I'm
going
to
go
ahead
and
click
on
that,
and
what
I
want
to
do
here
is
look
for
a
sandbox
and
every
pull
every
pull
request
automatically
generates
a
sandbox
where
you
can
log
in
and
test
the
pull
request.
A
Now,
I'm
anticipating
a
problem
because
we
chose
to
go
with
a
very
old
pull
request.
My
suspicion
is
that
the
sandbox
isn't
going
to
work
and
sure
enough.
I
click
on
it
and
I
get
this
sort
of
russian
landing
page,
which
is
not
something
to
be
concerned
and
doesn't
mean
that
our
site
has
been
hacked.
This
just
has
to
do
with
the
tools
I'm
familiar
with
this
page.
A
I've
seen
it
before
this
is
the
tool
we
used
to
use
to
do
our
pull
requests,
but
this
poll
we're
not
using
that
tool
anymore,
which
is
partially
why
we
can't
get
the
pull
request.
So
normally,
what
I
would
do
is
go
back
to
the
pull
request
and
say
and
post
a
note
saying
you
won't
be
able
to
reset
the
the
pull
request
to
generate
a
new
sandbox.
A
So
you
go
ahead
and
you
put
a
comment
and
ask
for
that
anyways.
I
was
hoping
that
I
might
be
able
to
go
ahead
and
get
this
reset
right
away,
but
I
can't
so
what
this
means
is
that
that's
really
as
far
as
we
can
go
on
this
issue,
but
we
we
have
potentially
helped
move.
This
forward
issue
be
this
this
issue
forward,
because
we
have
reminded
the
folks
who
were
involved
in
this
issue
originally
that
it's
still
out
there.
A
It
still
needs
some
work
and
that
we
or
somebody
else
might
be
willing
to
test
it.
If
we
could
get
a
working
sandbox
and
hopefully
they
will
do
that
for
us.
This
is
something
I
maybe
work
on
myself
later,
so
I'll
come
back
to
it.
In
the
meantime,
it
puts
us
back
in
the
pull
request
queue.
A
Looking
for
another
issue
to
work
on,
I
do
have
an
issue
picked
out
to
look
at
and
it's
called
allow
display
settings
for
book
navigation
and
basically,
if
you're
familiar
with
the
book
module
in
backdrop,
what
this
this
issue
has
to
do
with
it.
Well,
the
book
module
allows
you
to
aggregate
a
bunch
of
pages
into
what's
called
a
book,
and
a
book
has
a
little
a
special
navigation
at
the
bottom.
A
Is
I'm
going
to
sort
of
scan
through
the
issue?
I
picked
this
issue,
partly
because
when
it's
an
understandable
issue,
also
because
it
isn't
very
long,
we
could.
It
only
has
about
eight
or
nine
comments,
whereas
some
issues
have
up
to
100
or
more
comments,
and
it
can
take
you
a
little
while
to
figure
out
what
the
status
of
the
issue
is.
A
So
the
first
thing
I'm
going
to
do
in
an
issue
like
this
is
there
there
are.
Actually
there
are
no
screens
well,
there
are.
There
are
some
screenshots,
but
not
enough
for
me
to
make
absolutely
clear
what's
going
on
and
I
oftentimes
want
to
see
what
does
the
problem
look
like
before
I
do
the
test,
so
then
I
can
test
it
with
the
pull
request
and
see
what
happens.
So.
A
A
I
went
ahead
and
took
a
fresh
backdrop
site,
but
fortunately
I
know
that
the
book
module
is
not
on
by
default,
it's
in
core,
but
I
had
to
go
to
the
list
modules
page
and
turn
it
on.
Sometimes
this
happens
with
both
the
sandboxes
onbackdropcms.org
and
the
github
sandboxes,
and
we
just
have
to
wait
a
second
for
them
to
reload.
So
now
I
go
here.
I
go
to
the
book
module
and
we
can
see
that
I
did
go
ahead
and
enable
that
before
we
got
here.
A
So
if
I
go
to
my
backdrop
book,
we
can
see
that
what
this
issue
is
about
are
these
links
at
the
bottom.
This
is
the
content.
A
This
is
the
homepage
for
our
book
and
then
it's
showing
me
all
the
main
pages
in
in
the
book,
and
it's
giving
me
some
navigation,
so
I
can
navigate
to
the
next
page
and
then
on
the
next
page.
I
now
have
the
ability
to
navigate
back
to
the
previous
page,
go
to
the
next
page
or
go
back
up
to
the
top.
A
A
So,
basically,
what
the
issue
is
is
asking
for
is:
can
we
create
a
user
interface
that
will
allow
me
to
to
turn
that
off?
Okay,
now
we're
going
to
jump
ahead
and
we're
going
to
go
ahead
and
click
on
the
pull
request
over
here
for
this
issue,
we're
going
to
scroll
down
until
we
find
the
last
sometimes
there'll
be
more
than
one
sandbox
listed,
because
some
older
sandboxes
will
still
be
open.
I
don't
think
that's
happening
anymore,
but
but
in
the
past
it
did
anyways.
A
A
So
that
looks
to
me
like
it's
part
of
the
the
fix,
and
then
I
can
go
back
to
my
test.
Site
is
sort
of
a
control
group
and
I
can
go
to
books
and
I
can
go
to
settings
and
I
can
see
that
those
settings
aren't
here.
So
the
only
settings
we
had
before
this
pull
request
were
these
at
the
top,
the
these
content
type
content
types
allowed
in
book,
outlines
and
content
types
for
pages,
and
now
what
I
can
do
is
go
here.
A
I
see
we
have
these
extra
settings
and
I
can
just
sort
of
test
them
out,
and
so
the
first
thing
I'm
going
to
do
is
sort
of
disable.
Both
of
these
links.
A
Click
save
go
back
to
the
home
page,
actually
go
to
the
content,
page
and
click
on
one
of
the
pages
in
my
book,
and
I
can
see
right
away.
There
aren't
any
navigation
links
below
because
I
turned
those
off.
I
can
go
back
to
another
page
also
in
the
book.
This
is
also
not
there.
I
could
go
to
the
book
edit
orders
and
titles.
A
Okay
and
those
are
the
only
two
pages-
well
plus
the
main
page
in
the
book,
but
none
of
these
none
of
these
have
any
of
that
navigation,
so
that
seems
to
be
working
as
expected.
Now.
My
goal,
unfortunately,
is
to
kind
of
try
and
break
this.
I
want
to
find
bugs
before
they
get
committed
to
core.
So
I
want
to
keep
pushing
this.
I
don't
want
to
like
really
quickly
say:
hey
yeah.
A
A
A
I
want
to
go
to
the
view
page
there's
that
there
so
now,
let's,
let's
go
back
to
books
and
go
to
settings
and
let's
turn
that
off,
but
click
display
book
navigation
now,
there's
two
different
options:
the
table
of
contents
and
the
previous
next
links
and
tell
you
what
we'll
go
ahead
and
turn
both
of
those
on
so
now
we
should
see
all
of
those,
but
not
the
add
child
links.
A
A
This
is
the
the
main
page
for
the
book,
but
as
we
click
on
the
others,
we
don't
actually
see
the
outline,
but
we
do
see
the
we
see
the
navigation
and
now,
when
we
again,
when
we
get
back
to
the
main
page,
we
should
see
that
again
we
don't
see
the
ad
child
links.
So
on
the
whole,
I
think
this
is
enough
for
me
to
say
you
know
what
this
is
working
as
expected.
A
Now
again,
depending
on
how
much
time
I
have
I
you
know,
I
might
try
harder
to
break
this
and
find
scenarios
like
one
thing
I
did
do
was
I
did
include.
We
have
one
child
page,
that's
a
book
page
and
we
have
another
child
page,
that's
a
post
or
that's
a
regular
backdrop
page.
So
we've
tried
two
different
content
types.
A
I
could
also
go
to
the
regular
page
and
make
sure
that
none
of
the
book
stuff
is
showing
up
here,
because
this
isn't
part
of
the
book
and
it's
not
and
just
think
about
anything
else.
I
could
think
of
doing.
I
might
try
logging
in
as
a
different
role
to
see
if
I
can
break
it.
That
way,
but
I
want
to
do
my
best
to
sort
of
test
and
make
sure
this
is
working
for
the
purposes
of
this
video.
I
think
we're
going
to
say
it's
good.
A
A
I'm
not
sure
if
that's
that
helpful,
so
I
might
do
this,
I'm
not,
and
then
what
I
would
do
is
go
up
here
and
remove
the
needs
testing
and
if
you
don't
have,
if
you,
if
you're
unable
to
change
these
labels,
then
just
put
a
note
in
the
issue:
queue
saying
that
you
were
not
able
to
change
the
labels.
Sometimes
when
you
first
try
to
test
issues,
you
won't
have
this
permission,
but
then
you'll
get
it
quickly
afterwards,
either
we'll
give
it
to
to
you
manually
or
you
might
even
get
it
automatically.
A
There
we
go
and
so
those
those
labels
have
been
changed
and
now
the
next
step
is
somebody
else
has
to
come
along
and
do
a
code
review,
and
I
am
probably
not
the
best
person
to
do
that
code
review,
so
I'm
going
to
leave.
I
could
do
that
if
I'm,
if,
if,
if
you
or
I
have
the
php
skills
that
we
think
we
can
do
a
competent
code
review,
we
should
go
ahead
and
do
that.
However,
we
won't
talk
about
it.
That
can
be
another
video
for
my
purposes.
A
This
is,
as
far
as
I
can
go
in
this
issue,
and
I
need
to
leave
it
for
someone
else
to
do
the
code
review
and
then
for
a
court
committer
to
commit
it,
we've
taken
kind
of
an
old
issue
and
moved
it
forward.
Anyways.
I
think
that
is
all
we
are
going
to
do
today.
This
is
one
example
of
how
you
can
review
a
pull
request
in
the
core
issue:
queue
and
help
make
backdrop
better.