verco
git-absorb
Our great sponsors
| verco | git-absorb | |
|---|---|---|
| 1 | 22 | |
| 230 | 3,184 | |
| - | - | |
| 10.0 | 7.5 | |
| 6 months ago | 18 days ago | |
| Rust | Rust | |
| GNU General Public License v3.0 only | BSD 3-clause "New" or "Revised" 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.
verco
-
This is how I use vim and git, any other tips?
Check out Verco. I find it superior in almost every way. It also does more than just Git, so you have the same experience no matter what VCS you use.
git-absorb
- Git Absorb
- Git-absorb: Git commit –fixup but automatic
-
OpenTF Repository is now Public
Nice, no need to look up past commits ! Didn't know about this, I had to look it up.
It's a separate project from git [0].
[0]: https://github.com/tummychow/git-absorb
-
Lazygit: Simple terminal UI for Git commands
Boy have I got the thing for you. git absorb - https://github.com/tummychow/git-absorb
The way to work with it is:
git add file1 - tummychow/git-absorb: git commit --fixup, but automatic
-
What do you use for git integration in neovim?
You can also manage via a holistic UI: - Bisection - Log and reflog, stashes - subtrees, submodules - certain third party subcommands like git-absorb, and extend it with your own - interact with issues and pull requests via forge - pretty much all of the hundreds of CLI flags via a modal UI that got generalized and extracted to a lib called transient - well-integrated diff and conflict resolution (which is mostly just smerge) - the rebase/cherry-pick workflows I liked the best, including support for --update-refs - at any time you can always press a key to see the raw commands and output that it's using, which taught me a ton of corner cases - IMO it has a great manual
-
Move File Changes From One Commit To Another
I sometimes use git-absorb to help me if I made a tonne of changes, and can't be arsed to manually make the fixups
-
Theodore Ts'o on how he uses Git when working on Linux (2017)
If done well, your git history carries the information of your process in a very similar way.
You have to be somewhere in the middle, so I'd say to do a semantic rebase at last step before merge. A fantastic tool that is not so well-known is git-absorb, which helps a lot doing that cleanly and automatically.
https://github.com/tummychow/git-absorb
-
Intern fixes 600 bugs but makes only 1 PR because it's more efficient.
Squash merge is like a sledge hammer, interactive rebase + git reset -N HEAD^ + git-absorb + git add -p (or even better, Magit) are surgical tools.
- git-absorb - git commit --fixup, but automatic
What are some alternatives?
vim_examples - Some examples of vim features captured from terminal with asciinema.
git-autofixup - create fixup commits for topic branches
gv.vim - A git commit browser in Vim
magit - It's Magit! A Git Porcelain inside Emacs.
vim-flog - A fast, beautiful, and powerful git branch viewer for vim.
stgit - Stacked Git
gitsigns.nvim - Git integration for buffers
git-instafix - Amend old git commits with a simple UI.
tig-explorer.vim - Vim plugin to use Tig as a git client. Seamless switching between vim and Tig with opening in the same buffer.
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
tig - Text-mode interface for git
transient - Transient commands