vim-blueplanet
octo.nvim
vim-blueplanet | octo.nvim | |
---|---|---|
2 | 28 | |
10 | 2,120 | |
- | - | |
9.2 | 8.7 | |
about 2 months ago | 30 days ago | |
Lua | Lua | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-blueplanet
-
FAVOURITE PLUGINS
To my knowledge vim-test has no out-of-the-box configuration for TypeScript. I forgot why. Anyway here is my configuration that adds mocha and jest as testers for TypeScript. Though it is mostly based on the existing JavaScript support of vim-test it adds some extra support for Vue testing and project local binaries. Finally ensure you enabled these testers in the vim-test configuration (g:test#custom_runners).
-
Do you use a single init.lua/.vim file or an organized directory structure? Just curious :)
You could take a look here at my configuration. Not sure if that is helpful. You should first read up native packages as it has been linked above. I don't explain the little sneaks and features here. But in its core I put file and directory structure above everything else. I barely import anything manually but fully rely on automated mechanisms. I use lazy loading heavily. I use a mix of .vim and .lua files depending on its content and which language is easier (e.g. mappings are simpler in VimL. In result I have hundreds of files in my configuration. My everything follows a structure. With tools like fzf or telescope it is too easy to open the file you search for. It's basically no overhead. It would be more work to find what I search for if I would have less files. Finally this keeps everything incredibly independent. I can add, change and especially remove thing very easily as most things are very separated and independent. I want to remove a plugin, all its config, mappings, highlights, signs, ... I just remove one directory. Nothing more and nothing less. Clean cut. If I want a plugin and everything around it (copy-paste from above) to be lazy loaded it just works out-of-the-box. It's very simple and elegant. In my opinion. Though you can easily dislike it if you don't agree that strong with the approach it's fundamental arguments.
octo.nvim
- Octo – Edit and review GitHub issues and pull requests inside nvim
-
Anyone have a nice way to get permalink using octo.nvim?
Would be really cool to be able to create a link to the line under the cursor in a new issue using https://github.com/pwntester/octo.nvim . Just like you can do when viewing the file on github.com. Has anyone done this?
-
How to view PR details associated with a blamed line
I'm not aware of any plugins that does this. Maybe these can do it but I'm not an avid user of either. https://github.com/ldelossa/gh.nvim https://github.com/pwntester/octo.nvim
-
a github plugin that allows you to do reviews with lsp built in
Octo maintainer here. You can try this Octo PR, hopefully we will merge it soon https://github.com/pwntester/octo.nvim/pull/349
- What is your nvim workflow for reviewing PRs?
-
What is the best way to review code in neovim?
https://github.com/pwntester/octo.nvim seems like what you’re looking for
-
How to Review a PR without Leaving the Terminal (Neovim)
Not sure, I mostly replied to existing comments. While I was posting the video, someone recommended I check out octo.nvim, which is the same but looks more maintained. Maybe they support it better? Apparently, it's also created by someone working at GitHub I was told.
-
"GitHub Pull Requests and Issues" plugin for Neovim
Might not solve your problem, but https://github.com/pwntester/octo.nvim
-
Complete github issue list when edit commit message
Similar to octo.nvim, then?
-
Are there plugins for Neovim that don't exist, that should exist, in your opinion?
Another alternative is octo.nvim
What are some alternatives?
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
neogit - An interactive and powerful Git interface for Neovim, inspired by Magit
nvim - Simple and ready configuration for neovim(nvim) with LSP. Inited with rust and go support
gh.vim - Vim/Neovim plugin for GitHub
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
diffview.nvim - Single tabpage interface for easily cycling through diffs for all modified files for any git rev.
nvim-dap - Debug Adapter Protocol client implementation for Neovim
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
Vim - The official Vim repository
lazygit.nvim - Plugin for calling lazygit from within neovim.
cli - GitHub’s official command line tool
vim-suda - 🥪 An alternative sudo.vim for Vim and Neovim, limited support sudo in Windows