Sean Allred

I don't know of a good way to advise a function such that it 'inserts' functionality (as you do with `magit-log-wash-rev`), but I'll note that [getting the statuses for a...

I'm not saying there's a better way; just that it's too fragile to release 😄 It's still a clever idea – I just hope there's support for it. We'll wait...

You should be able to give `magithub-dir` an appropriate value – unless I'm mistaken, it already is in `.emacs.d`: ```elisp (defun magithub-issue-personal-note-file (issue-or-pr) "Return an absolute filename appropriate for ISSUE-OR-PR."...

The only effect that would have on the cache is re dropbox syncing. The cache is written to on emacs-close and [every 10 minutes of idle time](https://github.com/vermiculus/magithub/blob/18e66c284af911f3e3178550384d050536db42ac/magithub-core.el#L182). If you're ok...

You will see notifications if GitHub created a notification for it. This is the default unless you explicitly unsubscribe from threads you are no longer interested in. Turning this issue...

Magithub notifications are currently only available in the dashboard. There is an open idea (somewhere) to pull notifications for a repository into the status buffer / unread notification count into...

leaving open as an enhancement request for displaying comment reactions

My build directory seems to be `.`. The compilation database is a sibling of the source file in the directory tree. I've not configured anything with `irony-cdb-json-add-compile-commands-path`. Running `irony-cdb-autosetup-compile-options` gives...

However, after running `irony-cdb-autosetup-compile-options` (even with it producing an error), `irony-cdb-menu` now shows a database.

I was in a magit-status buffer, so that explains that. Where should I ideally run it from?