Slapr

Add Pull Requests status emojis to Slack posts.

On pull_request_review or pull_request events Slapr will update your slack posts with suitable emojis.

Slack posts should contain the PR URL.

Examples:

• Blabla Need Review for 👀 DataDog/integrations-core#5746
• Blabla Need Review for rev DataDog/integrations-core#5746

Slack API Token with following permissions

• channels:history
• groups:history - Needed if your review channel is private
• channels:read (required when using review-map)
• reactions:read
• reactions:write

By default, slapr posts emoji reactions to a single Slack channel (SLACK_CHANNEL_ID). With the review-map input, you can route reactions to different Slack channels based on which GitHub teams are requested for review.

Create a YAML file mapping GitHub teams to Slack channels:

# github_slack_map.yaml
'@datadog/agent-apm':
  review:
    name: 'apm-review'
    id: 'C01234ABCDE'          # preferred: name + id (no API call needed)
  notification:                 # ignored by slapr (used by other tools)
    name: 'apm-notifications'
    id: 'C09876FGHIJ'
'@datadog/agent-build':
  review:
    name: 'agent-build'         # id omitted: resolved via Slack API at startup
'@datadog/agent-ci': 'DEFAULT_SLACK_CHANNEL'  # falls back to SLACK_CHANNEL_ID

• Each team entry has a review subfield.
• Preferred format: provide both name (for readability) and id (avoids Slack API rate limits) under review.
• When id is omitted, the channel name is resolved via the Slack API at startup (requires channels:read scope).
• Only public channels are supported. Private channels cannot be resolved by name and are not supported.
• Use DEFAULT_SLACK_CHANNEL to route a team to the default SLACK_CHANNEL_ID.

On review events, slapr checks the reviewer's team membership (requires read:org scope on the GitHub token) and posts to the matching channel. On merge/close events, it uses the GitHub Timeline API to find all teams that were ever requested and posts to each of their channels.

When review-map is not set, behavior is identical to before (single channel).

Note: Team membership checks require the read:org scope. The default GITHUB_TOKEN does not have this — you need a PAT or GitHub App token.

name: Slack emoji PR updates
on:
  pull_request_review:
    types: [submitted]
  pull_request:
    types: [closed]

jobs:
  run_slapr:
    runs-on: ubuntu-latest
    steps:
    - uses: DataDog/slapr@master
      with:
        github-token: "${{ secrets.GITHUB_TOKEN }}"
        slack-api-token: "${{ secrets.SLACK_BOT_USER_OAUTH_ACCESS_TOKEN }}"
        slack-channel-id: CNY5XCHAA
        bot-user-id: UTMS06TPX
        review-map: .github/review-map.yaml  # optional
        number-of-approvals-required: 2
        emoji-partially-approved: next_track_button # :next_track_button:
        emoji-approved: ship # :ship:

emoji-partially-approved is opt-in. When it is not configured, approvals below the required count do not add a separate status emoji, preserving the existing behavior.

If you get the following error during Slapr run:

slack.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'account_inactive'}

Your SLACK_BOT_USER_OAUTH_ACCESS_TOKEN OAuth Token might not be valid anymore. If that's the case you should replace it with the one in https://api.slack.com/apps/{your_app_id}/oauth.