Closed exosyphon closed 11 months ago
Hi, I can reproduce this on my side. Is this a public PR I can take a look? Can you try doing :e!
instead of Octo pr reload
? Do you get the same error when not using the enable_builtin
feature (using :Octo pr list
instead of Octo
and then selecting pr list
)?
Unfortunately it's not a public PR but I think I reproduced it with a couple repos. I'll confirm that and try :e!
If I use the :Octo pr list command instead of :Octo flow then it works as expected
I tested today whether :e! resolved the issue and it did not. I tried recreating this today with the latest gh cli and now it merges a PR if I select it from the pr list menu π¨
I tried recreating this today with the latest gh cli and now it merges a PR if I select it from the pr list menu π¨
Sorry about that, it was a bug introduced by a very recent PR. Reported and fixed here
I tested today whether :e! resolved the issue and it did not
I just merged another fix related with the buffer reloading. Not sure if it will fix this problem but worth trying with the latest version
@pwntester Looks like you linked to the wrong pull request π , it should be https://github.com/pwntester/octo.nvim/pull/435 that fixed this issue.
BTW I saw exactly the same error before #435 merged
Ouch π thanks for the heads up and fix!
I tested with another branch today and everything works as expected with NVIM 0.9.4 and commit e933611.
Thanks again for all the updates!
Issue Description
Type: bug report
Describe what happened (or what feature you want)
When trying to reload a PR after opening it through the :Octo prompt I receive an error
Describe what you expected to happen
I expect the PR to be reloaded in the buffer without errors
How to reproduce it (as minimally and precisely as possible)
Tell us your environment
MacOS NVIM v0.9.2 Build type: Release LuaJIT 2.1.0-beta3 "octo.nvim": { "branch": "master", "commit": "22a231fc621346734464c3cbca0be467b292b343" },
Anything else we need to know?
If I use the :Octo pr list command instead of :Octo flow then it works as expected