-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
magithub warning: Error (use-package): magithub/:config: feature pull-request-merge failed to install: nil #11990
Comments
Most certainly an upstream issue at https://github.com/vermiculus/magithub/ due to magit/magit#3728, and probably not the only one, so please report upstream. Specifically this issue stems from magithub-core.el: `((pull-request-merge . ,(lambda ()
(require 'magit-popup nil t)
(when (boundp 'magit-am-popup)
(magit-define-popup-action 'magit-am-popup
?P "Apply patches from pull request"
#'magithub-pull-request-merge)
t)))
@syl20bnr we might need to disable |
I'm for removing |
I commented |
@syl20bnr -- I dont actually care -- if Will report upstream when I have cycles to so. |
Upstream report: vermiculus/magithub#402 |
Thank you!
…On 2/19/19 12:53 PM, Miciah Dashiel Butler Masters wrote:
Upstream report: vermiculus/magithub#402
<vermiculus/magithub#402>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11990 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABaMJZQrHsEZEz5gJja0RHTtpfeXGhrks5vPDosgaJpZM4a_OdT>.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
Fixed upstream. |
Description
magithub config is slightly broken, but not in an unusable way
Reproduction guide 🪲
github
layer enabledObserved behaviour: 👀 💔
Error (use-package): magithub/:config: feature pull-request-merge failed to install: nil
Expected behaviour: ❤️ 😄
No warning
System Info 💻
The text was updated successfully, but these errors were encountered: