Open seanhagen opened 2 years ago
I guess my first question would be 'is magithub-pull-requests-list
getting defined in time to be used?' Perhaps an autoload cookie is needed -- and as a workaround you could just require the package in your :config
form.
By the way, you might take a look at switching to Forge! It's got much more inertia behind it IMO as a first-class citizen in Magit (being developed by its maintainer). There are some things Magithub can still do that Forge can't (like displaying CI status, if memory serves), but I suspect there are other solutions for this as well out there.
Truth be told, I'm more likely to make further contributions to Forge rather than make enhancements here. My company is standing up a GitLab instance for our production code and I'm more likely to want to integrate with that in my day-to-day -- something Magithub is unlikely to be able to do (#81).
Switching to Forge seems straight-forward enough, I'll give that a shot!
If you're not going to be maintaining Magithub anymore, may I suggest putting the repo in read-only mode or putting a big "DEPRECATED: Please use Forge instead" banner at the top of the README? That way folks would (hopefully) get the message they should be using Forge instead :smile:
done 😄
Trying out Emacs 29 and I'm running into this error after having straight update all the repos:
Here's the relevant section of my config file:
The error seems to be the call to
magithub-pull-requests-list
here