Skip to content

Post messages to Discord for MR ready and help reactive commands

What does this MR do and why?

This is one of the next steps mentioned in https://gitlab.com/gitlab-org/quality/contributor-success/team-task/-/issues/100#note_1184631438 and also help with gitlab-org/gitlab#385387.

With this MR, the reactive commands @gitlab-bot ready and @gitlab-bot help will send messages over to channels on Discord, if configured 🙂

This is the format of the message posted for the @gitlab-bot ready command:

A merge request from `<MR author username>` is ready to be reviewed:
- URL: <MR url>
- Title: <MR title>
- Project: <MR project path>
- Labels: <MR labels>
- Reviewers: <reviewers assigned by the command>

This is the format of the message posted for the @gitlab-bot help command:

`<MR author username>` is looking for help on a merge request:
- URL: <MR url>
- Title: <MR title>
- Project: <MR project path>
- Labels: <MR labels>

In order to be enabled:

  • @gitlab-bot ready commands the DISCORD_WEBHOOK_PATH_COMMUNITY_MR_REQUEST_REVIEW environment variable must be provided
  • @gitlab-bot help commands the DISCORD_WEBHOOK_PATH_COMMUNITY_MR_HELP environment variable must be provided

This subdivision has been made since the webhook URL also decides to which server channel the message will be posted to, and this way we can send messages to two different channels 🙂

Expected impact & 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
Edited by Marco Zille

Merge request reports