Did you get inspiration from octo.nvim? #33
Replies: 1 comment 1 reply
-
|
Hey, thanks. Before pwntester/octo.nvim#98 (comment) and pwntester/octo.nvim#288 (comment) These were major limitations for me, but have this been implemented. The other major difference is "gh.nvim" pulls the remote code local and checks out the branch/commits. I wanted this because it creates a seamless review process. All LSP tools work and you can run tests and local dev environments to confirm the code in the pull works well. I also have started to quite like the thread and issue buffers. Moving forward, I plan to keep removing my usages of GitHub in the browser and place them into gh.nvim. The next big aspect is the "Notifications" features. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I am looking forward to learning and helping out with this plugin.
Quick question: Did you use
octo.nvimbefore? If so, why did you decide to write a new plugin apart from the arguments given in the readme?Beta Was this translation helpful? Give feedback.
All reactions