reviewGOOSE:Discord

The Discord integration for reviewGOOSE — know instantly when you're blocking a PR.

reviewGOOSE:Discord tracks GitHub pull requests and notifies reviewers when it's their turn. Works alongside reviewGOOSE:Desktop for a complete PR tracking experience.

Features

• Creates Discord threads for new PRs (forum channels) or posts in text channels
• Smart notifications: Delays DMs if user already notified in channel
• Channel auto-discovery: repos automatically map to same-named channels
• Self-service user linking: Link your GitHub account with /goose github-user command
• Smart user matching: Automatically matches by username, display name, or server nickname
• Configurable notification settings via YAML
• Activity-based reports when you come online
• Reliable delivery with deduplication

Quick Start

Prerequisites

• GitHub organization admin access
• Discord server admin access
• Discord Developer Mode enabled (Settings → Advanced → Developer Mode)

1. Install the GitHub App

Install the reviewGOOSE GitHub App on your organization.

2. Get Your Discord Server ID

Enable Developer Mode (if not already enabled):

1. Open Discord Settings (gear icon)
2. Go to Advanced (under App Settings)
3. Enable "Developer Mode"

Get Server ID: Right-click your server name → Copy Server ID

3. Create Configuration Repository

Create a repository named .codeGROOVE in your GitHub organization.

4. Add Configuration File

Create .codeGROOVE/discord.yaml:

global:
  guild_id: YOUR_DISCORD_SERVER_ID

# Optional: Add explicit user mappings if GitHub/Discord usernames differ
# users:
#   github-username: discord-user-id

5. Add the Bot to Your Server

Add reviewGOOSE to Discord

Channel Access:

• Public channels: Bot automatically has access after installation
• Private channels: Manually add the bot via channel settings:
  1. Right-click channel → Edit Channel → Permissions
  2. Click "+" → Select reviewGOOSE bot
  3. Enable "View Channel" permission

Done! The bot will post PR notifications to channels matching your repository names (e.g., api repo → #api channel).

Configuration

Full configuration options for .codeGROOVE/discord.yaml:

global:
  guild_id: 1234567890123456789
  reminder_dm_delay: 65  # Minutes to wait before sending DM (default: 65, 0 = disabled)

users:
  alice: 111111111111111111    # GitHub username → Discord user ID
  bob: discord-bob-username    # GitHub username → Discord username
  # Unmapped users: bot attempts username match in guild

channels:
  # Route all repos to one channel
  pull-requests:
    repos:
      - "*"

  # Route specific repos with custom DM delay
  backend:
    repos:
      - api
      - db
    reminder_dm_delay: 30

  # Disable notifications for a repo
  noisy-repo:
    mute: true

How It Works

Channel Routing

• Default: repos auto-map to same-named channels (api repo → #api channel)
• Override: Add repo to a channel's repos: list to route elsewhere
• Wildcard: Use repos: ["*"] to route all repos to one channel
• Mute: Set mute: true on a channel to disable notifications

Channel Types

• Forum channels: Each PR gets its own thread (recommended)
• Text channels: PR updates appear as regular messages

User Mapping

The bot maps GitHub → Discord users using a 4-tier lookup system:

1. Explicit Config Mapping (Highest Priority)

Checks the users: section in discord.yaml. Values can be:

• Discord numeric ID: "111111111111111111"
• Discord username: Bot will look it up in the guild

2. Self-Service Linking

Users can link their own accounts with /goose github-user <username>. Mappings are stored persistently and take priority over automatic discovery.

Example:

/goose github-user octocat

3. Automatic Username Match

Searches the Discord guild for the GitHub username using progressive matching. At each tier, checks:

• Discord Username (e.g., @johndoe)
• Discord Display Name (the name shown in the member list)
• Discord Server Nickname (the custom name set for this server)

Matching tiers:

• Tier 1: Exact match (checks Username, Display Name, then Nickname)
• Tier 2: Case-insensitive match (e.g., JohnDoe matches johndoe)
• Tier 3: Prefix match (e.g., john matches johnsmith) - only if unambiguous (exactly one match)

4. Fallback

If no match is found, mentions GitHub username as plain text (e.g., octocat instead of @octocat)

---

When to add explicit mappings: Only needed if automatic matching fails or usernames are too different

How to get Discord User IDs: With Developer Mode enabled, right-click any username → Copy User ID

Pro tip: Set your Discord server nickname to match your GitHub username for automatic matching!

Slash Commands

• /goose status - Show bot connection status and statistics
• /goose dash - Get your personal PR report and dashboard links
• /goose github-user <username> - Link your Discord account to a GitHub username
• /goose users - Show all GitHub ↔ Discord user mappings
• /goose channels - Show repository to channel mappings
• /goose help - Show help information

Notification Behavior

• Channel mentions: DMs delayed by reminder_dm_delay (default: 65 min)
• No channel access: Immediate DM to user
• Activity reports: Sent when you come online if you have pending PRs and 20+ hours since last report
• Anti-spam: Rate limiting prevents notification floods

Troubleshooting

Bot doesn't respond to commands

• Verify bot has correct permissions
• Try removing and re-adding the bot

No notifications for my org

• Verify GitHub App is installed on your org
• Check .codeGROOVE/discord.yaml exists in .codeGROOVE repo
• Verify guild_id matches your Discord server ID

Messages not appearing in channels

• Check channel name matches repo name or is configured in yaml
• For private channels: verify bot has been added to the channel (Edit Channel → Permissions → Add bot → Enable "View Channel")
• Verify bot has "Send Messages" permission in channel settings
• For forum channels: verify bot has "Create Public Threads" permission

DMs not working

• User must share a server with the bot
• User must have DMs enabled from server members
• Check reminder_dm_delay isn't 0 (disabled)

Self-Hosting

See DEPLOYMENT.md for instructions on deploying your own instance.