v2.1.0

Added requested bulk action support for marking topics read/unread.

The following interactive functions are available:

• gh-notify-marked-notifications-set-read: sets marked notifications as read
• gh-notify-marked-notifications-set-unread: sets marked notifications as unread
• gh-notify-set-status-read: sets notification at point as read
• gh-notify-set-status-unread: sets notification at point as unread

In concert with the existing region aware gh-notify-mark-all-notifications and gh-notify-unmark-all-notifications this should provide all the primitives one needs for local read state management of notifications.

Note that these are db local operations and do not reflect state changes on the remote end. A future release will have more integrated and comprehensive remote state syncing, pending Forge semantics.

v2.0.1

• API bugfixes for issue and pullreq listings
• Updated package dependency versions

v2.0.0

This version of gh-notify is only compatible with the latest version of Magit/Forge as of April, 2024.

It leverages Forge's new built-in incremental fetch logic as well as its updated unread/read state management.

I've updated this for folks who are running the latest versions of Magit/Forge yet still prefer the gh-notify UX for filtering/sorting notifications.

If you are running older versions of Magit/Forge pre October 2023 please use v0.1.0 of gh-notify.

v0.1.0

First stable release of gh-notify.

v0.1.0 changes:

• visit repo at point default binding changed from C-c C-g to C-c C-v
• mark/unmark bindings disabled by default
• various small doc and var changes to make checkdoc, package-lint, and byte-compile happy for melpa release