GitTrack/Documentation
Back

GitTrack Documentation

Everything you need to connect GitHub with Discord. Get real-time notifications, manage repositories, and keep your team in sync with your development workflow.

What is GitTrack?

GitTrack is a Discord bot that bridges your GitHub repositories with your Discord server. Get real-time notifications for pushes, pull requests, issues, releases, and workflow runs directly in your channels. With branch pattern matching and flexible event routing, GitTrack keeps every team member up to date.

Installation

Get up and running in minutes.

Add GitTrack to Discord

Quick Setup

1

Run /setup from your project channel

Connect the GitHub repository and choose the default channel. The bot replies with the webhook payload URL and secret.

/setup repository:https://github.com/your-org/your-repo channel:#notifications
2

Configure the GitHub webhook

In GitHub go to Settings → Webhooks → Add webhook. Set Content type to application/json and choose "Send me everything".

3

Link branches or wildcard patterns

Route production, release, or feature prefixes into their own channels.

/link url:https://github.com/your-org/your-repo branch:release/* channel:#deploys
4

Route events & fine-tune filters

Move issues, releases, and stars into dedicated channels and toggle which actions alert your team.

/set-event-channel repository:<repo> event:issues channel:#triage

Tip: Run /status anytime to review active repositories, limits, branch links, and event routes.

Commands Reference

Complete list of all available GitTrack slash commands.

Setup Commands

Configure GitTrack and manage repository connections.

/setup repository:<url> [channel]

Register a GitHub repository, pick a default notification channel, and generate the webhook secret + payload URL.

Parameters

repositoryrequiredFull GitHub repository URL (https://github.com/org/repo)
channeloptionalDefault channel for repository-wide notifications
/set-default-channel repository:<repo> channel:<channel>

Update where general (non-branch) notifications for a repository are delivered.

Parameters

repositoryrequiredSelect from repositories configured with /setup
channelrequiredNew default channel for the repository
/link url:<repo> branch:<pattern> channel:<channel>

Route branch-specific activity (pushes, PRs, etc.) into a Discord channel. Supports exact branches and wildcard patterns.

Parameters

urlrequiredRepository to link (autocomplete supported)
branchrequiredBranch name or wildcard pattern (main, release/*, *)
channelrequiredChannel that should receive these branch events
/unlink url:<repo> branch:<pattern> [channel]

Remove a branch or pattern link. Optionally scope the removal to a specific channel.

Parameters

urlrequiredRepository to update
branchrequiredBranch or wildcard pattern to unlink
channeloptionalOnly remove the mapping from this channel
/remove-repo url:<repo>

Delete a repository from the server along with every branch link and event override.

Parameters

urlrequiredRepository URL you want to remove entirely
/reset confirm:true

Danger zone. Clears all GitTrack data for the current server after explicit confirmation.

Parameters

confirmrequiredMust be set to true to run the reset

Event Routing & Filters

Control where non-branch GitHub events are delivered and which actions trigger alerts.

/set-event-channel repository:<repo> event:<type> channel:<channel>

Send non-branch GitHub events (issues, releases, stars, etc.) to a dedicated channel.

Parameters

repositoryrequiredRepository whose events you want to route
eventrequiredPick from: issues, pull_request, release, star, fork, create, delete, milestone
channelrequiredDestination channel for the selected event
/remove-event-channel repository:<repo> event:<type>

Remove an event override so it falls back to the repository default channel.

Parameters

repositoryrequiredRepository to modify
eventrequiredEvent route to remove
/edit-event repository:<repo> event:<type>

Interactively toggle which actions inside an event should alert (e.g., only opened/closed issues).

Parameters

repositoryrequiredRepository to configure
eventrequiredEvent whose action filters you want to edit

Info Commands

Available to all server members.

/status

View every tracked repository, branch pattern, event route, and the current server limits.

/help

Show the in-Discord help center with command usage and tips.

/ping

Simple health check to confirm the bot is online.

Branch Pattern Matching

GitTrack supports wildcard patterns so you can monitor groups of branches without configuring each one individually.

*

All branches

Tracks every branch in the repository.

main

Exact name

Tracks only the specified branch.

release/*

Prefix wildcard

Tracks all branches starting with the prefix.

Pattern Rules

  • Wildcards are limited to a standalone * or a single trailing * after a prefix (e.g. release/*).
  • Branch names are case-sensitive and must match exactly what GitHub sends in the webhook.
  • Allowed characters: letters, numbers, hyphens, underscores, dots, and forward slashes.
  • Multiple patterns can overlap — if two patterns match the same push, GitTrack delivers both notifications.

Permissions & Limits

Discord Permissions

Setup and configuration commands require the Manage Webhooks permission in your Discord server. Info commands (/status, /help, /ping) are available to all members.

Server Limits

Each Discord server can register up to 10 repositories by default. Branch notification channels are unlimited. Run /status to see current usage. Remove unused entries with /remove-repo or /unlink before adding new ones.

Need more capacity? [email protected]

Troubleshooting

Bot not receiving webhooks

  • —Verify the webhook URL is correct and publicly accessible.
  • —Check the webhook secret matches the one from /setup.
  • —Review GitHub webhook delivery logs for failed attempts.

Notifications not appearing in Discord

  • —Check the bot has Send Messages permission in the target channel.
  • —Verify the channel is properly linked using /status.
  • —Ensure branch patterns match the pushed branch name exactly.

Branch autocomplete not working

  • —Public repos: autocomplete works automatically.
  • —Private repos: requires manual typing.
  • —Check the repository URL is correct and accessible.

Still stuck?

  • Run /status to review your full configuration.
  • Run /help for in-Discord command usage.
  • Join our support Discord for direct assistance.
  • Check GitHub's webhook delivery logs for detailed error responses.