►
Description
During this Community Office hours call, James Rushford is walking us through how he is tackling a front-end issue.
Meeting's Agenda: https://bit.ly/3y8fqZc
Contribute to GitLab: https://about.gitlab.com/community/co...
Join the next office hour call: https://www.meetup.com/gitlab-virtual...
B
A
Perfect,
hello,
everyone
hi
welcome
to
another
community
office,
article
happy
to
see
you
all,
I'm
christopher
harakis,
contributor
program
manager
and
before
we
begin
today
we
have
a
special
guest
james
rashford.
Before
I
introduce
him
right,
I
think
it
would
be
nice
like
to
introduce
ourselves
briefly.
Where
are
we?
I
can?
A
I
can
begin
I'm
based
in
in
right
now:
burning
berlin,
35
degrees
celsius
and
38,
sorry
and
melting,
so
yeah,
I'm
the
tribute
program
manager
and
I'm
my
my
role
at
gitlab
is
like
to
help
people
who
want
to
contribute
to
kids
love
or
they
they're,
going
to
or
they'd
be
contributing
to
make
their
life
easier
and
rewarding
yeah.
So
I'm
gonna
go
through
the
list
of
people
here
on
zoom
that
we
have
here
so
the
introductions,
so
fatima
is
after
me,
fatima
yeah
hi.
A
I'm
fatima
I
am
a
developer
evangelist
focused
on
community
stuff
on
the
community
relations
team.
At
get
lab
excited
to
be
here.
Gonna
stay
off
camera.
It's
not
feeling
well
today,
after
me
is
I
guess
we
have
different
lists,
but
I
will
pass
it
to
jamie.
A
Thank
you
so
I'm
jamie
rochelle.
I
also
sit
on
the
community
relations
team
with
fatsuma
and
christos.
I
am
an
evangelist
program
manager
and
I
help
with
our
community
engagement
in
regards
to
our
advocacy
program,
known
as
the
get
lab
heroes
and
our
meetups,
and
also
our
beyond
code
twitter
space
series
as
well.
A
Hi,
I'm
marshall
miller.
This
is
actually
my
first
one.
I
wanted
to
give
it
a
look.
I
work
in
in
education,
I'm
the
director
of
online
learning
for
college
in
pennsylvania
and
I'm
very
excited
to
contribute,
and
I
want
to
see
you
know
we
used
git
lab
at
our
school
and
I
kind
of
just
wanted
to
see
how
I
can
give
back
and
contribute-
and
this
looks
like
a
good
way
to
get
involved.
A
Marco,
I
want
to
go
next.
Oh,
I
didn't
hear
sorry,
yes,
so
yeah,
I'm
arco,
I'm
based
in
italy
and
I've
been
our
contributor
for
the
past
almost
four
months
and
yeah.
Basically,
this
is
it.
I
am
not
a
web
developer,
I'm
mainly
a
developer.
B
A
No
worries
no
worries:
okay,
measured,
okay,
I'm
measured,
I'm
a
frontend
engineer,
I'm
based
in
cairo,
egypt
here
and
I'm
working
with
established
and
yeah
excited
to
be
here.
A
Do
you
want
to
go
next,
yeah
sure
hi,
guys,
I'm
sridhar.
I
work
as
a
front-end
engineer
at
beacon
stack,
I'm
from
bangalore,
india,
I'm
a
contributor
at
kit
lab
excited
to
be
here
thanks.
C
Yes,
daniel
danielle
danielle
daniel,
as
you
want
so
guys,
I'm
daniel
benny
foseka,
I'm
brazilian
guy,
but
I'm
living
in
belgium.
C
So
I
like
these
changements
and
I'm
here
just
to
change,
try
to
to
enter
this
gitlab
world
and
I'm
software
engineer
web
developers
with
tech,
as
you
want
call
me,
so
I'm
here
to
start
to
learn
how
to
contribute
in
and
get
on
this
gathering.
Okay,
there
is
another
one.
I
can
see
why
I
can
pass
my
let's
go
with
yeah.
A
Okay,
they
want
only
to
listen,
that's
okay!
I
also,
if
you
want
to
write
something
itamar
in
gp
in
the
chat
feel
free
to
introduce
yourself
or
in
the
talk.
That's
absolutely
fine,
hello
from
brazil
there
as
well
they're
enjoying
from
brazil,
okay.
So
with
no
further
ado.
Last
but
not
least,
also
our
main
speaker
for
today,
james
with
drumroll.
A
B
Cool,
so
I'm
james,
I'm
from
australia,
but
I
live
in
berlin,
so
I
used
to
work
in
advertising
sales
for
like
10
years
and
then
around
three
and
a
half.
Four
years
ago
I
started
to.
I
was
working
on
this
spreadsheet
and
I
wanted
to
update
it
automatically
and
my
friend
who
works
at
getlab
was
like.
Oh
did
you
know
you
can
use
javascript
in
google
sheets,
which
I
didn't,
and
then
I
learnt
javascript
so
that
I
could
update
this
spreadsheet
and
I
really
enjoyed
it.
B
So
I
said:
can
you
do
this
as
a
job
full
time
and
he
said
that's
pretty
much
what
he
did
as
a
front-end
developer.
So
I
got
a
internship
as
a
front-end
developer
that
was
around
three
years
ago
and
I
just
started
at
get
lab
just
in
april,
so
I'm
new
to
gitlab,
I'm
also
reasonably
new
to
engineering.
So
please
don't
mind
my
mistakes
so
also.
I
wanted
to
say
that
I
I
teach
at
a
volunteer
code
school
in
berlin,
but
I
normally
teach
beginners.
B
So
I
have
done
a
bit
of
quite
a
lot
of
live
coding,
but
you're
all
far
more
senior
than
I
would
normally
demonstrate
too.
So,
if
I
like,
don't
feel
offended,
if
you
feel
like
I'm
explaining
over
explaining
some
simple
things
yeah,
that's
me
show
me
the
jump
starting
sure
great,
so
share
my
screen.
B
B
So,
to
find
a
issue
to
work
on,
I
just
looked
at
this
list
of
front-end
tasks
and
then
in
the
list
I
found
that
most
of
the
ones
at
the
top
were
already
being
worked
on.
So
what
I
did
was
I
changed.
It
changed
this
to
created.
B
I
looked
for
things
that
were
created
in
the
last
couple
of
weeks,
so
yeah
created
descending
anyway,
so
I
had
to
look
through
it
before
so
I
picked
something
that
was
reasonably
recent.
So
then
the
information
is
going
to
be
up
to
date
and
probably
nobody
is
already
working
on
it.
So
I've
picked
this
task.
It's
completely
separate
to
what
I
normally
work
in.
B
B
B
Oh
no,
okay,
so
this
takes
you
to
the
jobs
page,
there's
a
filter
that
you
can
set
here,
but
it
is
not
connected
to
the
url
and
what
we
wanted
to
do.
What
we
want
to
do
is
connect
it
to
the
url.
It's
also
not
connected
to
the
page.
So
if
you
say
page
two
that
also
does
not
stay.
So
what
we
want
to
do
is
add
the
search
filters
into
the
url
search
parameters
on
this
page.
B
So
the
first
thing
I
wanted
to
do
was
I.
I
noticed
that
in
so
in
trying
to
tackle
this.
We
want
to
make
sure
that
I
do
it.
We
do
it
in
the
most
simple
way
possible,
because
if
we
create
like
a
custom
solution
for
every
single
part,
our
code
base
grows
unmanageable.
So
what
we
want
to
do
is
find
a
way.
Is
there
or
think
about?
Is
there
a
way
we
can
achieve
this?
That
is,
writing
as
little
code
as
possible.
That
is
our
goal.
B
So
I
noticed
that
in
when
you
search
for
issues
the
url
is
connected.
So
what
I
want
where
I
will
start
is,
I
will
look
at
how
this
works
and
see
if
we
can
use
that
same
logic
elsewhere.
Now
I
did
run
through
this
before
so
I'm
going
to
run
through
very
quickly.
That's
not
quite
thinking
in
real
time,
but
it's
it's
sped
up
for
your
enjoyment.
B
Otherwise,
you'll
just
see
me
banging
my
head
against
the
wall
for
a
while.
So
the
first
thing
I'm
going
to
do
as
well
before
I
forget
is
I'll
just
create
a
new
branch.
You
can
use
the
branch
name
here
and
create
a
new
merge
request.
So,
instead
of
creating
new
merge
requests,
I'm
just
going
to
take
this
branch
name.
B
Okay
cool,
so
what
I
want
to
know
is
how
does
this
work
and
why
like?
How
does
it
talk
to
the
url?
So
what
I'll
do
first
is:
let's
so
now
we're
in
the
gdk,
so
this
is
running
locally,
so
we
want
to
find
out.
Oh
no,
that's
not
good!
Please.
B
What
I
want
to
do
is
find
what
is
this
component
called
and
how
does
it
work
so
it's
easier
to
do
in
the
gdk,
because
you
can
use
view
dev
tools,
so
in
view
you
can
see
that
each
of
so
the
way
git
lab
pages
are
set
up
is
a
little
bit
unusual
because
of
the
complexity
of
the
system.
So
there's
actually
six
different
view,
applications
running
here,
so
there's
you
can
see
each
one
and
what
we're
looking
for
is
this
search
function?
B
So
it's
it's
actually
in
this
application
and
then
it's
called
jobs,
filter
search,
so
we'll
look
at
our
code
for
jobs,
filter
search,
and
that
is
the
search
bar
that
we're
actually
using.
So
what
I
want
to
do
here
is
work
out.
What
is
this
component
called
because
I
don't
know
why
it's
not
loading
in
jdk,
but
I'm
not
going
to
try
to
work
it
out
while
I'm
presenting,
but
what
I
will
do
is
you
can
usually
take
like
data
qa
selector.
B
We
can
just
search
for
this
in
our
code
base
and
we'll
probably
find
it
I
looked
for
it
before,
so
I'm
probably
going
to
find
it
pretty
quickly
so
issuable
list
route.
That
is,
that
that's
the
component
so
filtered
search
bar.
This
is
the
component
that
is
using.
This
is
the
search
component.
That's
on
the
issues
page.
B
What
I
want
to
know
is
how
is
this
component
updating
the
url,
and
can
we
use
that
same
logic
in
our
code?
So
we
can
have
a
look
at
the
actual
component
itself.
B
So
what
I'm
doing
there
is
just
copying
the
name
and
then
opening
the
default.
The
file,
the
shortcuts,
don't
work,
because
these
are
all
shortened
but
yeah
anyway,
it's
pretty
straightforward,
so
you
can
see.
B
B
So
just
search
in
in
the
file
for
url
params
and
we're
going
to
find
a
pretty
good,
pretty
good
indication.
So
this
is
a
prop.
So
what's
actually
happening
is
issuable
list
route
is
being
rendered
by
something
else
that
is
handling
the
prop,
so
we
can
find
where
that
is
being
rendered.
B
We
rented
it
in
a
bunch
of
places.
Let's
just
look
at
one
and
then
again
we
want
to
find
the
url,
and
we
want
to
know
like
how
you,
how
are
you
doing
the
url?
B
So
we
get
a
bunch
of
utilities.
B
So
how
did
these
utilities
work
so
you
can
read
through
long
story
short.
It's
super
complex,
how
they
work
and
it's
not
really
appropriate
to
use
the
same
logic
in
our
search
bar,
because
this
is
really
specific
to
this
issues
page.
This
happens
a
lot
in
gitlab,
because
gitlab
is
very
large
and
some
parts
of
gitlab
are
pretty
old
and
those
parts
are
super
complex
and
not
super
duplicatable.
So
when
we
create
new
things,
we
want
to
make
sure
that
it
is
duplicatable.
B
The
next
thing
I
would
think
about
is
what
is
the
gitlab
ui
component
that
we're
using
to
render
search,
because
some
gitlab
ui
components
can
affect
the
url
search
parameters
like,
for
example,
if
you
look
at
tabs
you
can
you
can
access?
You
can
change
the
url
in
the
component
itself,
so
what
I
want
to
do
is
again
find
jobs,
filter
search,
and
this
is
rendering
get
lab
filtered
search.
So
this
is
git
lab
ui
component,
so
we
can
look
at
the
gitlab
ui
library
which
have
shortcutted
here
the
storyboard.
B
Okay,
so
filtered
search
component
and
what
we
want
to
know
is,
can
we
just
add
url
search
parameters
to
this,
but
url
is
not
on
the
documents
page.
It's
not
a
good
sign.
We
can't.
We
can't
do
that.
So
one
long
term
option
might
be
consider
adding
url
parameters
to
the
filtered
search
component.
So
then
it
would
work
across
all
gitlab
search
bars.
B
We
can
use
the
same
sort
of
logic,
so
you
can
consider
this
and
I
did
consider
this
and
then
I
realized
the
code
is
is,
is
actually
quite
different
in
each
place.
So
what
I
want
to
work
out
is
how
does
how
does
this
actually
work?
So
what
I
want
to
know
is
when
we
run
when
we
change
the
status,
what's
actually
happening
here,
so
we
can
have
a
look
at
the
jobs,
filtered
search.
B
B
So,
okay,
so
we're
not
actually
changing
the
filters
in
this
component,
but
it's
parent
so
again
we're
going
to
copy
the
name
and
try
to
find
out
like
are
there?
Is
there
just
one
parent
of
this
or
is
there
a
few
which
one
are
we
actually
talking
about?
B
So
we
have
so
we
have
jobs
table
app
and
we
have
these
two,
which
are
both
have
spec
after
it.
So
spec
means
the
tests.
So
these
are
the
tests
to
make
sure
that
this
works.
So
what
we
actually
want
is
this
view
component
that
renders
it
and
what
we
should
expect
here
is
for
it
to
render
jobs,
filter
search,
which
does,
and
what
we
want
to
know
is
what
is
it
doing
when
we
omit
jobs
filter
by
search?
B
B
So
we
can
read
through
and
understand
this,
but
what
I
actually
want
to
know
is
like
what
is
the
data
structure
of
filters
and
how
easily
can
we
put
it
into
the
search,
the
url
parameters,
because,
depending
on
its
complexity,
it
might
have
a
different
setup,
so
we
can
have
a
look
just
adding
a
debugger
and
then
refresh
and
we'll
add
a
status
and
we'll
see
what
it
actually
says.
Oh
no,
why
did
I
refresh
please.
B
Okay,
I
don't
know
what
happened,
but,
let's
just
hope,
just
tenuously
yeah,
okay
cool,
so
we
have
filters
we
can
read.
I
don't
know
if
this
is
big
enough
for
you
guys
to
read,
so
we
have
id
token
one.
I'm
not
sure
what
this
is
doing.
B
The
type
is
status,
the
value
is
cancelled
and
is
equal
to.
So
what
are
we
actually
doing?
With
this
information,
we
can
read
in
our
code
a
little
bit
easier,
so
we
are
checking
the
type.
So
if
there's
no
type
we're
giving
a
warning
okay,
fair
enough-
and
if
that,
if
the
type
is
status,
what
we're
doing
is
we're
adding
statuses
so
we're
adding
to
the
apollo
query
the
parameters
of
the
parameter
statuses
and
we're
just
giving
it
the
filter
value
data.
B
B
So
how
does
this
work?
We
have
our
apollo
query
here
and
what
we're
doing
is
we're
so
we're
adding
the
variable
in
here.
B
This
is
a
little
bit
confusing
and
again
it
took
me
a
little
while
to
quite
understand,
what's
happening,
but
I
I
played
around
with
it
a
little
bit
here
and
I
realized
so
there's
a
couple
of
clues.
So
this
is
a
really
confusing
piece
of
code
if
you're
not
really
familiar
to
the
git
lab
code
base.
Even
if
you
are
it's
quite
confusing,
so
what
it's
doing
is
it's
creating
an
event
hub
event.
B
So
what
happens?
What
is
an
event
hub?
It's
what
you
need
to
do
if
you're
running
five
view
applications
on
one
page
and
you
want
them
to
talk
to
each
other,
because
it's
not
usual
that
we
have
multiple
view
apps
on
one
page,
we
have
this
sort
of
custom
solution.
That
says
like
okay,
here
is
an
events
hub.
It
has
five
children,
the
children
are
the
applications,
the
five
different
applications.
B
B
We
want
to
run
job
act,
handle
job
action,
so
this
is
super
confusing
and
again
took
me
a
while
to
work
out,
but
I'm
going
to
give
you
the
the
pre-workout,
the
the
fast
route
of
working
it
out.
So
I
don't
know
what
this
is.
So
I'm
going
to
look
for
it
in
the
code
base
and
try
to
find
out
where
it
is
so
here
you
can
see.
B
So
this
is
where
we
are
action
cell.
This
is
emitting
the
the
event
and
then
this
is
very
similar.
This
is
listening
for
the
event
and
then
this
is
the
test.
So
what
we
want
to
know
is
like,
when
are
you
emitting
this
this
event
right?
So
what
it's
actually
doing
is.
B
I'll
spare
you
the
detail,
what
it's
doing
is
it's
listening
for
this
event,
when
you
click
finished
and
what
it
does
is
when
you
click
finished
it,
it
adds
some
statuses
to
it
in
the
scope,
so
we
can
test
it
by
just
adding
some
debuggers
and
work
out
when
these
have
been
fired.
B
This
is
literally
what
I
did
so
we're
going
to
listen
for
it.
So
when
we
change
tabs,
we
get
fetch
jobs
by
status
and
we
have
the
scope,
as
an
array
of
success,
failed
cancelled.
So
what
this
means
is
so
this.
B
Okay,
so
that
is
how
that
is
working,
let's
get
rid
of
those
debuggers
and
th.
This
is
what
this
is.
It
doesn't
matter
we'll
we'll
rush
through.
We
don't
have
none
of
time,
so
what
I
I
want
to
do
is
work
out.
So
what
I
want
to
do
is
for
starters,
when
I
get
a
filter,
I
want
to
add
it
to
the
url
search
parameters
so,
and
I
want
to
think
about
the
data.
How
should
this
be
structured?
B
So
actually
the
only
information
we
consider
in
the
search
bar
is
the
status
you
can
see
that
by,
if
you,
oh,
this
is
just
dying
all
over
the
place.
I
don't
know
why,
if
you
do
a
search
for
james
you'll,
see
an
error
coming
up
saying
raw
text
is
not
supported.
Please
use
the
search
tokens,
so
we
don't
actually
have
to
support
the
raw
text.
All
we
need
to
support
is
the
status,
so
this
would
look
something
like
oops.
B
So
what
we
ideally
want
to
do
is
have
something
like
this.
This
is
what
I
did
before.
Statuses
is
passed
so
when
we
add
a
status
in
the
search
bar
like
this
fast,
we
want
that
detail
to
be
passed
to
the
url
parameter.
So
we
do
this
fairly
straightforwardly.
B
That
says
when
you
have
filtered
job
by
search
while
we're
doing
these
things.
Actually,
what
we
want
to
do
is
is
in
this,
so
we
want
to
adjust
the
url
parameter
here,
because
this
is
a
failure
warning
and
if
this
doesn't
happen,
nothing
happens.
So
what
we
want
to
do
here
is
update
the
search
parameters,
so
we
can
say.
B
We
can
do
this
by
working
out
the
current
url
search
parameters,
so
search
params
are
equal
to
and
then
I
can't
ever
remember
how
to
do
it.
Url
search
params.
B
So
this
is
how
it
looks
so
we
have
we're
going
to
have
search
params
equals
new
search,
params.
B
Like
this,
so
I
want
to
do
this
in
the
same
way
that
get
lab.
Usually
does
it-
and
I
don't
know
what
that
is,
so
I'm
going
to
search
for
url
search
params
in
our
code
base
and
look
for
a
similar
solution,
because
there's
no
way
we
haven't
already
used
url
search
parameters,
so
I
want
to
use
the
same
structure.
B
So
this
is
how
we've
we've
done
it
in
template.
Selector
blob
bundle,
these
look
pretty
similar,
so
we're
going
to
do
the
same
thing
so
so
the
url
search
parameters
is
equal
to
window.location.search,
so
window.location.search.
B
B
B
So
now
we
can
read
the
url
search
parameters
in
our
code
and
what
we
want
to
do
is
so
because
this
might
be
an
array
we
want
to
get
them
and
then
we
want
to
add
to
them
so
search
params
dot.
So
if
we
add
to
the
search
params,
I
don't
know
how
to
do
that
so
set.
B
B
Not
the
same
so
we
can
get
and
then
we
can
add
to
it.
I
also
don't
know
how
this
works
with
an
array
and
we're
really
running
out
of
time.
So,
but
I'm
sure
you
can
work
that
bit
out
so
here
we
want
to
add
the
search
parameters
and
then
the
next
important
thing
we
want
to
do,
which
I
will
live
code
is
how
do
we
read
the
parameters
so
in
our
apollo
query,
which
is
somewhere
on
this
page
variables?
B
So
now
we
can
get
the
statuses
and
we
can
pass
them
to
the
the
apollo
query
variables.
So
with
this
now
we
should
be
able
to
read
the
url,
so
we
can
test
this
because
we
sort
of
manually
set
statuses
to
pass.
C
You're,
let's
in
your
code,
you
start
you
don't
finish
your
last
code
before.
A
C
Before
that,
before
that
step,
you
did
something
to
set
you.
Let's,
you.
B
A
Lot
of
time
I
mean
normally
it's
like
45
to
50
minutes,
but
we
can
go
like
up
to
the
hour
like
until
7
30..
It's
up
to
us.
B
So
I'm
still
gonna
finish
this
part
first,
because
what
I
want
to
do
is
be
able
to
read
the
url,
so
we
need
two
things.
We
need
to
be
able
to
write
the
url.
We
need
to
be
able
to
read
the
url
and
another
important
point
is
I'm
only
storing
the
state
of
the
search
bar
in
the
url,
it's
important
to
just
have
the
one
source
of
truth:
we're
not
moving
it
to
the
state
and
then
reading
from
the
state
we're
just
reading
directly
from
the
search
bar.
B
B
B
So
we
got
passed,
but
it
is
expecting.
One
of
these
so
pass
is
not
actually
valid.
Let's
try
success
and
we
should
only
have
success,
but
we
still
don't.
B
B
B
B
We
can't
just
change
it
because
it's
going
to
be
an
array
and
we're
looking
at
each
item
in
the
array
now,
so
I
didn't
get
this
file
when
I
was
practicing
so
now
this
is
actual
live
code
and
and
if
you
can
can
jump
in
with
some
ideas,
please.
B
So
we
can
say
set
so
we
can
say
search
for
ram
dot
set.
So
that's
fine.
We
can
do
that
and
we
will
do
that.
So
the
way
this
works
is
then
we
have
our
filters,
but
what
I
want
to
know
is
how
do
we?
B
How
do
we
make
filters,
the
existing
filters
and
the
new
filters,
and
it
should
be
whatever
filter
filters?
Are
this
is
our
our
list
right?
Does
that
make
sense?
So
we
can
just
say,
like
filters
is
equal
to.
B
B
B
So
one
thing
we
can
do
here
is:
you
can
actually
only
search
by
one
filter,
so
you
can't
actually
add
another.
It
doesn't
let
you
so
we
can.
We
could
assu.
We
could
remove
this
rewrite
this
code
to
say
instead
of
for
each,
but
here
we
have
the
reason
why,
eventually
there
will
be
more
tokens
available
and
this
code
is
written
to
scale
for
these
tokens.
B
So
we
need
to
consider
how
this
will
affect
the
future.
There
is
some
argument
to
say
like
let's
write
for
now
and
not
for
later,
because
this
was
done
four
months
ago,
because
when
we
have
new
information
we
might
have
a
different
way
of
thinking
about
it,
so
you
could
really
rewrite
this
entirely
and
then
say
in
your
merge
requests.
B
I
don't
like
this.
How
this
is
done,
like
don't
write
code
for
the
future
write
code
for
now
and
then
in
the
future,
then
write
it.
You
can
argue
that
if
you
want
like
the
the
good
thing
to
remember,
is
you
don't
need
this
code
to
be
perfect
or
even
great?
B
You
need
to
make
sure
it's
working,
because
when
you
push
the
code
in
your
merge
request,
you'll
have
at
least
two
reviewers,
I
think
for
community.
You
get
like
a
nice
person
to
to
coach
you
with
it.
So
that's
helpful,
but
even
for
me,
like
I,
I
find
myself
like.
Oh,
I
don't
want
to
push
yet
because
it's
not
perfect,
but
I
need
to
actually
push
and
then
push
my
code.
I
mean
finish.
B
My
merge
request,
stake
my
case
and
then
I'll
get
the
pushback
from
the
code
reviewer
and
then
once
they
have
approved,
then
I
will
get
additional
pushback
from
the
maintainer
before
it's
actually
merged
and
we
can
continue
the
conversation
there.
B
So
there
is
an
argument
to
say
that,
but
we
can
give
this
a
little
bit
more
thought.
A
C
Sorry
can
I
contribute
please,
okay,
james.
I
think
I
think
this
just
enough
use
the
append
method.
No,
because
we
are
inside
the
for
each.
We
are
in
a
filter
specific.
So
if
filters
is
an
a
that
is
treated
as
an
a
in
the
line
138.
C
So
now
we
are
in
the
element
of
this
array.
So
if
we
have
a
status,
so
we
are
treating
these
status,
so
I
think
we
need
to
test
just
call
the
search
parents
append
so
to
to
treat
these
tattoos.
C
C
B
C
B
B
But
then
we'll
have
to
wait,
let's
just
try
and
see
if
it's
magically
working
it
is.
B
C
B
Success-
okay,
so
should
have
we
might
need
to.
We
then
need
to
set
it
back
to
the
url.
B
That
is
my
mistake,
so
I
can't
exactly
remember
how
we
do
this,
because
what
we
want
to
do
is
update
the
url,
but
we
don't
want
to
refresh
the
page
how
to
do
this.
This.
B
That's
that's
just
google
yeah
go
ahead.
A
B
C
C
B
Work
search
rams-
this
is
this-
is
this
is
not
right.
Okay,
let's
try
here.
B
A
A
A
C
B
So
for
the
moment,
because
we
only
have
one,
we
could
just
change
it
to
set
and
set
the
one
and
then
when
we
eventually
make
this
scalable,
the
whole
function
is
going
to
have
to
be
rewritten
anyway,
because
at
the
moment
it
just
looks
for
one
status.
You
can't
have
more
than
one
so,
instead
of
append,
which
you
should
do,
which
is
correct.
We
can
actually
just
do
set
because
we're
gonna
overwrite
the
previous
detail,
because
there
is
only
one
possible
status
in
the
search
bar.
C
B
Because
it's
yeah
this
is
written
funny
and
it
does
at
least
there's
notes
to
say
why
it's
written
like
this,
because
eventually
we'll
have
more
than
one
filter.
But
currently
we
only
have
one
filter,
so
we
can
write
as
if
we
only
have
one
filter
and
then
next
time
we'll
we'll
fix
it
really
come
on.
A
File;
okay,
that
basically
has
most
of
the
things
we
are
trying
to
do
already
implemented.
B
But
for
now
I
just
I
just
want
something
that
works.
Yeah.
A
Point
thanks
for
the
assist
it's
just
a
friendly
reminder
that
if
you
open
an
mr
until
the
end
of
july
and
it's
gonna
be
merged
anytime
during
august,
except
on
the
website,
slash
handbook,
you're,
gonna
get
and
backpack.
B
Let's
try
a
couple
times:
let's
see,
what's
wrong
with
my
gdk:
okay
go
so
one
problem
here
is
it's
not
yes,
we're
not
filling
the
search
bar
and
also,
I
noticed
if
we
have
failed.
If
we
we
update
it,
this
works,
but
if
we
clear
it
that
doesn't
update
the
url
either
so
yeah
whoever's
gonna,
do
this
there's
a
couple
of
extra
little
things
for
you
to
do
so
that
you
earn
your.
B
Backpack
but
yeah,
that's
that's
how
I
do
it.
B
I've
had
enough
struggling,
I
mean
yeah
if
there's
extra
time
yeah.
I
better
answer
any
questions.
You
have
yeah.
C
I
have
one
question
you
started
show
us
you
get
the
the
branch
name
from
the
the
issue
this
process.
This
initial
process
cannot
be
applied
for
back
end
on
another
another
another
team
or
just
for
front-end
team-
that
we
do
this.
This
way.
B
C
A
There's
also
another
problem
for
us
contributors,
because
we
can't
actually
create
branches
on
the
main
only
made
project,
because
we
only
create
branches
on
our
forks.
B
C
For
my
part,
I
have
a
last
question
for
today
how
I
didn't
see
that,
but
I
need
to
to
just
add
more,
but
how
could
the
team
manage,
because
we
are
here
working
together,
but
let
let's
think
if
marco
and
and
me
want
to
work
the
same
issue,
how
we
we
we
both
create
the
marriage
request.
How
can
I
work
together?
How
can
I
control
this
to
not?
How
could
I
say
I
spend
the
work
work?
C
B
I
can
give
you
my
personal
opinion,
okay
yeah,
so
I
I
think,
because
you
said
you're
you
teach
students
right
is
that
right.
So
I
I
guess
what
you're
asking
is.
Can
I
have
a
couple
of
students
work
on
the
same
topic?
Yeah
together?
That's
it
yeah.
So
this
is
possible.
They
can
have.
You
know
they
can
work
off
the
same,
get
branch
they
could
add
commits,
but
it
is
so
messy.
B
Even
when
you
have
professionals
working
on
the
same
branch,
it
is
just
so
bad,
so
uncomfortable
and
so
awful,
but
just
run
into
so
you
run
into
the
biggest
problem
is
like
get
merged
conflicts
which,
unless
you
really
know
get.
You
can't
fix
this
this.
You
can't
teach
students
this
like
give
them
two
years
in
their
first
engineering
job
and
then
they'll
be
able
to
deal
with
merge
complex.
B
In
my
opinion,
that's
how
long
it
took
me
and
I
tried
real
hard.
So
what
I
think
is
a
far
better
way
of
doing
it
and
how
we
generally
do
it
at
gitlab
is
split
the
task
into
smaller
issues
and
have
one
person
work
on
one
issue.
B
We
do
pair
program
gramming
every
friday
afternoon
or
friday
afternoon
afternoon,
european
time
anyway,
and
so
this
is
really
useful
and
it's
it's
a
good
way
to
learn.
But
I
really
think
that
giving
students
one
task
with
multiple
branches
is
just
all
kinds
of
bad
ideas.
B
Because
it
also
means
like
when
you're
working
on
the
same
branch,
you
can
only
change
just
such
a
tiny
amount,
like
often
at
gitlab
you'll,
see
some
poorly
worded
variable
or
function
that
you
want
to
rewrite.
And
if
you
do
that
it
affects
so
many
other
places.
It
should
actually
be
done
in
a
separate,
merge
request.
A
B
A
Yeah,
so
I
have
a
question
so
I
just
today
signed
up
for
the
gitlab
self-made
premium
so
from
where
do
I
get
that
license
file
to
activate
premium
features
in
local
jdk.
A
Did
you
send
me
a
message?
I
think?
Yes,
you
send
me
a
message:
yeah
yeah,
I
reply
to
your
message.
You
can
try
for
for
the
free
trial
and
when
you're
done
with
the
free
trial
in
a
development
guide
in
the
contributing
guide.
Sorry
there
is
in
the
get
help
section.
There
is
a
link
where
you
can
request
for
development
purposes
for
communication
purposes
and
license
okay
in
the
documentation.
A
I
saw
that
there
we
have
to
set
some
path
to
the
license
file,
but
I
did
not
receive
any
license
file
yet,
but
have
you
have
you
open
that
issue?
I
don't
know
okay,
so
I
still
have
like
30
days
so
free
trial
yeah,
so
in
the
contributing
guide
in
the
contributing
guide
that
I
placed
here
on
zoom.
If
you
go
on
the
get
help
section,
there
is
a
link
from
where
you
can
request
the
license.
A
A
I
don't
have
any
other
questions.
I
will
like
take
the
opportunity
to
thank
you
all
for
joining
james
for
walking
us
through
how
to
your
your
thought
process
actually
and
everyone
for
participating.
A
It
was
really
nice
one
of
my
favorite
office
articles
so
far
so
yeah.
If
you
need
any
help
in
general,
let
me
say
help
section
in
the
contributing
guide.
That's
gonna
get
you
to
all
our
communication
mecca
and
platforms
in
the
agenda
here
in
the
document
of
this
meeting.
There
are
also
a
lot
of
very
nice
resources
like
videos,
a
playlist
with
youtube
videos
on
how
to
get
started
and
also
a
link
to
our
community
run
discord
platform
and
yeah
just
wanna.
Thank
you
I'll!
Stop.
Talking
now.