|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Refined Github||21,788||6 days ago||121||mit||TypeScript|
|:octocat: Browser extension that simplifies the GitHub interface and adds useful features|
|Octolinker||5,182||2||2 days ago||1||December 13, 2015||61||mit||HTML|
|OctoLinker — Links together, what belongs together|
|A collection of awesome browser extensions for GitHub.|
|Browser extension - Get notified about new GitHub notifications|
|[WebExtension] Open GitHub notifications with shortcuts in Gmail.|
|Octohint||923||2 years ago||1||January 19, 2017||10||mit||TypeScript|
|The missing IntelliSense hint for GitHub and GitLab|
|Npmhub||699||2 months ago||6||mit||Svelte|
|🔎 A browser extension to explore npm dependencies on GitHub repos|
|[Web extension] Filter events on github.com activity dashboard.|
|:cactus: Show stats about contributors on github|
|Github Vscode Icons||251||7 months ago||17||mit||TypeScript|
|📦 vscode-icons for github, nearly 1000 file/folder icons|
Browser extension - Get notified about new GitHub notifications
Checks for new GitHub notifications every minute, shows the number of notifications you have, and shows desktop notifications as well.
Make sure to add a token in the options.
The extension requests a couple of optional permissions. It works as intended even if you disallow these. Some features work only when you grant these permissions as mentioned below.
When you click on the extension icon, the GitHub notifications page is opened in a new tab. The
tabs permission lets us switch to an existing notifications tab if you already have one opened instead of opening a new one each time you click it.
This permission also lets us update the notification count immediately after opening a notification. You can find both of these options under the "Tab handling" section in the extension's options page.
If you want to receive desktop notifications for public repositories, you can enable them on extension options page. You will then be asked for the
If you want to receive (useful) desktop notifications for any private repositories you have, you will have to create a GitHub personal access token that has access to the
repo scope as well. This is due to GitHub's current permission scheme, as the only way we can read anything about your private repos is if we have full control over repositories.
If you're concerned with your security in this manner, please feel free to ignore this scope. Just be aware that if you do not grant this scope, clicking on the notification will take you to the notifications home page, since we can't get any information about the repo you got the notification for.
You can opt-in to receive desktop notifications for new notifications on GitHub. The extension checks for new notifications every minute, and displays notifications that arrived after the last check if there are any. Clicking on the notification opens it on GitHub.
If you have desktop notifications enabled as mentioned above, you can also filter which repositories you wish to receive these notifications from. You can do this by only selecting the repositories (that grouped by user/organization) in the options menu.
By default, the extension works for the public GitHub site. If the repo of your company runs GitHub on their own servers via GitHub Enterprise Server, you have to configure the extension to use the API URL. For example