When authenticating via Personal Access Token (PAT):

• open GitHub Developer Settings >> Tokens
• confirm that your PAT has the following permissions: notifications, read:user and repo

When authenticating via Gitify GitHub App:

• some organizations require GitHub Apps to request access prior to allowing access to organization data (including notifications)
• to check if Gitify is approved by your organization open GitHub Developer Settings >> GitHub Apps, then click on Gitify and scroll to Organization access

To authenticate via an OAuth App:

• create a new application within GitHub → Settings → Developer settings → OAuth Apps.
• Set Authorization callback URL as gitify://oauth
• Complete all remaining mandatory fields
• Click Register application
• Now click on Generate a new client secret
• Use this client/secret pair within Gitify to authenticate.

When you Unsubscribe from Thread, you will not receive future notifications for the thread until you either comment on the thread or get a @mention.

Note: If you are watching a repository, you receive notifications for all threads by default.

Using Chrome Developer Tools (console logs, network requests, etc):

• All platforms: right click tray icon then Developer → Toggle Developer Tools
• macOS: command + opt + i
• Windows: ctrl + shift + i
• Linux: ctrl + shift + i

Using Application Log Files:

• All platforms: right click tray icon then Developer → View Application Logs
• macOS: ~/Library/Logs/gitify
• Windows: %USERPROFILE%\\AppData\\Roaming\\gitify\\logs
• Linux: ~/.config/gitify/logs

If you experience issues opening Gitify on Linux due to Chrome Sandbox permissions, try running the following commands:

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

To check for startup errors

journalctl -xe | grep gitify

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

Check out our open issues and see if there is any existing ideas that you would like to work on.