►
From YouTube: Blog Bug Fixes
Description
GitLab's Managing Editor, Rebecca Rodd, walks through her bug fix contributions to the GitLab Blog.
A
A
Okay,
so
I
think
you
should
be
looking
at
a
merger
quest.
That's
been
merged.
This
was
to
address
a
bug
that
was
creating
this
issue.
Where
I'll
show
you
what
was
happening.
This
is
our
hero
post
on
the
blog
home
page.
We
set
this
by
using
the
featured
field
in
the
front
matter.
What
was
happening
is
every
time
a
new
featured
post
was
coming,
it
was
being
placed
in
this
hero
spot
and
then
it
would
just
disappear
from
the
page.
A
My
expectation
would
be
that
it
would
just
move
down
into
recent
posts,
but
the
way
the
logic
was
set
up
was
it
was
written
to
exclude
any
featured
posts
from
this
second
line,
so
feature
posts
go
up
here.
Non-Featured
posts
go
down
here
and
if
a
post
is
featured
and
then
gets
pre
or
like
superseded
by
a
more
recent
featured
post,
it
was
just
going
straight
to
our
archives
and
was
no
longer
discoverable.
A
This
is
obviously
not
ideal
behavior,
because
it
then
stops
something
that
was
an
important
post
because
it
was
featured
from
being
found
on
the
blog
home
page.
So
I
had
some
help,
but
we
basically
rewrote
the
logic
to
just
exclude
the
hero
article
or
the
current
hero
article
from
that
second
row,
and
then
anything
else
is
fair
game
for
being
included
there.
So
that's
one
example:
I'm
gonna
find
the
next
one.
A
Oh,
this
was
happening
in
a
sense
on
our
category
pages
as
well,
so
quite
a
few
people
pointed
out
that
they
couldn't
find
our
main
the
monthly
release
post
from
the
previous
months
on
the
releases
category
page.
So
this
was
a
slightly
different
bug,
but
we
managed
to
rewrite
this
so
that,
oh
sorry,
I'm
rambling
here,
but
I've
just
realized
what
was
this
is
an
off
by
one
era
which,
if
you
are
familiar
with
coding
at
all,
this
is
apparently
a
classic
thing.
A
But
basically,
by
having
this
set
to
include
articles
2
to
24,
it
was
skipping
the
article
that
was
at
position
1,
because
in
ruby
a
list
of
articles
starts
from
zero,
not
one
so
erica.
I
don't
know
if
this
is
it.
This
is
all
news
to
me,
so
you
could
just
smile
and
nod
if
you're
unfamiliar,
but
apparently
this
was
my
first
off
by
one
area
that
I
helped
to
debug.
A
So
pretty
exciting
there
jump
in
if
you
have
any
questions
also,
but
I'm
gonna
open
the
next
one
which
wasn't
a
bug,
but
this
is
something
that
I
changed.
So
we
have
the
blog
archive,
which
is
this
list
of
articles
here
when
we
split
the
release
posts
into
like
a
separate
blog
in
releases
and
they
weren't
being
included
in
this
archive.
A
A
B
A
You
can
you
can
set
it
in
the
front
matter
which
we
do
encourage
if
you
know
of
a
blog
post
that
someone
else
would
be
interested
in
reading
if
they're
reading
this
current
post.
But
as
you
can
see
what's
happening,
we
are
on
this
blog
post,
the
basics
of
gitlab,
ci
updated,
and
it's
showing
you
the
same
post
that
you're
currently
reading.
A
We
thought
we'd
fix
this
a
while
back,
but
there
was
a
regression
where,
like
we
changed
something
else,
and
then
this
bug
crept
back
in
so
I've
added
some
logic
here
to
reject
the
current
article
so
that
you
don't
see
that
again,
but
that
one
still
needs
to
be
reviewed
and
merged
by
one
of
our
website
team
and
then
the
last
one
that
I
will
show
you,
which
is
kind
of
a
bug.
I
guess
so
when
we
move
to.
A
Making
the
hero
image
in
a
blog
post
be
optional.
We
now
have
this
kind
of
layout
where,
before
the
title
used
to
be
overlaid
on
the
image
now
it's
it's
kind
of
separated,
just
underneath
the
title
and
description,
but
these
little
icons
were
white
because
they
used
to
be
overlaid
on
the
image
and
so
to
make
them
visible.
They
were
just
white,
so
I
noticed
that
for
some
reason
they
were
invisible
unless
you
hovered
over
them,
because
we
have
this
setting.
A
That
makes
it
change
color
if
you
hover
over
it,
and
then
I
figured
out
that
they
were
set
to
white
because
they
used
to
be
overlaid
on
an
image.
I've
now
changed
them
to
this
gray,
which
we
use
in
some
other
elements
of
our
our
design.
So
that
was
just
a
simple
change
here:
to
change
it
from
white
to
gray.
A
B
This
is
really
really
cool
to
see
like
as
the
person
who
is
in
charge
of
the
editorial
side,
like
also
being
able
to
dig
into
some
of
the
engineering
behind
it
and
actually
contribute,
and
before
we
started
recording.
I
think
you
said
some
really
interesting
stuff.
I
just
felt
like
how
empowering
this
felt
and
I'm
just
curious.
B
A
A
This
has
helped
me
work
better
with
we
have
a
contractor
doing
some
stuff,
improving
the
blog,
and
I
had
asked
her
to
create
some
blog
subcategories,
which
apparently
middleman
doesn't
support,
but
by
digging
into
how
the
website
takes
the
code
that
we
give
it
and
interpret
it.
I
realize
that
we
don't
need
categories.
A
I
think,
if
it's
possible
to
use
tags
to
achieve
the
same
effect,
I'm
open
to
it,
but
I
didn't
know-
and
we've
kind
of
circled
back
to
the
solution
of
using
tags
instead
of
categories.
So
essentially,
we
will
have
a
link
to
a
tag
instead
of
a
link
to
a
category,
but
the
layout
will
be
the
exact
same
as
a
category.
So
that's
something
that
she's
working
on
and
I
don't
think
we
would
have
got
to
the
solution.
A
A
A
Yeah,
you
got
it
and
I
I
should
sort
some
thanks
out
to
the
patient
website.
Team
brandon
and
lauren
have
been
reviewing
some
of
these
merger
quests
and
I
I
know
sometimes
it
can
be
uncomfortable
if
someone
comes
in
and
starts
like
rooting
around
in
in
your
like
behind
the
scenes,
but
I
hope
what
I'm
trying
to
do
here
is
solve
more
of
my
own
problems
and
yeah
take
a
more
active
approach
to
contributing,
instead
of
just
always
giving
them
bug
reports
and
asking
them
to
deal
with
it.