►
Description
GitLab label hygiene
Automate the updates and management of Issue and Merge Request Labels with the GitLab Triage Bot. This makes your teams more efficient and efficient and effective as you manage work with issues and merge requests.
Get in touch with Sales: http://bit.ly/2IygR7z
A
Hi
John
Jeremiah
here
gitlab
I,
wanted
to
share
a
little
little
insight
learning
we
had
recently
about
how
we
can
make
our
labels
and
our
projects
more
effective,
cleaner
and
more
efficient.
One
of
the
challenges
we
faced
was:
we
were
doing
project
management
and
managing
our
work
using
a
couple
of
different
processes
in
strategic
marketing
at
get
lab.
A
One
of
the
things
we
would
do
is
we
had
a
process
where
we
would
establish
a
workflow
for
new
requests
and
when
new
requests
would
come
in,
we
would
put
the
right
labels
on
them
and
they
would
have
scope
labels
that
would
change
over
time
and
then
periodically.
We
would
expect
them
to
close
well.
This
led
to
some
problems.
A
One
of
the
problems
was
that
the
labels
weren't
always
consistent,
and
we
had
cases
where
labels
were
getting
out
of
sync
and
it
was
hard
to
manage
it
was
confusing
and
and
likely
we
also
were
managing
and
looking
at
edit
lab
insights.
So
we
could
look
at
issues
and
see
whether
or
not
they
were
either
internal
or
external
work.
And
again,
this
was
dependent
upon
issues
having
the
right
labels
on
them
and,
regretfully
sometimes
they
didn't
so
we
had
two
choices
right
we
could.
A
We
could
try
to
teach
everyone
to
use
the
right
labels
or
we
could
look
for
a
better
way.
Well,
the
good
news
and
I
want
to
share
with
all
of
you
is
that
there
is
a
better
way.
There
is
a
bot
that
allows
you
to
manage
and
maintain
and
update
labels
and
keep
your
labels
clean.
The
git
lab
triage
project
is
a
independent
project
that
that's
been
built
to
create
a
bot
that
will
run
in
your
pipeline
and
will
allow
you
to
apply
and
enforce
policies
or
rules
about
how
you
managed
labels
super-awesome.
A
It's
super
cool.
Here's
an
example
of
how
they
described
it
and
I'll
I'll.
Give
you
a
link
to
this
at
the
end
of
this
quick
video,
but
you
can
go
there
and
look
at
this
and
set
it
up
in
your
project
and
help
to
make
your
labels
more
effective
and
cleaner,
as
you
go,
I've
also
documented
a
process
of
how
to
do
this.
A
The
pipeline,
the
CIA
amo
file,
defines
the
pipeline.
We
now
have
three
jobs.
We
have
one
that
runs
the
triage
as
a
dry
run.
The
dry
run
is
a
test.
It's
a
way
to
test
your
rules
without
making
any
changes,
because
when
you
do
make
changes
all
of
your
issues
that
apply
will
get
updated.
So
this
is
a
dry
run.
It
will
do
a
test
run.
Oh,
we
can
show
you
that,
and
it
hat
takes
an
API
token,
so
you
have
to
set
that
up
again
the
instructions
we
wrote.
Show
you
how
to
do
that.
A
Then.
There's
a
policy
run
job
where
we
can
manually
run
a
job
and
say
look
I
want
to
apply
all
the
rules
and
in
the
last
last
one
is
a
scheduled
job,
a
job
that
we
run
on
schedule
B.
We
run
it
every
day
and
that
keeps
our
issues
and
labels
all
squeaky,
keen,
clean
and
ready
to
go.
So
so,
first
off,
that's
the
first
file,
that's
added!
A
The
second
file
we
have
is
the
policies,
it's
called
triage
policies,
yeah
mo
it's
it's
right
there
in
the
root
directory
of
the
project,
and
this
file
describes
the
rules,
and
so
each
rule
consists
of
a
name
conditions
and
then
actions,
and
this
these
first
two
them
I,
don't
have
any
actions,
I'm
just
doing
tests
to
see
how
it
runs.
So
the
name
of
it
of
the
rule
is
that
the
condition
find
all
the
open
issues.
A
The
second
one
find
issues
that
don't
have
any
labels
and
the
last
one
the
next
one
I'll
talk
about
is
one
we're
gonna
do
something,
and
so
this
one
finds
any
issues
that
have
this
label
on
it:
the
the
analyst
relations
label,
and
then
it
adds
a
summary
label,
a
scope
label
that
we
call
external
and
you
can
see
here
the
conditions
it
has
this
label.
It's
missing
this
label,
it's
open,
and
so
therefore,
do
these
things
add
a
label
and
put
a
comment
too.
A
Now
the
fact
that
you're
put
in
a
comment
means
you
can
do
all
sorts
of
other
things
with
quick
actions
you
could
assign
it
to
an
epic.
You
could
assign
it
to
an
individual.
You
could
even
change
issues
from
being.
You
know
from
being
public
to
confidentially
anything.
You
can
do
with
quick
actions.
A
So
when
this,
when
this
runs
when
we're
done-
and
it
runs
every
day
so
if
I
go
to
our
pipelines,
you
can
see
where
it
ran
this
morning
and
I
open
up
our
pipelines,
who
can
see
where
this
was
the
morning
time
it
ran,
and
in
fact
the
pipeline
was
triggered
a
little
while
ago,
when
Ryan
actually
updated
a
updated
one
of
our
templates
again,
the
stages
don't
run
because
they're
both
manuals,
so
they
don't
run,
but
the
pipeline
was
triggered.
If
we
look
at
the
one
where
it
ran
this
morning,
we
opened
it
up.
A
We'll
take
a
look
at
the
job.
You
can
see
the
details
of
how
it
ran
and
you'll
look
at
this
when
you're,
defining
your
policies
and
you're
defining
how
it
goes,
and
so
this
is
the
bottom
of
it
there's
300
lines
in
this
thing
we
can
just
scroll
up
and
look
at
this.
You
can
see
here
it
processed
a
rule
of
looking
for
anything
that
was
declined
and
then
we
clothed
in
it
we
closed
it.
Is
that
what
that
rule
would
do?
We
are
it's
missing
it
scoped
label.
A
We
can
go
further
up
and
here's
one
that
closes
one,
here's
one
that
finds
ones
with
the
web
label
and
adds
a
scope
label.
So
we
have
a
whole
host
of
these.
You
see
the
outputs
here's
one
that
found
was
called
a
one
that
was
missing
a
scoped
label,
so
we
added
a
scope
label
here.
So
that's
that's
the
way
it
flows
and
that's
the
way
it
works,
and
it's
gonna
help.
A
You
make
your
labels
your
projects
and
issues
more
clean,
more
effective
and
easier
for
you
to
manage
things
over
time
and
you'll
spend
the
less
time
looking
for
issues
that
don't
fit.
That
somehow
are
our
out
of
sync.
So,
in
the
spirit
of
efficiency,
spirit,
of
moving
faster,
this
triage
bot
and
label
hygiene
is
a
huge
time
savings.
So
if
you
want
to
look
at
the
file
light
at
the
page,
I
wrote
about
how
to
set
it
up.
That's
this
first
link:
bitly
slash
label
hygiene.
A
If
you
want
to
go
to
the
triage
bot
itself,
you
can
go
to
the
one
at
the
bottom.
Bitly,
slash
triage
bot
and
with
that
good
luck,
happy
triaging,
and
if
you
have
any
feedback
or
questions,
we
believe
everyone
can
contribute.
So
if
you
see
something
that
doesn't
look
right
on
the
page,
we
wrote
please
update
a
merge,
request
and
submit
an
EMR
and
we'll
be
glad
to
take
those
and
update
with
that
thanks
very
much
in
having
a
great
rest
of
the
day.