git-stack
toggleterm.nvim
git-stack | toggleterm.nvim | |
---|---|---|
12 | 89 | |
10 | 3,710 | |
- | - | |
3.9 | 8.2 | |
about 1 month ago | 9 days ago | |
Rust | Lua | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
git-stack
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
git-stack is the most complicated, rewriting history, detecting when a branch was squashed, etc
-
Lazygit: A simple terminal UI for Git commands
I used to use aliases but got frustrated with them when dealing with PRs depending on PRs, so I wrote git-stack [0]. Thought I'd share in case you'd find it useful
[0] https://github.com/epage/git-stack/blob/main/docs/reference....
-
Stacked changes: how FB and Google engineers stay unblocked and ship faster
For anyone interested, I've been collecting notes on various tools in this space: https://github.com/epage/git-stack/blob/main/docs/comparison... (granted the page doesn't mention git-stack since that is assumed)
-
Good strategy to follow for small incremental pull request
Personally, I rebase my PR branches on top of each other, rather than merge. It creates a cleaner history (if your merge policy allows maintaining branch history). Tired of managing these branches, I wrote a tool to help though there are other tools in this space, like git-branchless and graphite.
-
Lightning-fast rebases with Git-move
git-move and git-branchless do some great stuff, I wish this wasn't focused on the performance side to distract from the real value.
What I find useful is not the performance but this line
> For example, it can move entire subtrees, not just branches
The referenced docs mention other great quality of life improvements that streamline standard workflows (e.g. deleting local PR branches when merged into upstream)
When performance does matter is when the rebase operation is a small part of a larger operation. In my related tool, git-stack [0], I rebase all branches on top of their latest upstream branches along with re-arranging and squashing fixup commits and soon other features. When automating entire workflows, having each part be fast is important for the whole to still have decent performance.
[0] https://github.com/epage/git-stack
-
Continuous Integration with Github Actions and Rust
audit for security audits - Separate from regular CI since it only matters for specific changes or when new critical issues come out.
-
My favorite git aliases
You might be interested in git-stack that I've previously announced
-
git-stack: Request for feedback / testers
Could you comment on https://github.com/epage/git-stack/issues/25 for why it helps to iterate to find the last non-conflicting commit to rebase onto?
git-stack is the result of me being tired of annoyances in the PR workflow and trying to improve it, like
-
git-stack: Stacked branch management for Git
Fixing branches off of branches when applying a fixup commit (not implemented yet)
toggleterm.nvim
-
Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
As a data point, I'd like to chime in here. I have been a 15 year user of tmux (and screen before that) and never thought I'd change my development habits. Over the holidays I decided I would do one of those once-every-five-years upgrades to my vim setup as I had accrued dozens of vendored plugins in normal vim and wanted to see what the big deal with neovim was.
I bit the bullet and evaluated some of the "distributions" (AstroNvim and kickstarter) and played around with all the new lua plugins that I had never thought I needed (why use telescope when FZF-vim worked so well?).
Anyways, after a month of tweaking and absorbing, I found myself running Neovide only, and doing something I never thought I'd see, running tmux from within neovim/neovide. I think this only works (for me) because of session management (there are half a dozen plugins for handling quickly changing 'workspaces') and because the built-in terminal (with a very useful plugin called toggleterm: https://github.com/akinsho/toggleterm.nvim) works so well.
I have not stopped using tmux and layouts, and it sits in another fullscreen iterm2 workspace, but I find that I now spend 90% of my time using a fullscreen neovide and summoning/toggling tmux momentarily for running commands.
Of course, the caveat here is that my preferred mode of operation is being fullscreen as often as possible. I think if your preferred mode of operation is to always see splits then running neovim from the terminal within tmux is still the way to go.
As for why I like neovide? I find the animations, when tweaked to be less 'cool' are extremely useful to see where the cursor jumps to. I am also a huge fan of the fact that I can finally use 'linespace' to put some space between my lines of code -- it is an aesthetic I didn't realize I wanted.
-
NeoVim Capability Functions
For splitting the terminal you could try either toggleterm or tmux. If you want to send things from one tmux pane to another, then you can use slime. For a toggle-able filetree, you can use nvim tree.
-
Is there any gotchas for using Neovim's built in terminal?
I just found toggleterm which feels awesome. Pretty much exactly what I was looking for to use with Alacritty but even better since its integrated into the rest of my Neovim workflow.
-
How to unfloat a terminal in Lazyvim
I saw this plugin that tells me how to do it, however I got confused after I added "require("toggleterm").setup({})" in the lazy.lua file and installed the package as well using the Lazy command
-
VSCode-like terminal setup
I tried toggleterm but I wasn't successful.
-
Noobie Needs a Nudge
And I never really got into Gitsigns or vim-fugitive. Lots of people love them, so I'm sure they're great, but I'm happy opening a floating terminal with Toggleterm and using Lazygit.
-
Using Floaterm, what's the best way to toggle between the editor and opened window and maintain the shell session?
I agree with u/Bamseg, but you can get what you want using toggleterm.nvim BUT NOT IN FLOAT.
-
What do you use for git integration in neovim?
I use gitsigns for linewise operations (blame, reset, etc), and a floating terminal (toggleterm) for everything else. flatten.nvim also helps with nested nvim instances.
-
Switching from Emacs. My experience
but I ended up finding a good enough workaround by using Lazygit through Toggleterm.
-
Just got neovim up and working
Perhaps you want something like https://github.com/akinsho/toggleterm.nvim and make a custom profile? Remapping a key for each extension seems fine as well, just remap it per-buffer inside of on_attach
What are some alternatives?
ghstack - Submit stacked diffs to GitHub on the command line
vim-floaterm - :computer: Terminal manager for (neo)vim
lazygit.nvim - Plugin for calling lazygit from within neovim.
neoterm - Wrapper of some vim/neovim's :terminal functions.
graphite-cli - Graphite's CLI makes creating and submitting stacked changes easy.
multiterm.vim - Toggle and Switch Between Multiple Floating Terminals in NeoVim or Vim
git-branchless - High-velocity, monorepo-scale workflow for Git
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
feedback - Public feedback discussions for: GitHub for Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! [Moved to: https://github.com/github-community/community]
tmux - tmux source code
GitUp - The Git interface you've been missing all your life has finally arrived.
AstroVim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins [Moved to: https://github.com/AstroNvim/AstroNvim]