-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hub-independence #79
Hub-independence #79
Conversation
Now, when you create issues, you'll see the labels available for the repository instead of the previously hard-coded defaults! Fix #6
I didn't realize this wasn't a built-in. I'm surprised Emacs doesn't come with such functionality as core C code.
This should avoid excessively pinging the API.
I seem to get an error on the new version (this is a repo with no CI):
I can't seem to find that function being invoked though, that might just be something wrong with the way I installed it? |
@jgkamat What version of |
I was running a |
I did neglect to update the package-versions before I pushed to master, so it's possible package.el didn't update ghub+ if it didn't think it had to (fixed in b9878f7). Can you try installing |
As for the ping bug, do you want to hop on gitter sometime to hash it out? |
I'll hop on gitter now, I'll see you there. I'll work on installing ghub+ manually too :P |
Try to fix some issues dicussed in #79
On updating to the newest version of
It looks like it's trying to get something from the gh api, failing at getting it, and not handling that (as far as I know), but I have no idea what that could be... I haven't done anything like adding an API key (no instructions in the readme), let me know if I need to do anything like that. |
As discussed on gitter (and reproduced here for other readers), this is because you haven't authenticated |
This is just about ready for release. There is some final testing to do (i.e., I'm just going to used it for a little while to see if it breaks), but everything should be quite stable in this branch now.
Feel free to take this opportunity to review the changes. If you come across any issue in this branch, leave a comment instead of opening up an actual issue.
Fixes #6, #15, #18, #19, #44, #58, and #75