41564bd60f
* * add new logo * * add attribution // becuase I based the icon design on one of Raeha's illustrations. * * remove old svgs * update pngs * * change tagline * * add new logo * * add attribution // becuase I based the icon design on one of Raeha's illustrations. * * remove old svgs * update pngs * * change tagline * * capitalise * check in new icons such icon, very image. wow. * Pin the filter/action bar to the top of the notifications table (#821) Fixes #817 * Make the mute selected button available on archive view * Add missing documentation header * Fixed misspellings of 'notification' * Document runtime-dyno-metadata setting in heroku setup Closes #795 * Delete removed labels from subjects when syncing (#825) Fixes #808 * Mark notifications as read when archiving (#826) Fixes #824 * Use git-merge icon for merged pull requests to match GitHub.com behavior (#827) * Fix z-index of navbar dropdown * Dark outline buttons should have white icons on focus as well * Fix sync keyboard shortcut and animation Fixes #829 * Bump autoprefixer-rails from 9.1.2 to 9.1.3 (#830) Bumps [autoprefixer-rails](https://github.com/ai/autoprefixer-rails) from 9.1.2 to 9.1.3. - [Release notes](https://github.com/ai/autoprefixer-rails/releases) - [Changelog](https://github.com/ai/autoprefixer-rails/blob/master/CHANGELOG.md) - [Commits](https://github.com/ai/autoprefixer-rails/compare/9.1.2...9.1.3) Signed-off-by: dependabot[bot] <support@dependabot.com> * Add spacing between icon and text on login button * Simpler relationship between repositories and subjects * Add label scope to Subject * Avoid using fetch_subject config method directly in views * Basic admin page (#833) Closes #784 * Respect github_domain config when linking to notification settings (#832) * Shorten units for human numbers in admin * Fix ambiguous column error when filtering by unlabelled and assignee * Simplify an inverted condition in helper method * Add repository tests * Remove tests of a branch that hasn't been merged yet * Admin controller test * More admin tests * Add test for SyncAllUserNotificationsWorker * Bump pg from 1.0.0 to 1.1.0 (#837) Bumps [pg](https://bitbucket.org/ged/ruby-pg) from 1.0.0 to 1.1.0. - [Changelog](https://bitbucket.org/ged/ruby-pg/src/master/History.rdoc) - [Commits](https://bitbucket.org/ged/ruby-pg/commits) Signed-off-by: dependabot[bot] <support@dependabot.com> * Bump et-orbi from 1.1.4 to 1.1.5 (#838) Bumps [et-orbi](https://github.com/floraison/et-orbi) from 1.1.4 to 1.1.5. - [Release notes](https://github.com/floraison/et-orbi/releases) - [Changelog](https://github.com/floraison/et-orbi/blob/master/CHANGELOG.md) - [Commits](https://github.com/floraison/et-orbi/compare/v1.1.4...v1.1.5) Signed-off-by: dependabot[bot] <support@dependabot.com> * Revert "Bump pg from 1.0.0 to 1.1.0" (#840) * Revert "Bump et-orbi from 1.1.4 to 1.1.5 (#838)" This reverts commit |
||
|---|---|---|
| app | ||
| bin | ||
| config | ||
| db | ||
| docs | ||
| lib | ||
| log | ||
| openshift | ||
| public | ||
| test | ||
| tmp | ||
| vendor/assets | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .env.example | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .rubocop.yml | ||
| .ruby-version | ||
| .slugignore | ||
| .travis.yml | ||
| Dockerfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.txt | ||
| Procfile | ||
| README.md | ||
| Rakefile | ||
| app.json | ||
| config.ru | ||
| docker-compose-dev.yml | ||
| docker-compose.yml | ||
README.md
Octobox 📮
📮 Untangle your GitHub Notifications.
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
Octobox.io
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:
- Subject syncing (includes authorship and open/closed/merged status information) (#411)
- Personal Access Tokens (#185)
Features are disabled for various reasons, such as not wanting to store users' tokens at this time. Some features might never be enabled, and some just might have other prerequisite work pending completion.
Install
You can also host Octobox yourself! See the installation guide for installation instructions and details regarding deployment to Heroku, Docker, and more.
Desktop usage
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 extension
You can also install the cross-browser Octobox Web Extension. It is available for Google Chrome and Mozilla Firefox, but you can also use it with other browsers that support web extensions.
Requirements
Web notifications must be enabled in your GitHub settings for Octobox to work.
Keyboard shortcuts
You can use keyboard shortcuts to navigate and perform certain actions:
a- Select/deselect allror.- Refresh listj- Move down the listk- Move up the lists- Star current notificationx- Mark/unmark current notificationyore- Archive current/marked notification(s)m- Mute current/marked notification(s)d- Mark current/marked notification(s) as read here and on GitHuboorEnter- Open current notification in a new window
Press ? for the help menu.
Backers
Thank you to all our backers! 🙏 [Become a backer]
Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
Contribute
Please do! The source code is hosted at GitHub. If you want something, open an issue or a pull request.
If you need want to contribute but don't know where to start, take a look at the issues tagged as "Help Wanted".
You can also help triage issues. This can include reproducing bug reports, or asking for vital information such as version numbers or reproduction instructions. If you would like to start triaging issues, one easy way to get started is to subscribe to Octobox on CodeTriage.
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 the project on Twitter: @octoboxio.
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.
Copyright
GNU Affero License © 2018 Andrew Nesbitt.