-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
No applicable method: forge--format, nil, "%i:new-comment" #124
Comments
It would appear that (defvar forge-topic-mode-map
(let ((map (make-sparse-keymap)))
(define-key map (kbd "C-c C-n") 'forge-create-post)
(define-key map (kbd "C-c C-r") 'forge-create-post)
(define-key map [remap magit-browse-thing] 'forge-browse-topic)
map)) What exactly were you trying to do? Reply to a PR from the status buffer or create a PR? |
It is
I was trying to reply to the PR, and also trying to see what I can do, exploring how emacs can interact with the review process. As you can see in the PR I had already tried github-review.el, and while that was successful it works by typing comments into a diff-mode buffer, lacking all the power and comfort of the magit interface I am used to, so I wanted to see what capabilities magit and forge have on that front. Going through the manual I now see that
so I guess I've been doing it wrong (and doing it right did allow me to make a comment), however I still would expect either an error message like from Another thing I noticed: the comment I made with forge is visible in the topic view, the comment I made with github-review.el is not. Is this a known limitation/ working as intended, or a bug, or something I didn't do right? |
github-review likely creates 'review' comments which are a separate entity as far as GitHub is concerned. Forge does not yet have support for it, though I do believe it is a planned feature (but no planned release date). |
Does the above patch provide a more useful error message in this case? |
Yes.
There's an option for "reject", "approve" and "plain" comments. I picked the latter, but you're right, they're all still review comments, so I'll go subscribe to #75 for this. |
Just ran into this trying to create a new post. Reproduced as follows:
emacs -q
magit-status
for repository with open PR, in my case this oneforge-pull
forge-create-post
This results in the following stack trace:
Magit 20190316.1829, Git 2.21.0, Emacs 26.1, gnu/linux
The text was updated successfully, but these errors were encountered: