Gitify can show notifications from several Git hosts, not only GitHub.com.

• GitHub.com — the public github.com service, including GitHub Enterprise Cloud organizations hosted there
• GitHub Enterprise Server (GHES) — a self-hosted GitHub instance
• GitHub Enterprise Cloud with data residency (GHDR) — GitHub Enterprise Cloud on [tenant].ghe.com
• Gitea — including self-hosted instances
• Forgejo — uses the same sign-in flow as Gitea
• Codeberg — powered by Forgejo
• Bitbucket Cloud — bitbucket.org
• GitLab Cloud and Self-Managed — GitLab.com and self-hosted GitLab

You can stay signed in to more than one account at the same time, including accounts on different forges.

Related: What authentication methods does Gitify support? · How do I add multiple accounts?

How you sign in depends on the forge. On GitHub.com, start with Login with GitHub. On other GitHub hostnames, use a personal access token (PAT) or a GitHub OAuth app. On Gitea, Forgejo, Codeberg, and GitLab, use a PAT. On Bitbucket Cloud, use an app password.

GitHub

GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server:

• Login with GitHub — The simplest option on GitHub.com. Gitify shows a code, opens github.com/login/device in your browser, and finishes sign-in for you. This method is for GitHub.com only.
• Personal access token (classic) — A classic token from your GitHub account settings. Works on GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server.
• GitHub OAuth app — A Client ID and Client Secret from an OAuth app you create. Works on GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server.

If you are unsure, use Login with GitHub on GitHub.com. On GitHub Enterprise Cloud or GitHub Enterprise Server, use a classic personal access token or a GitHub OAuth app.

Gitea, Forgejo, Codeberg

• Personal access token (PAT) — Create a token under Settings → Applications, then enter it in Gitify with your instance hostname (for example codeberg.org or your self-hosted URL).

Bitbucket Cloud

• App password — Create an app password under Personal settings → App passwords and enter it as your token in Gitify.

GitLab

GitLab Cloud and Self-Managed:

• Personal access token (PAT) — Create a token under User settings → Access tokens, then enter it in Gitify with your instance hostname.

Related: Which Git forges does Gitify support? · How do I configure GitHub OAuth app authentication? · What GitHub scopes does Gitify require?

You can sign in with a GitHub OAuth app on GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server by registering an app and pasting its client ID and secret into Gitify.

1. On GitHub.com, open GitHub → Settings → Developer settings → OAuth Apps. On GitHub Enterprise Cloud or GitHub Enterprise Server, open the same page on your GitHub hostname.
2. Click New OAuth App.
3. Set Authorization callback URL to gitify://oauth.
4. Fill in the other required fields.
5. Click Register application.
6. Click Generate a new client secret.
7. Enter the client ID and secret in Gitify.

Note: Create a separate OAuth app for each GitHub hostname. Enterprise Managed Users (EMU) and enterprise policies may block OAuth apps. For Gitea, Forgejo, Codeberg, GitLab, and Bitbucket Cloud, use a personal access token or app password instead.

Related: What authentication methods does Gitify support? · Does Gitify support GitHub Enterprise Cloud and GitHub Enterprise Server?

Yes. Gitify works with GitHub.com, GitHub Enterprise Cloud (including GitHub Enterprise Cloud with data residency (GHDR)), and GitHub Enterprise Server (GHES).

When you sign in with a personal access token (classic) or a GitHub OAuth app, Gitify shows a Hostname field. It defaults to github.com. Change it to match your instance:

• GitHub Enterprise Server (GHES): your self-hosted hostname, for example github.mycompany.com
• GitHub Enterprise Cloud with data residency (GHDR): your tenant hostname, for example myorg.ghe.com
• GitHub.com / GitHub Enterprise Cloud on github.com: leave the hostname as github.com

Note: Enterprise Managed Users (EMU) is an account model, not a separate forge. Your enterprise policy may limit which sign-in methods you can use.

Note: Login with GitHub only works on GitHub.com (github.com) and does not show a hostname field.

Related: What authentication methods does Gitify support? · How do I add multiple accounts? · Which Git forges does Gitify support?

Gitify needs specific GitHub permissions so it can read your notifications and profile. The required GitHub scopes depend on how you sign in.

This article covers GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server only.

Login with GitHub and GitHub OAuth app

Gitify requests the scopes for you during sign-in. You do not choose them yourself.

Classic personal access token (PAT)

When you create a classic PAT, select:

• notifications — to read GitHub notifications
• read:user — to read your GitHub user details (name, profile, avatar)
• repo — to enrich notification details for public and private repositories

Note: If you only need public repositories, you can use public_repo instead of repo.

Fine-grained PATs use repository and account permissions instead of these classic scopes. Confirm that your Gitify version and GitHub deployment support the permissions required by fine-grained PATs before using one.

On GitHub.com, create a classic token at GitHub → Settings → Developer settings → Personal access tokens. On GitHub Enterprise Cloud or GitHub Enterprise Server, open the same page on your GitHub hostname.

Related: What authentication methods does Gitify support? · Why aren’t my notifications showing?

If your GitHub organization uses SAML single sign-on (SSO), you must authorize your classic personal access token (PAT) for that organization. Until you do, Gitify will not show notifications from that organization’s repositories, even if the token has the right scopes.

1. On GitHub.com, open GitHub → Settings → Personal access tokens. On GitHub Enterprise Cloud or GitHub Enterprise Server, open the same page on your GitHub hostname.
2. Find the token you use with Gitify.
3. Click Configure SSO next to the token.
4. Click Authorize next to each SSO-enabled organization you want to allow.
5. Complete the SSO sign-in for each organization.

After that, Gitify can fetch notifications from those organizations. You may need to authorize again if your SSO session expires or your organization’s SSO setup changes.

Fine-grained PATs use different SSO and repository-permission controls.

For more detail, see GitHub’s documentation on authorizing a PAT for SSO.

Related: What GitHub scopes does Gitify require? · Why aren’t my notifications showing?

Gitify can stay signed in to more than one account at once. You can add several GitHub.com accounts, or mix accounts from different forges — for example GitHub.com with GitHub Enterprise Server, Gitea, or Bitbucket Cloud.

1. Open the Accounts screen from the Gitify sidebar.
2. Click Add new account and choose your forge and sign-in method.
3. Finish sign-in for the extra account.

All signed-in accounts appear on the Accounts screen. Click the star next to an account to make it the primary account — Gitify uses that account as the default where it needs one.

You can refresh or sign out of each account on its own.

Related: Which Git forges does Gitify support? · What authentication methods does Gitify support?

Gitify can start automatically when you log in to your computer.

1. Open Settings in Gitify.
2. Go to the System section.
3. Turn on Open at startup.

Note: This setting is available on macOS and Windows only. On Linux, use your desktop environment or init system to start Gitify at login.

Filters let you hide notifications you do not need so you can focus on the ones that matter.

Open Filters from the left-hand sidebar. By default, Gitify shows all notifications. You can filter by reason (for example Mentioned, Review Requested, or Assigned), repository, or account.

If you turn on more than one filter, Gitify shows only notifications that match every selected filter. For example, Mentioned plus a specific repository shows mentions in that repository only.

You can choose how Gitify alerts you to new notifications from Settings → System.

• Show system notifications — show native operating system notifications for new unread items
• Play sound — play a sound when new notifications arrive
• Volume — use the volume buttons to change the notification sound level, or reset it

You can change how Gitify looks from Settings → Appearance.

• Design — choose Classic or Glass
• Theme — choose System (follows your operating system), Light, or Dark. Extra themes depend on your design, including color-blind friendly and dimmed variants
• Increase contrast — use higher contrast for text and UI
• Show status icon colors — show colored status icons in the menu bar
• Zoom — zoom in, zoom out, or reset zoom for the whole app
• Show account header — show the account header in the sidebar
• Show full notification title — show full notification titles instead of truncating them

Gitify includes keyboard shortcuts for common actions.

• h — go home
• n — open My Notifications
• w — toggle focused mode (participating only)
• f — open Filters
• i — open My Issues
• p — open My Pull Requests
• r — refresh notifications
• s — open Settings
• a — open Accounts (from Settings)
• q — quit the app

You can also set a global shortcut to show or hide Gitify from Settings → System → Global shortcut.

Unsubscribe from Thread stops future notifications for that thread until you comment on it or get an @mention.

Note: Depending on your notification subscription settings for the repository, you may still get some notifications after unsubscribing from a single thread.

Gitify checks for updates when it starts and every 24 hours.

When an update is ready, it downloads in the background. Gitify then asks you to Restart now or choose Later to apply it the next time Gitify restarts.

To check manually, right-click the tray icon and select Check for Updates.

Gitify is signed in but your inbox is empty? Check the steps for your forge below.

GitHub

GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server:

Classic personal access token (PAT)

1. On GitHub.com, open GitHub → Settings → Developer settings → Personal access tokens. On GitHub Enterprise Cloud or GitHub Enterprise Server, open the same page on your GitHub hostname.
2. Confirm the token Gitify uses is a classic PAT with the scopes listed in What GitHub scopes does Gitify require?.

Note: If your organization uses SAML single sign-on (SSO), authorize the PAT for that organization. See How do I authorize my classic PAT for a GitHub SSO organization?.

Login with GitHub

Gitify signs in with its GitHub OAuth app. Some organizations must approve that app before Gitify can see their notifications.

1. Open GitHub → Settings → Applications → Authorized OAuth Apps.
2. Click the Gitify application.
3. Under Organization access, check the state for each organization:

Note: If an organization shows Request or Disallowed by org owner, you will not get notifications from that organization until access is approved.

Gitea, Forgejo, Codeberg

• Check your personal access token (PAT) is valid and has not expired — create a new one under Settings → Applications if needed
• Confirm the hostname in Gitify matches your instance URL exactly (for example codeberg.org or your self-hosted domain)
• Confirm the PAT can read notifications and repositories on that instance

Bitbucket Cloud

• Check your app password is valid and has not been revoked — create a new one under Personal settings → App passwords if needed
• Confirm the app password grants Read access to Account, Repositories, and Pull requests

GitLab

GitLab Cloud and Self-Managed:

• Check your personal access token (PAT) is valid and has not expired — create a new one under User settings → Access tokens if needed
• Confirm the hostname in Gitify matches your instance URL exactly (for example gitlab.com or your self-hosted domain)
• Confirm the PAT can read notifications and repositories on that instance

Related: What authentication methods does Gitify support? · What GitHub scopes does Gitify require?

You can inspect Gitify with developer tools or by reading its log files.

Chrome Developer Tools

Console logs, network requests, and similar:

1. Right-click the tray icon and select Developer → Toggle Developer Tools, or use the shortcut for your platform:
   • macOS: command + opt + i
   • Windows / Linux: ctrl + shift + i

Application log files

1. Right-click the tray icon and select Developer → View Application Logs, or open the log folder for your platform:
   • macOS: ~/Library/Logs/gitify
   • Windows: %USERPROFILE%\AppData\Roaming\gitify\logs
   • Linux: ~/.config/gitify/logs

If Gitify will not open on Linux because of Chrome Sandbox permissions, the Electron sandbox binary must be owned by root and have the set-user-ID (SUID) bit set.

1. Run:

sudo chown root:root /opt/Gitify/chrome-sandbox
sudo chmod 4755 /opt/Gitify/chrome-sandbox

2. If Gitify still fails to start, check logs with:

journalctl -xe | grep gitify

Note: /opt/Gitify/chrome-sandbox is the path for a standard install. If you installed Gitify as an AppImage or in a custom directory, change the path to match.

On Wayland, the desktop controls window placement, so Gitify may open in the center of the screen. The optional Gitify KWin script on KDE Store places its popup beside your panel when you open it from the tray.

Requirements

• KDE Plasma 6 on a Wayland session.
• Gitify 7.8 or newer, installed separately, with Use X11 backend off.

The script is not needed on an X11 session or when Gitify’s Use X11 backend setting is enabled.

Installation

1. Download gitify.kwinscript from the KDE Store listing.
2. Open System Settings → Window Management → KWin Scripts.
3. Choose Install from File and select the downloaded script.
4. Enable Gitify and click Apply.
5. Open Gitify from its tray icon.

Window placement

The script remembers the last tray-click position for keyboard opens. Before the first tray click, it places Gitify near the end of the panel. It supports top, bottom, left, and right panels, including floating and auto-hide panels.

For current compatibility, source code, and issue reports, see Gitify for KDE on GitHub.

Related: GNOME window positioning.

On Wayland, the desktop controls window placement, so Gitify may open in the center of the screen. The optional Gitify GNOME extension places its popup below its tray icon.

Requirements

• GNOME Shell 50 or 51 on a Wayland session.
• Gitify 7.8 or newer, installed separately, with Use X11 backend off.
• A tray provided by AppIndicator and KStatusNotifierItem Support, or a distribution that includes it, such as Ubuntu. GNOME Shell has no built-in tray.

The extension is not needed on an X11 session or when Gitify’s Use X11 backend setting is enabled.

Installation

From GNOME Extensions

1. Install and enable AppIndicator support if your desktop does not already provide it.
2. Install and enable Gitify on GNOME Extensions.
3. Open the extension’s settings in GNOME Extensions or Extension Manager and use Set up Gitify to check the app and tray setup.
4. Open Gitify from its tray icon. Portable AppImages may need to be launched from your files first.

The GNOME Extensions listing currently provides version 0.1.0 for GNOME Shell 50. For GNOME Shell 51, use a release bundle whose metadata includes Shell 51 until a compatible version is published on the listing.

From a release bundle

Download gitify@gitify.io.shell-extension.zip from the latest extension release, then run:

gnome-extensions install --force gitify@gitify.io.shell-extension.zip

GNOME Shell discovers new extensions at login on Wayland, so log out and back in, then enable the extension:

gnome-extensions enable gitify@gitify.io

If you use Gitify 7.8.0 with the default dark GNOME panel, enable Use white tray icon in Gitify’s Tray settings.

Window placement

The extension places Gitify below its tray icon. If it cannot find the icon, it places the window in the top-right corner of the primary monitor instead.

For current compatibility, source code, and issue reports, see Gitify for GNOME on GitHub.

Related: KDE Plasma window positioning.

You can help Gitify by opening an issue or pull request on GitHub at gitify-app/gitify.

1. Read CONTRIBUTING.md for branch naming, the pull request process, and code style.
2. Browse open issues and pick something you want to work on.

Not a developer? You can still help by reporting bugs, improving docs, or starring and sharing the project.