git-stack
spr
git-stack | spr | |
---|---|---|
10 | 10 | |
482 | 658 | |
1.9% | - | |
8.8 | 6.7 | |
1 day ago | 6 days ago | |
Rust | Go | |
Apache License 2.0 | 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.
git-stack
-
Pijul: Version-Control Post-Git • Goto 2023
I'm not seeing a git compatibility layer? So I think it's a neat project, but I probably won't try it because nearly all code is rooted squarely in git. Even if Pijul is perfect, you'd need to convince everyone else to use it.
Nevertheless, the increased interest in moving to patch based workflows from branch based ones is great. There's a lot of similar tools here (https://github.com/gitext-rs/git-stack/blob/main/docs/compar...) which I refer to infrequently.
Personally my favorite tool for living-with-the-reality-that-is-branches is git-machete (https://github.com/VirtusLab/git-machete).
-
Highlights from Git 2.38
This is huge. I've wasted so much time on this, I wrote my own tool. No idea how thoroughly they've implemented this though (what all corner cases does it update or not)
-
In Praise of Stacked PRs
> Probably some arcane git magic to (interactively) rebase branch
There is not really a command for that yet, short of adding a bunch of `exec` steps to your interactive rebase manually. See https://news.ycombinator.com/item?id=32217204 for an upcoming command.
You might enjoy using https://github.com/gitext-rs/git-stack, which specifically tries to let you manage stacked branches locally while not exposing tons of PRs to your coworkers.
git-branchless itself also lets you manage stacked branches in various ways. For example, you can do `git checkout `, `git commit --amend`, and then `git restack` to rebase all the descendant branches sensibly. You can use it on the local side of things only and then use Github PRs as normal.
-
Termgraph 0.1 released
I've been using termtree in my applications but I'm needing something more like git log --graph for git stack but haven't found a general purpose one (there is an implementation inside of git branchless) and haven't had a chance to make one myself.
-
Git PR management Tooling
Got a comparison of tools in this space at https://github.com/gitext-rs/git-stack/blob/main/docs/comparison.md
- Git-stack: Stacked branch management for Git
-
🗓 ⬇️ Lost in a sea of local branches? `--sort` might help!
I try to keep the number of branches down but git-stack provides something like git log --graph that collapses branches from other users and old branches, keeping the main view clean.
-
Code Review Decision Fatigue
Checkout https://github.com/gitext-rs/git-stack/blob/main/docs/compar... (note, the tool hosting this page is not included but as the author).
As the author of git stack, with all relevant biases, I recommend
- git stack for automating what you are already doing
- git branchless for more power at the risk of incombatibilities because its only as good as the data fed to git hooks
- jj if your open to something very different
spr
- Stacked Pull Requests on GitHub
-
Your GitHub pull request workflow is slowing everyone down
Graphite is neat. If you want something lighter-weight, spr[1] is also worth taking a look at as an entirely client-side "solution" to PR stacking.
Unfortunately, it is very hard to build good code review tooling on top of GitHub due to the severe impedance mismatch between the two models as well as GitHub API limitations and rate limits. That mismatch cannot be fully resolved (branches vs. patches) and results in constant friction, and you end up trusting a third party with full control over your repositories and approval workflows.
Graphite is the best attempt I've seen so far, but it still doesn't come anywhere close to Gerrit[2], which simply uses plain Git commits. Every commit becomes a review, and stacking is accomplished by simply pushing multiple commits. No custom tooling required - just `git push`.
It has very, very good code review UX and allows meaningful and in-depth back-and-forth during a code review, without losing context or having to re-review the entire diff. Once you're past the initial learning curve, it is blissful.
Gerrit is open source and it's what Google uses for many of their public projects such as Chromium and Android, and it is quite easy to self-host. It is entirely built on JGit and even stores code reviews as Git commits alongside the repositories.
If you want to give it a try - there's a well-maintained public instance, Gerrithub[3], operated by Gerritforge. Many open source projects use it.
[1]: https://github.com/ejoffe/spr
[2]: https://www.gerritcodereview.com/
[3]: https://gerrithub.io
-
I (kind of) killed Mercurial at Mozilla
The CLI doesn't help with stacked commits, though. There's tools like spr[1] but none of them are anywhere as pleasant to use as Gerrit (or Phabricator, I guess).
[1]: https://github.com/ejoffe/spr
-
GitHub's Down
Haven't tried this one but Reviewable and Graphite. They're all very nice and yours looks nice also. The problem with all these third party SaaS-es on top of GitHub:
- You have to trust a random (no offense meant!) SaaS company with wide-ranging access to your repository.
- GitHub API rate limits end up causing issues sooner or later. For instance, Reviewable would randomly break and ask you to add more admin users so it could load balance API requests across multiple accounts!
- Likewise, you are still forced into the PR model and things that are trivial in Gerrit, like stacked diffs, are still hard. spr helps[1], but at that point you are piling workarounds on top of workarounds, might as well use a tool that supports the workflow natively...
[1]: https://github.com/ejoffe/spr
-
PR that converts the TypeScript repo from namespaces to modules
But, probably better to use https://github.com/ejoffe/spr (which I found many months after writing the create-stack script). Though, in this particular PR's case, it would have been a lot of work to preserve the commit IDs in the commit messages thanks to its generated nature; if you have a stack produced by hand, it'd work a lot better because a human is editing the PR and its description.
-
Git-stack: Stacked branch management for Git
Another tool to look out for: https://github.com/ejoffe/spr
-
Code Review Decision Fatigue
I've heard good things from our customers about spr for GitHub (https://github.com/ejoffe/spr). It extends git with useful commands and hooks directly into GitHub PRs. We'll be adding some direct support for the tool in Reviewable shortly.
- Simple and straight forward helper to stack pull requests.
- If you love the Gerrit style workflow, checkout SPR, a simple tool to stack pull requests and achieve Gerrit like flow on GitHub without any server side scripts or bots.
- If you love the Gerrit style workflow, checkout SPR, a simple tool to stack pull requests and achieve Gerrit like flow on GitHub without an server side changes of bots.
What are some alternatives?
graphite-cli - Graphite's CLI makes creating and submitting stacked changes easy.
typeformer - A typescript code terraformer
git-branchless - High-velocity, monorepo-scale workflow for Git
acyl - Testing Environments On Demand
autorebase - Automatically rebase all your branches onto master
jj - A Git-compatible VCS that is both simple and powerful
tig - Text-mode interface for git
soft-serve - The mighty, self-hostable Git server for the command line🍦
lazygit.nvim - Plugin for calling lazygit from within neovim.
cli - GitHub’s official command line tool
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows
sapling - A Scalable, User-Friendly Source Control System.