Skip to content

Simplify community-related processors' conditions

Rémy Coutable requested to merge 1037-follow-up-from-allow-assigning-reviewers-as-community-contributor into master

What does this MR do and why?

  • Add an Event#by_team_member? method

  • Streamline the way we check for community contributions

    The first detection still checks against members of the
`gitlab-org`/`gitlab-com` groups to set the `Community contribution`
label, then all the other community-related processors simply check for
the `Community contribution` label.

This also moves two (currently unused) processors to the `community/`
namespace.

Expected impact & dry-runs

The behavior of the processors shouldn't change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs.

Action items

  • (If applicable) Add documentation to the handbook pages for Triage Operations =>
  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group =>
    • Relevant Slack channels =>
    • Engineering week-in-review

Closes #1037 (closed).

Edited by Rémy Coutable

Merge request reports