The rationale is that for ~Next, ~"Needs Review" and ~Doing, the
author is not actually the one who should respond.

This list was curated by hand and by parsing the mr ls output

This was lost when moving to the common code.

This is mostly a noop. The biggest difference is that we'll stop
pinging the entire team when a label is missing, which is a good
thing.

This is a little unfortunate: I'm not sure the bot will be as
effective without this mention. But the reality is that not everyone
in the team is responsible for triage, so it was actually creating
noise for the entire team.

People responsible for triage should probably watch the project in a
way that they will see those notices anyways.

We actually move the "unassigned" policy to a `.meta` directory
because it has team-specific things in there, but the other two are
generic enough that they can be reused everywhere.

The first two, in particular, I want to reuse in tpo/tpa.

this was being interpreted as a hash badly written by the yaml parser,
see https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage#list

We pick lavamind and kez because they're doing most of the web
work. We use the `random_reviewer` function because there's no
`random_assignee` but I think it should work anyways.

See: #9

Here we also mark old issues in ~Next and ~Doing as ~Stale: the
rationale is that assignees should give regular updates even if the
work takes longer than a week.

We don't send tickets from ~Next or ~Doing in the ~Icebox though,
that's too hard, and a real information loss...

We use this pattern here:

https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage#list

... not sure it actually works.

See: #9

We just change the "mention" in the unlabel warning.

This only affects tpo/web/team for now.

See: #9

add tor-tor-browser-build policy

See merge request !13

fix incorret subscribe command usage

See merge request !12

initial rules for application's team

See merge request !11

update some api requests for gitlab 15.x

See merge request !10

add a few methods to help interacting  with CI status

See merge request !9

include some methods to know when the bot last interacted with an mr
these can be used so the bot does not repeat itself

cohosh will only review snowflake mr

See merge request !8

don't assign busy people as reviewer

Closes #1

See merge request !7