Take back control of your GitHub Notifications with Octobox.
Why is this a thing?
If you manage more than one active project on GitHub, you probably find GitHub Notifications pretty lacking.
Notifications are marked as read and disappear from the list as soon as you load the page or view the email of the notification. This makes it very hard to keep on top of which notifications you still need to follow up on. Most open source maintainers and GitHub staff end up using a complex combination of filters and labels in Gmail to manage their notifications from their inbox. If, like me, you try to avoid email, then you might want something else.
Octobox adds an extra "archived" state to each notification so you can mark it as "done". If new activity happens on the thread/issue/pr, the next time you sync the app the relevant item will be unarchived and moved back into your inbox.
Table of Contents
- Getting Started
- Keyboard shortcuts
You can use Octobox right now at octobox.io, a shared instance hosted by the Octobox team.
Note: octobox.io has a few features intentionally disabled:
Features are disabled for various reasons, such as not wanting to store users' tokens at this time.
You can also host Octobox yourself! See the installation guide for installation instructions and details regarding deployment to Heroku, Docker, and more.
You can run Octobox locally as a desktop app too if you'd like, using Nativefier:
npm install -g nativefier nativefier "https://octobox.io" # Or your own self-hosted URL
This will build a local application (.exe, .app, etc) and put it in your current folder, ready to use.
Web notifications must be enabled in your GitHub settings for Octobox to work.
You can use keyboard shortcuts to navigate and perform certain actions:
a- Select/deselect all
.- Refresh list
j- Move down the list
k- Move up the list
s- Star current notification
x- Mark/unmark current notification
e- Archive current/marked notification(s)
m- Mute current/marked notification(s)
d- Mark current/marked notification(s) as read here and on GitHub
Enter- Open current notification in a new window
? for the help menu.
Support us with a monthly donation and help us continue our activities. Become a backer
Become a sponsor and get your logo on our README on Github with a link to your site. Become a sponsor
If you need want to contribute but don't know where to start, take a look at the issues tagged as "Help Wanted".
Finally, this is an open source project. If you would like to become a maintainer, we will consider adding you if you contribute frequently to the project. Feel free to ask.
For other updates, follow me on Twitter: @teabass.
Note on Patches/Pull Requests
- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it. This is important so we don't break it in a future version unintentionally.
- Send a pull request. Bonus points for topic branches.
Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.