Skip to content


Switch branches/tags

Latest commit

…difying getUserData (#524)

* Fix Personal Access Token login method to Github Enterprise Server

* Apply prettier

Co-authored-by: Manos Konstantinidis <>

Git stats


Failed to load latest commit information.

Gitify github codecov downloads

GitHub Notifications on your menu bar. Available on macOS, Windows and Linux. Gitify Mobile has been deprecated in favour of the official GitHub mobile app.



You can download Gitify for free from the website or install it via Homebrew Cask.

brew install --cask gitify

Gitify supports macOS, Windows and Linux.

Prerequisites & Libraries


yarn install


Optional: If you prefer to use your own OAuth credentials, you can do so by passing them as environment variables when bundling the app. This is optional as the app has some default "development" keys (use at your own discretion).

OAUTH_CLIENT_ID="123" OAUTH_CLIENT_SECRET="456789" yarn build

To watch for changes(webpack) in the src directory:

yarn run watch

To run the electron app:

yarn start


The release process is automated. Follow the steps below.

  1. Create a new draft release. Set the tag version to something with the format of v1.2.3. Save as a draft.
  2. Once everything is merged to main, create a branch that starts with release/vX.X.X (ie. release/v1.2.3).
  3. In the same branch, bump the version of the app in the package.json file and open a PR. GitHub Actions will build, sign and upload the release assets for each commit to that branch as long as a branch is named like release/vX.X.X and there is a draft release with the same version number(package.json).
  4. Merge your release branch into main.
  5. Publish the draft release once you've added notes to it and all assets are there.


There are 2 checks - one for prettier and one for the unit tests with jest.

// Run prettier to check
yarn run prettier:check

// Run linter & unit tests with coverage
yarn run test

// Run jest directly - allows to pass arguments like `--watch`
yarn run jest


My notifications aren't showing?

Some organisations require applications to request access before allowing access to any data (including notifications) about their repositories.

To check if Gitify is approved by your organisation you can go to, then click on Gitify and scroll to Organization access.

Something looks wrong - How can I debug?

You can debug Gitify by pressing alt + command + I. This will open the dev tools and then you can see any logs, network requests etc.


  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request
  6. Make sure tests are passing


Gitify is licensed under the MIT Open Source license. For more information, see the LICENSE file in this repository.