# Actions in Slack Source: https://docs.gitnotifier.com/actions-in-slack Use GitNotifier Slack actions to reply to pull request comments, add GitHub reactions, and merge ready PRs without leaving Slack. GitNotifier notifications include interactive Slack actions. ## Reply to PR Comments Use the **Reply** button on a comment notification to open a modal and post a GitHub reply. ## Add Reactions Use emoji buttons (`๐Ÿ‘`, `๐ŸŽ‰`, `๐Ÿ‘€`, `โค๏ธ`) to add GitHub reactions from Slack. ## React with a native Slack emoji You can also react to a comment notification with a native Slack emoji (the same way you react to any Slack message), and GitNotifier mirrors it onto the underlying GitHub comment. Remove the emoji to remove the GitHub reaction. Supported reactions: | Slack emoji | GitHub reaction | | -------------------------- | --------------- | | ๐Ÿ‘ `:+1:` / `:thumbsup:` | `+1` | | ๐Ÿ‘Ž `:-1:` / `:thumbsdown:` | `-1` | | ๐Ÿ˜„ `:smile:` | `laugh` | | ๐ŸŽ‰ `:tada:` | `hooray` | | ๐Ÿ˜• `:confused:` | `confused` | | โค๏ธ `:heart:` | `heart` | | ๐Ÿš€ `:rocket:` | `rocket` | | ๐Ÿ‘€ `:eyes:` | `eyes` | Any other emoji is ignored. GitNotifier confirms the action with a short reply in the message thread. Reactions only sync to GitHub on comment notifications. If you react to another kind of notification (for example a CI status update), GitNotifier replies with a short hint instead, and points you to ๐Ÿ”‡ `:mute:` when the message references a pull request. ## Mute a PR with a reaction React to a PR notification with ๐Ÿ”‡ (`:mute:` or `:no_bell:`) to mute that pull request. Remove the reaction to unmute and restore notifications. This is the same mute rule you can manage with `/gitnotifier mute` or in Slack App Home. See [Mute Rules](./mute-rules). ## Merge Ready PRs When a PR is ready, GitNotifier can show a **Merge** button in Slack. ## Notes * You must have a linked GitHub account in GitNotifier. * Organization SAML/SSO policies can require reauthorization before actions succeed. * Reactions run against your own GitHub account, so each person's reaction or mute applies only to them. * If GitNotifier replies that it is missing Slack permissions, ask a workspace admin to re-install the app with the latest scopes. See [Slack Permissions](./slack-permissions#update-permissions-when-the-slack-app-scopes-change). # Changelog Source: https://docs.gitnotifier.com/changelog Read the GitNotifier changelog for the latest product updates, bug fixes, security improvements, and new Slack and GitHub workflow features. * ๐Ÿ‘€ When you submit a review (approve or request changes) on a PR in your latest **PR Review Digest**, GitNotifier now strikes through that line in place and marks it reviewed, no new ping. Only your own line is struck, so teammates who still owe a review keep theirs. * ๐Ÿคซ When you have no assigned or review-requested open PRs, GitNotifier now skips the scheduled **PR Review Digest** instead of DMing you an empty one. * โœ… When a PR in your latest **PR Review Digest** is merged or closed, GitNotifier now strikes through that line in place and marks it merged or closed, no new ping. * โœ๏ธ When someone edits a GitHub comment, GitNotifier now quietly updates the original Slack message in place instead of doing nothing or sending a duplicate. No new ping. - ๐Ÿ”” Prefer a fresh message on every edit? Turn on **Comment update notifications** in Slack App Home. That path still respects Do Not Disturb and your mute settings. * ๐Ÿ’ก GitNotifier now sends you one short product tip in Slack every Tuesday at noon. Each tip surfaces a feature that helps you stay on top of code reviews. - Toggle weekly tips on or off anytime from the **Weekly tips** button in Slack App Home. Tips are on by default. * โฐ Scheduled reminders can now fire at up to 4 times per day on the same cadence, e.g. weekdays at 9 am and 2 pm. Previously you could pick only a single time. - ๐Ÿ•˜ Pick your times from one multi-select in the Slack **Configure reminders** modal, in 30-minute increments. Your existing single time is carried over automatically, so nothing changes unless you add more. - ๐Ÿ  App Home and the first-digest intro now list every reminder time (e.g. "9 am and 2 pm"). * โœจ React to a comment notification with a native Slack emoji and GitNotifier mirrors it onto the GitHub comment. Remove the emoji to remove the GitHub reaction. All 8 GitHub reactions are supported: ๐Ÿ‘, ๐Ÿ‘Ž, ๐Ÿ˜„, ๐ŸŽ‰, ๐Ÿ˜•, โค๏ธ, ๐Ÿš€, ๐Ÿ‘€. - ๐Ÿ”‡ React to a PR notification with ๐Ÿ”‡ (`:mute:` or `:no_bell:`) to mute the pull request, and remove the reaction to unmute. It uses the same PR-level mute rule as `/gitnotifier mute`. - Each reaction runs against your own GitHub account and mute settings, so it only affects you. GitNotifier confirms every action with a short reply in the message thread. - ๐Ÿ” If your Slack install is missing a permission the reaction needs, GitNotifier now replies in-thread asking a workspace admin to re-install with the latest permissions, instead of doing nothing. - โš ๏ธ New Slack scope: `im:history` (read the single DM you reacted to). Workspace admins should re-install GitNotifier to pick up reaction support. * ๐Ÿค– Better bot comment notifications in Slack. - Fixed a bug where bot comments were silently dropped even when you had "Mute all comments from bots" turned off. If you opted in to bot comments, you now actually receive them (including accounts like Copilot that don't use a `[bot]` suffix). - Comment edits from assistants like `claude[bot]`, Copilot, and Cursor (which update a single comment with fresh analysis) now notify you, instead of only the original comment. - Cursor Bugbot review comments now include **Fix in Cursor** and **Fix in Web** buttons right in the notification. - Bot senders are clearly prefixed with ๐Ÿค–, previews show up to 3 lines as a blockquote, and GitHub Markdown is cleanly converted to Slack formatting (noisy bot metadata stripped out). - โœจ New feature preview: **Truncate GitHub comments** toggle in Slack App Home. Enabled by default (comments are trimmed to a short preview). Turn it off to receive the full comment body from anyone, human or bot, with GitHub Markdown converted to native Slack formatting: code blocks, lists, and bold/italic text render directly in Slack so you can read and act without clicking through to GitHub. - ๐Ÿ”— Smoother Slack setup when GitHub isn't connected yet. - Using a Slack action (mute rules, scheduled reminders, invites) before connecting GitHub now shows a one-click **Connect GitHub** prompt instead of failing silently. * ๐Ÿ’ณ Improved billing dashboard with a usage bar and tiered plan cards so you can see your plan limits at a glance. - ๐Ÿข Dashboard now surfaces pending GitHub org installation approval requests, so you can track whether your GitHub App install is still awaiting admin approval. - ๐Ÿ“ง Requesters now receive an email once their GitHub org installation request is approved. - โšก Slack emoji reactions (e.g. marking a PR as done) now acknowledge instantly, eliminating the perceived lag. - โšก Slack modal submissions (e.g. invite flows) now acknowledge immediately for a snappier experience. * โœจ New command: `/gitnotifier muted` to list all currently muted PRs with direct links. - ๐Ÿ”• Added **Reviewer Comment Quiet Mode** in Slack App Home mute settings. - Mutes reviewer-scoped PR comment notifications. - Keeps the initial review-request DM. - Direct `@mentions` still notify. - ๐Ÿ” Added a Slack permissions update flow in the dashboard (`Slack is connected` card menu โ†’ **Update Permissions**) with docs and screenshot guidance. * โœจ Added `/gitnotifier connect` so users can launch the GitHub connect flow directly from Slack with a one-click **Connect GitHub** button. - โœจ New command: `/gitnotifier emoji me` and `/gitnotifier emoji @user` to generate a custom emoji-ready profile image download link directly in Slack. - โœจ Improved `/gitnotifier mute` so it can resolve open PRs by title search text (for example ticket IDs or short phrases) when no explicit PR reference is provided. - When multiple open PRs match, GitNotifier now shows up to 3 candidates and asks you to pick one explicitly or refine the search. - ๐Ÿ”• Added team-level mute rules in Slack App Home (`Mute settings`) so users can mute review requests for specific GitHub teams (for example `@chapter-nodejs`). - When a PR is review-requested to a muted team, GitNotifier now auto-mutes that PR for the user. - Direct GitHub `@mentions` still notify the user. * ๐Ÿ“š Public documentation at [https://docs.gitnotifier.com/](https://docs.gitnotifier.com/) is live ๐Ÿš€! - Rework the changelog page & move it under our new documentation - Enable RSS feed for the changelog - Document new features and improvements such as the new slash commands - ๐Ÿ”ง Improved the slack notification on pull request updates by showing who reviewed the PR. If it's the junior in the team, you still might want to have a look at the PR... ;) - โœจ Added `/gitnotifier mute` and `/gitnotifier unmute` slash commands for PR-level mute control directly from Slack threads. GitNotifier slash command in Slack - ๐Ÿงช Added a new **Feature preview** section in Slack App Home so users can opt in to experiments. - First sneak-peak: **New Slack notification design** for PR review-request notifications. New Slack notification design preview * ๐Ÿ›ก๏ธ Hardened OAuth and callback flows with stricter state handling, improved sanitization, and safer error rendering. - ๐Ÿ›ก๏ธ Added stronger security posture across web and API with improved response headers and reduced internal error leakage. * โœจ Launched dashboard analytics with panels for CI failures, active repositories, comment activity, and top failing repositories. - ๐Ÿ”ง Improved light theme readability in onboarding and connected-user modals. * ๐Ÿš€ Public beta launched! ๐ŸŽ‰ with: - scheduled reminders - Slack App Home controls - improved notification actions in Slack. - ๐Ÿ“š Added public security disclosure page and onboarding/support docs updates. * ๐Ÿš€ Initial alpha release with core GitHub + Slack integration and foundational PR notifications. # Quick Start Source: https://docs.gitnotifier.com/getting-started Set up GitNotifier in minutes by connecting GitHub and Slack, then onboard teammates to start receiving high-signal pull request notifications. ![GitNotifier overview](https://www.gitnotifier.com/images/og-image.png) ## Step 1 - Create your GitNotifier dashboard account Start at [www.gitnotifier.com/dashboard](https://www.gitnotifier.com/dashboard), create your account, and then follow the next steps below! **Only the GitHub/Slack admin needs to create a GitNotifier account** and complete the installation through the UI. Once installed, any team members can join from slack with one click. ## Step 2 - Install the GitHub App Install GitNotifier on your GitHub account or organization from the dashboard. If you are not a GitHub organization admin, GitHub will let you request the installation instead. A GitHub organization admin can then approve that request directly in GitHub. GitHub documents this flow here: [Requesting a GitHub App from your organization owner](https://docs.github.com/en/apps/using-github-apps/requesting-a-github-app-from-your-organization-owner). When you submit the request, GitHub notifies your organization owner so they can review and approve the installation. ## Step 3 - Connect your Slack Workspace In the dashboard, connect Slack and authorize the workspace. And you are good to go! ๐ŸŽ‰ ## How to get your teammates onboard? Normal team members can join with 3 current ways: 1. Get invited from Slack App Home (any existing GitNotifier Slack user can invite teammates). 2. Open the GitNotifier app in Slack (`@gitnotifier` App Home) and follow the connect flow. 3. Run `/gitnotifier connect` in Slack. ## If Connection Requires Reauthorization If Slack shows **Reconnect required**, click **Reconnect GitHub** in App Home and complete OAuth again. # Overview Source: https://docs.gitnotifier.com/index Learn how GitNotifier delivers GitHub pull request notifications in Slack DMs, with setup guides, features, and workflows to review and merge faster. # Hello, stranger from the internet! ๐Ÿ‘‹ Welcome! GitNotifier is a tool to send GitHub pull request notifications to your Slack DMs and lets you act from Slack. If you are interested in reducing the number of open PRs, merging faster and improving your productivity & velocity, you are in the right place. From Slack you can always run `/gitnotifier help` to get a list of available commands! ## Where do you want to go next? * New here? Follow [Getting Started](./getting-started) ๐Ÿš€ * Configure [Scheduled Reminders](./scheduled-reminders). * Set [Mute Rules](./mute-rules). * Learn [Slash Commands](./slash-commands). * Follow product updates in the [Changelog](./changelog) ๐Ÿ‘€ * And don't hesitate to reach out to us on [Discord](https://discord.com/invite/5f68xxjpFx) if you have any questions or feedback! ๐Ÿ’ฌ # Mute Rules Source: https://docs.gitnotifier.com/mute-rules Reduce GitNotifier noise by muting bots, users, GitHub teams, or specific pull requests, with supported formats and guidance for managing muted items in Slack. Use **Mute rules** in Slack App Home to control notification noise. ## Available Rule Types * **Mute all comments from bots**: enabled/disabled * **Reviewer Comment Quiet Mode**: mute PR comment notifications when you are in reviewer scope (direct reviewer or requested via team), except direct `@mentions` * **Mute specific users/bots**: comma-separated GitHub logins * **Mute review-requested teams**: comma-separated GitHub team slugs * **Mute specific pull requests**: comma-separated PR references ## Reviewer Comment Quiet Mode When enabled, GitNotifier keeps your initial review-request DM, but mutes follow-up PR comment notifications where you are in reviewer scope. * Applies to PR comments and review-thread comments. * Direct `@mentions` still notify you. * Non-reviewer notification paths are unaffected. ## Muting Team Review Requests If a PR is review-requested to a muted team (for example `@chapter-nodejs`), GitNotifier: * Skips the review-request DM for you. * Auto-mutes notifications for that PR for you. * Still notifies you when you are directly `@mentioned` in comments. If you are explicitly requested as a reviewer in addition to the team, notifications continue as usual. ## Mute a PR with a Slack reaction React to a PR notification with ๐Ÿ”‡ (`:mute:` or `:no_bell:`) to mute that pull request without leaving the message. Remove the reaction to unmute and restore notifications. This adds or removes the same PR-level mute rule as `/gitnotifier mute` and the **Mute specific pull requests** setting. See [Actions in Slack](./actions-in-slack#mute-a-pr-with-a-reaction). ## List all muted PRs You can see all muted PRs in the **Mute Settings** section of the Slack App Home (@gitnotifier page) ## Supported PR Reference Formats * `owner/repo#123` * `https://github.com/owner/repo/pull/123` ## Examples ```text theme={"theme":{"light":"github-light","dark":"github-dark"}} dependabot[bot], coderabbitai[bot], alice ``` ```text theme={"theme":{"light":"github-light","dark":"github-dark"}} @chapter-nodejs, @acme/frontend-platform ``` ```text theme={"theme":{"light":"github-light","dark":"github-dark"}} acme/api#42, https://github.com/acme/web/pull/128 ``` # Notifications Source: https://docs.gitnotifier.com/notifications See which GitHub pull request, review, comment, CI, and release events GitNotifier sends to Slack, including routing behavior and mention rules. GitNotifier focuses on high-signal pull request activity. Here are the events we react on and \_can \_forward. ## Pull Request Events * Review requested * Review request removed * Assignment / unassignment * Review submitted (including approved and changes requested) * PR opened * PR merged * PR closed without merge * New comments on PRs ## Review Comment Routing For GitHub `pull_request_review_comment` notifications, GitNotifier routes recipients based on whether a comment starts a thread or replies in a thread. * Top-level human comment: notify the PR audience (author, assignees, requested reviewers), excluding the sender. * Top-level bot comment: notify nobody. * Reply in a thread: notify the PR author, non-bot thread participants, and the replied human user (excluding the sender). * Reply to a bot message: skip the replied-user recipient, but still notify the PR author and non-bot thread participants. * `@mentions` on human comments/replies notify mapped users in our DB, even if they are not PR author/assignee/reviewer. * Top-level bot comments are strict no-notify, including mentions. If **Reviewer Comment Quiet Mode** is enabled for a user, GitNotifier mutes reviewer-scoped PR comment notifications for that user while still delivering direct `@mentions`. ## Team Review Request Mute Behavior When you mute a GitHub team slug in Slack App Home and a PR is review-requested to that team: * GitNotifier skips your review-request DM for that event. * GitNotifier auto-mutes that PR for your future notifications. * Direct `@mentions` to your GitHub username still notify you. * If you were also explicitly requested as an individual reviewer, notifications continue as usual. ### Examples * John posts a top-level review comment -> PR audience is notified. * Bob replies to John's thread comment -> John, PR author, and other thread participants are notified (deduped, excluding Bob). * John and Bob each post separate top-level comments -> PR audience is notified for both comments. * `coderabbit[bot]` posts a top-level comment -> nobody is notified. * John replies to `coderabbit[bot]` in thread -> PR author and other non-bot thread participants are notified. * `coderabbit[bot]` replies to John's thread comment -> John, PR author, and other non-bot thread participants are notified. ## CI Signals * Check suite failures * Workflow job failures * Main/default branch failure alerts after merge * Ready-to-merge signal when CI succeeds ## Release Discussion Mentions Mentions in GitHub release discussions can be sent to Slack. # Scheduled Reminders Source: https://docs.gitnotifier.com/scheduled-reminders Configure daily, weekday, or weekly GitNotifier reminders in Slack so you never miss assigned or review-requested open pull requests. ## Configure in App Home Open **Configure reminders** and set: * **Status**: Enabled or Disabled * **Cadence**: * `daily` * `weekdays` (Mon-Fri) * `weekly_monday` * **Reminder times**: pick up to 4 local times per day (in 30-minute increments) from the multi-select. They all share the same cadence, so you could receive the digest on weekdays at 9 am and 2 pm. * **Additional section**: optionally include your own open PRs awaiting external review Timezone is auto-synced from your Slack profile each time the modal opens. If you travel, update your Slack timezone and save reminders again. You can also use **Send test reminder now**. ## Behavior Notes * Reminders apply to your personal DM notifications. * When you have nothing to review, the reminder is skipped instead of sending an empty digest. Your first digest and **Send test reminder now** always arrive, so you can confirm reminders are working. * Multiple times per day are edited from the Slack modal. The web dashboard is still single-time, so saving reminders there keeps only your first time. Use Slack to manage more than one. * Draft PRs are excluded in current behavior. * When **Additional section** is enabled, the digest includes your own PRs that match GitHub `review:required`. * If one of those PRs is mergeable (`mergeable: true` and `mergeable_state: clean`), GitNotifier shows a **Merge** button. * PRs still awaiting review are listed without a merge button. # Security and Privacy Source: https://docs.gitnotifier.com/security-privacy Review GitNotifier security and privacy practices, including OAuth protections, webhook signature checks, token handling, and minimal data storage. ## Authentication and Integrations * GitHub and Slack integrations use OAuth flows. * Request signatures are validated for Slack and GitHub webhooks. * OAuth state and PKCE protections are used in the Slack-initiated GitHub flow. For detailed Slack OAuth scopes and rationale, see [Slack Permissions](./slack-permissions). ## Token Handling * Integration tokens are stored server-side. * Reconnect flows are supported when tokens expire or are revoked. ## Data Scope GitNotifier stores only data needed to deliver notifications and preferences (for example, account mapping and reminder/mute preferences). ## Team Access Model * Only the admin needs to complete initial app setup. * Team members connect later via invitation or Slack App Home flow. ## Platform and Infrastructure Security GitNotifier is built entirely on the Cloudflare platform and runs on serverless runtimes (Cloudflare Workers). This makes our workloads safer than traditional VMs or Docker containers, for several reasons: * **No servers to compromise.** There is no long-lived VM, host OS, or container image that we operate, patch, or harden. There is no SSH, no shell, and no persistent host an attacker could pivot into. * **Strong isolation.** Each request runs in a lightweight, memory-isolated V8 isolate rather than a shared VM or container. The attack surface is far smaller than a full operating system with its libraries and background daemons. * **Ephemeral and stateless.** Execution is short-lived and stateless, with no persistent local filesystem and no background processes. There is nothing for malware to install into or persist across requests. * **Automatically patched.** Cloudflare keeps the underlying runtime current across its global network, which removes an entire class of "unpatched host" and outdated base-image risks that VMs and containers carry. ## Dependency Security We keep our dependencies current automatically with Renovate. Renovate opens pull requests to pull in the latest releases and patch known CVEs promptly, so we do not sit on outdated, vulnerable packages. ## Supply Chain Protection We use [pnpm](https://pnpm.io/supply-chain-security) to reduce the risk of supply chain attacks. When an npm package is compromised, there is a window between when the malware is published and when it is detected and removed from the registry. pnpm gives us a buffer during that window through several mitigations: * **Blocked install scripts.** pnpm does not automatically run `postinstall` scripts for dependencies, which is the mechanism most compromised packages use to execute code on install. * **Release-age delay.** pnpm delays installing newly published versions until they have aged (the `minimumReleaseAge` setting), so a version that is later found to be malicious is most likely pulled from the registry before we ever install it. * **Committed lockfile.** Our lockfile is committed to the repository, so installs are reproducible and dependencies do not update unexpectedly. For the full list of pnpm supply chain mitigations, see [Mitigating supply chain attacks](https://pnpm.io/supply-chain-security). # Slack App Home Source: https://docs.gitnotifier.com/slack-app-home Manage GitNotifier from Slack App Home with quick controls for reminders, mute rules, teammate invites, feature previews, and account connection. GitNotifier App Home is your control center in Slack. From there you can do most of the actions you need with GitNotifier to tweak your notifications coming from Github: mute, scheduled reminders (daily summary), invite your teammates and more. Note that settings related to analytics, billing, github app & slack app settings are in the [gitnotifier dashboard](https://www.gitnotifier.com/dashboard). ## Quick Actions * **Invite teammates**: send invites from Slack. Your teammates will receive a message to start with GitNotifier. They just have to click one button and they are good to go. * [Configure reminders](/scheduled-reminders): set daily/weekly reminders * **Global settings**: toggle comment update notifications and weekly tips (one short product tip in Slack every Tuesday at noon). By default, when someone edits a GitHub comment, GitNotifier quietly updates the original Slack message in place, so you never get a duplicate notification for an edit. Turn comment update notifications on if you would rather receive a brand-new Slack message each time a comment is edited. * **Feature preview**: enable upcoming features before general release. * [**Mute rules**](/mute-rules): mute bots, logins, review-requested GitHub teams, or specific PRs. See your muted PRs (and unmute them if needed) * **Manage connection**: disconnect/reconnect GitHub account. * **Send feedback**: send us some feedbacks! Of course you can also join our discord! # Slack Permissions Source: https://docs.gitnotifier.com/slack-permissions Understand GitNotifier Slack app scopes, why each permission is required, and how workspace admins can approve permission updates safely. GitNotifier only requests **Bot Token Scopes**. We do **not** request or use Slack User Token Scopes. We follow the least privileges principle, we only ask scopes we need for GitNotifier to work. You can only review the current permissions on the slack app itself. If Slack says `/gitnotifier` is not a valid command, see [Troubleshooting](./troubleshooting#slack-says-gitnotifier-is-not-a-valid-command). Notice that we **do** **not** **read** **your slack messages.** ## Update permissions when the Slack app scopes change When GitNotifier ships a feature that needs new Slack scopes, your workspace admin must approve the updated permissions. From the [gitnotifier Dashboard](https://www.gitnotifier.com/dashboard): 1. Go to the **Slack is connected** card. 2. Click the **three-dot menu** in the top-right of the Slack card. 3. Click **Update Permissions**. 1. If you are a Slack admin, you can do the permissions update flow in 2 clicks. 2. If you are not a Slack admin, Slack lets you submit a permissions update request and notifies your workspace admins by email that they need to approve it. Update Slack permissions from the dashboard ## Requested Bot Token Scopes ### `chat:write` Send messages as `@GitNotifier`. Why we need it: * Send direct notifications for GitHub events (new comments, CI failures, PR ready to merge, and similar updates). ### `commands` Add slash commands and shortcuts. Why we need it: * Support Slack command actions like muting/unmuting PRs. * Support account connect/authorize flows from Slack without requiring App Home navigation. ### `emoji:read` View custom emoji in a workspace. Why we need it: * Support richer message presentation when teams use custom GitHub/PR-related emoji. ### `im:write` Start direct messages with people. Why we need it: * GitNotifier is primarily DM-based to avoid channel spam. ### `im:history` View message history in direct messages GitNotifier is part of. Why we need it: * When you react to a notification DM, GitNotifier reads that single message to find which GitHub comment or pull request the reaction applies to. We only look at the message you reacted to. ### `reactions:read` View emoji reactions and associated content where GitNotifier is present. Why we need it: * Read user reaction inputs when reactions are used as lightweight actions. ### `reactions:write` Add and edit emoji reactions. Why we need it: * Reflect action status with reactions (for example, adding a success/check reaction). ### `team:read` View workspace name, email domain, and icon. Why we need it: * Show workspace identity (name and icon) in GitNotifier UI for better workspace management UX. ### `users:read` View people in a workspace. Why we need it: * Support GitHub user to Slack user mapping for accurate notifications and mentions. It replaces the Github handle by the Slack handle in the PR notifications (it's convenient as Github usernames are often different from the Slack usernames). # Slash Commands Source: https://docs.gitnotifier.com/slash-commands Discover every GitNotifier slash command, with examples for muting or unmuting pull requests, searching PRs by title, and listing muted items. GitNotifier exposes one slash command: `/gitnotifier`. GitNotifier slash command in Slack ## Available Commands ### General #### `/gitnotifier help` Show command help. #### `/gitnotifier connect` Start the GitHub connect flow for your Slack user (same flow as App Home and invite links). If you are already connected, GitNotifier returns an ephemeral "already connected" message and does not start OAuth. ### PR digest #### `/gitnotifier pr` Show your assigned/review-requested open PR digest as an ephemeral Slack message (same PR scope as scheduled reminders, with a command-specific title). #### `/gitnotifier prs`, `/gitnotifier list`, `/gitnotifier ls`, `/gitnotifier digest` Aliases for `/gitnotifier pr`. ### Mute management #### `/gitnotifier mute` Mute PR notifications in the current PR thread. #### `/gitnotifier mute owner/repo#123` Mute a specific pull request. #### `/gitnotifier mute https://github.com/owner/repo/pull/123` Mute a specific pull request by full GitHub URL (fragments like `#discussion_r...` are supported). #### `/gitnotifier mute ` Mute a pull request by searching open PR titles in GitHub (for example: `/gitnotifier mute NT-6879`, `/gitnotifier mute nx upgrade`, `/gitnotifier mute fix issue with memory`). GitNotifier runs this scoped query with your GitHub user context: * `is:pr is:open archived:false in:title "" involves:@me` If you wrap search text in single/double quotes (including smart quotes), GitNotifier strips wrapping quotes before querying. * If exactly one open PR matches, GitNotifier mutes it. * If multiple open PRs match, GitNotifier shows up to 3 candidates and asks you to pick one with `owner/repo#123` or refine your search. * If no open PR matches, GitNotifier asks for a more specific search or an explicit PR reference. * Under the hood, GitNotifier uses GitHub Search API with `is:pr is:open archived:false in:title "" involves:@me`. #### `/gitnotifier unmute` Unmute PR notifications in the current PR thread. #### `/gitnotifier unmute owner/repo#123` Unmute a specific pull request. #### `/gitnotifier muted` Show all currently muted PRs for your account in Slack, with clickable PR links. ### Emoji #### `/gitnotifier emoji me` Build a custom emoji draft from your own Slack profile photo. GitNotifier replies with an ephemeral **128x128 preview** and a **download link** to the PNG. #### `/gitnotifier emoji @user` Build a custom emoji draft from a teammate profile photo (use a real Slack @mention). GitNotifier also shows quick upload steps: 1. Click the generated **Download PNG** button (or link). 2. Hover any message, click the reaction icon, then click **Add a custom emoji**. 3. Upload the image and save an emoji name. GitNotifier adds a reminder that it is better to ask the person first. ## Accepted PR Reference Formats * `owner/repo#123` * `https://github.com/owner/repo/pull/123` * `https://github.com/owner/repo/pull/123#discussion_r456` ## Quick Usage ```bash theme={"theme":{"light":"github-light","dark":"github-dark"}} /gitnotifier mute /gitnotifier unmute /gitnotifier muted /gitnotifier pr # aliases: prs, list, ls, digest /gitnotifier emoji me /gitnotifier emoji @francois /gitnotifier mute acme/api#42 /gitnotifier mute NT-6879 /gitnotifier mute fix issue with memory /gitnotifier mute https://github.com/contentful/optimization/pull/205 /gitnotifier mute https://github.com/ninetailed-inc/kubernetes-infra/pull/598#discussion_r3001364001 /gitnotifier unmute acme/api#42 ``` # Troubleshooting Source: https://docs.gitnotifier.com/troubleshooting Fix common GitNotifier setup and Slack command issues, including invalid slash commands, PR reference parsing, search mismatches, and permission updates. ## Command says missing thread context For `/gitnotifier mute` and `/gitnotifier unmute` without explicit PR ref, run command in a PR thread. Alternative: pass explicit reference like `owner/repo#123`. ## Slack says `/gitnotifier` is not a valid command If `/gitnotifier` is missing or Slack reports it as not valid, the Slack app likely needs to be updated with newer permissions. From time to time, new GitNotifier features require additional Slack permissions. Example: slash commands require the command permission/scope to be granted to the Slack app. Quick fix from the dashboard: 1. Open **Dashboard** โ†’ **Step 2: Slack is connected**. 2. Open the **three-dot menu** on the Slack card. 3. Click **Update Permissions**. 1. If you are a Slack admin, just follow the steps to update the permissions. 2. If you are not a Slack admin, submit the request in Slack. Workspace admins should receive an email to approve it. Update Slack permissions from the dashboard ## Command cannot parse PR reference Use one of: * `owner/repo#123` * `https://github.com/owner/repo/pull/123` * `https://github.com/owner/repo/pull/123#discussion_r456` For `/gitnotifier mute`, you can also use free text to search open PR titles (for example `NT-6879` or `fix issue with memory`). The title search is scoped to your own relevant PRs: * `is:pr is:open archived:false in:title "" involves:@me` If you include wrapping quotes around the search text (single, double, or smart quotes), GitNotifier strips them before running the query. ## Command search returns multiple PRs GitNotifier shows up to 3 matching open PRs. Pick one by running `/gitnotifier mute owner/repo#123`, or refine your search text. ## Command search returns no PR Try a more specific search text, or use an explicit PR reference format: * `owner/repo#123` * `https://github.com/owner/repo/pull/123` ## `/gitnotifier muted` shows no results If you see "You have no muted PRs right now.", no PR-level mute rules are currently stored for your connected GitHub account. You can create one with: * `/gitnotifier mute owner/repo#123` ## Slack says reconnect required Open GitNotifier App Home and click **Reconnect GitHub**. ## Slack actions fail with SSO/SAML message Your org requires GitHub SSO authorization. Re-authorize GitNotifier, then retry action. ## No GitHub connection found Open GitNotifier App Home in Slack and complete **Connect GitHub**. ## I did not get a review comment notification Check the comment type first: * Top-level bot review comments do not notify anyone ๐Ÿค–. * Review-thread replies notify the PR author, non-bot thread participants, and the replied human user (excluding sender, deduped). * Replies to bot comments skip the replied-user recipient, but can still notify PR author and non-bot thread participants. For `@mentions`: * Mentioned users are notified only if they are mapped in GitNotifier's DB. * Top-level bot comments still do not notify anyone, even with mentions. ## I'm not getting notifications for bot comments By default, GitNotifier mutes all bot comments to reduce noise. To receive them: 1. Open the Slack App Home (`@GitNotifier`). 2. Go to **mute settings**. 3. Disable **Mute all comments from bots**. Once enabled, you receive notifications for bot comments from tools like Copilot, Cursor, Dependabot, and any other accounts (including those without a `[bot]` suffix). Bot senders are prefixed with a robot emoji ๐Ÿค– so you can tell them apart from human comments at a glance. ## Notifications are truncated or cut off By default, GitNotifier trims GitHub comments to a short preview in Slack. To receive the full content: 1. Open the Slack App Home (`@GitNotifier`). 2. Go to **Feature preview**. 3. Turn off **Truncate GitHub comments**. Once disabled, comments from anyone (human or bot) are delivered in full, with GitHub Markdown converted to native Slack formatting: headings, code blocks, lists, bold and italic text all render cleanly, so you can read and act without clicking through to GitHub. You still can't find what you are looking for? Something is broken? please reach out to us on [Discord](https://discord.com/invite/5f68xxjpFx) or by [e-mail](mailto:support@gitnotifier.com) ๐Ÿ™