Skip to content

Ensure we don't post the Hackathon message twice

Rémy Coutable requested to merge fix-hackathon-processor into master

What does this MR do and why?

Since we recently introduced unique_comment for the HackathonLabel processor (in !1400 (merged)), we could end up posting the Hackathon message twice since the original message didn't include the "unique comment identifier".

For instance, gitlab-org/cluster-integration/auto-deploy-image!269 (comment 968617457) duplicates gitlab-org/cluster-integration/auto-deploy-image!269 (comment 939852341).

This adds the condition that the Hackathon label isn't already set.

After some time, we should be able to remove the condition (but it doesn't really hurt to keep it).

Expected impact & dry-runs

No double Hackathon notes.

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
Edited by Rémy Coutable

Merge request reports