►
From YouTube: 2022 05 04 Inclusive Naming
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Go
from
there
welcome
this
is
the
jenkins
inclusive
naming
project
with
chico
africa.
Thanks
for
being
here,
it
is
the
fourth
of
may
I'm
going
to
share
my
screen
so
that
we
can
look.
Today's
objective
was
a
very
simple
one:
we've
got
30
minutes
where
we
would
like
to
show
how
to
do
a
multi-file
multi-component,
pull
request
from
the
github
web
user
interface
and,
and
so
that
is
that
I
think,
is
a
very
worthwhile
goal.
Catherine,
are
you
okay?
A
A
Well,
and
and
you're
welcome
to
ask
questions
during
this
discussion.
Absolutely,
but
let's
go
through
it,
so
so
what
I
did
was
I
used
the
inclusive
naming
sheet
to
try
to
find
a
plugin
that
needs
multiple
changes
and
where
did
I
put
that
sheet?
That
sheet
was
right
here,
just
a
minute
and
what
I,
what
I
found
was
that
the
subversion
plug-in
I
thought,
oh,
that's
an
old
enough
plug-in
that
it
might
need
multiple
changes.
A
A
A
This
one
is
really
embarrassing
because
it's
in
the
plug-in
documentation,
so
it
absolutely
should
be
changed
and
I
think
we've
got
three
examples
already
in
different
files.
This
is
the
old
changelog.
We
would
generally
not
revise
that.
So
we've
got
at
least
three
places
that
we
need
this
change,
one
in
in
the.
Let
me
go
find
it
in
the
copy
of
the
master
branch
one
in
here
where
we
see,
let's
find
that
there
we
go.
A
This
comment,
oh
with
master,
wait
a
sec;
yes,
yes,
so
that
is
talking
about
the
controller,
okay,
good
and
then
here
again
the
same
thing,
let's
be
sure
that
it's
visible
on
the
master
branch
and
there
it
is
okay
and
here's
a
use
of
the
word
slave.
So
there's
another
thing
that
needs
to
be
corrected,
and
now
this
one
in
readme.
A
A
C
A
A
Okay,
now
I'm
going
to
not
complete
the
task
here.
So
what
that
did?
Is
that
created
a
branch
notice
right
here?
The
branch
name
is
patch
dash
2
and
it's
some
number
it's
on
my
fork
and
it's
proposing
it
back
to
the
upstream,
but
I'm
going
to
cancel
out
of
this
and
remember
the
branch
name
patch
dash
2.,
okay,
so
I'm
not
going
to
create
the
pull
request.
I'm
actually
going
to
close
this
tab
completely
because
I'm
done
with
it.
I
don't
want
to
create
a
pull
request
for
that.
A
A
Propose:
oh,
no,
wait!
A
second
okay!
This!
I
think
I
may
have
to
cancel
this
because
it
didn't
quite
give
me
what
I
wanted.
Let
me
refresh
this
page,
I'm
going
to
go
into
edit
again
we're
going
to
see
if
I
can
make
this
work.
It
worked
when
I
tried
it
earlier
today:
master
okay,
looking
for
master,
make
the
change
here.
Controller.
A
A
Okay
and
I'm
going
to
hit
the
propose
changes
button,
no
it
created
as
patch
3.
That
was
not
what
I
wanted.
I
know
that
it
worked
for
me
earlier
so
now
I'm
going
to
have
to
go
figure
out
why
it
worked
for
oh,
oh,
oh,
I
know
what
I
did
earlier.
Sorry,
peace
and
catherine.
You
get
to
watch
me
making
mistakes
once
again.
Here's
what
we're
going
to
do
to
fix
my
mistake.
Okay,
remember
that
I
I
started
with
the
first
tab
that
was
named
patch
2.
A
in
this
tab.
In
the
second
place
that
I
need
to
make
the
change,
I
need
to
set
my
branch
to
patch
dash
2
and
then
make
the
change
there.
So
the
mistake
I
made
was,
I
did
not
set
my
branch
so
throw
this
change
away,
and
I
am
going
to
here
in
this
file,
cancel
changes
and
switch
now
notice,
I'm
in
the
jenkins
ci
subversion
plugin.
I
need
to
change
this
from
jenkins
ci
to
my
fork,
so
I'm
editing
the
url
to
put
my
username
in
up
at
the
top.
A
A
Now
I've
got
the
right
context
now
I
go
find
that
workspace
updater
thing
and
it
was
where
now
I've
unfortunately
lost
track
of
my
it
was
called
well,
let's
see
if
I
can
search
in
here,
I
don't
think
I
can
nope
okay,
so
back
to
the
search
here
we
go,
we
have
to
go
find
it.
My
place
that
I
needed
to
edit
was
not
that
one,
not
that
one,
not
that
one,
not
that
one,
not
that
one,
not
that
one,
this
one!
C
A
Exactly
well,
and-
and
that's
that's
correct-
is
that
okay,
a
pull
request,
is
just
submitted
from
a
branch
and
by
creating
a
branch
and
that's
what
I
did
in
the
first
step
was
create
a
branch
I
created
a
branch
and
then
made
changes
on
the
branch
and
then
switched
the
context
in
the
other
windows
to
also
use
that
same
brand
new
branch
and
then
made
the
changes
there
as
well.
So
what
I'll?
What
the
end
result
will
be
is
multiple
commits
on
a
single
branch
that
contain
the
different
things
that
I
wanted
to
change.
A
A
A
Naming
for
javadoc
okay,
so
I'm
going
to
commit
this
one
now
now,
if
we
look
at
the
list
of
commits
on
this
branch,
we
would
see
that
there
are
two
commits
on
this
branch
now
and
now
I
want
to
do
the
same
thing
again
with
that
oops.
I
just
moved
my
window
around
hang
on
back
here,
wrong,
keystrokes!
A
A
A
I
thought
I
had
proven
that
this.
Okay,
maybe
I
need
to
look
for
slave.
A
B
I've
seen
I've
seen
I've
seen
the
term
master.
B
A
B
Realized-
and
I
don't
know
if
this
is
something
someone
else
has
experienced,
if
you
search
in
lower
cups,
it
does
bring
up
some
terms.
A
A
A
A
A
If
that
happens,
to
not
be
available
for
you,
and
sometimes
it's
not.
You
can
also
click.
This
thing
right
here
notice.
This
contribute
word
that
thing
is
always
available,
and
so,
when
I'm
going
to
click
it
to
take
it
through,
the
the
more
general
case
so
contribute
whoops
contribute.
It
says
this
branch
is
three
commits
and
by
this
branch
it
means
patch.
Two
is
three
commits
ahead
of
master.
So
now
I'm
opening
the
pull
request,
and
now
now
I
have
to
fill
in
inclusive
naming
in
docs
and
javadoc.
A
In
doc
and
javadoc
and
this
you're
familiar
with
right
be
sure
I'm
doing
it
from
a
branch.
Yes,
I
am,
the
branch
is
patch
two
ensure
that
the
pull
request
describes
it
yep
describe
what
you
did
yes
linked
to
relevant
issues.
There
aren't
any
so
that's
okay
and
I'm
not
providing
any
additional
tests.
So
I'm
going
to
make
that
a
strikethrough.