spr
sapling
spr | sapling | |
---|---|---|
10 | 43 | |
661 | 5,828 | |
- | 1.4% | |
6.7 | 10.0 | |
13 days ago | 5 days ago | |
Go | Rust | |
MIT License | 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.
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.
sapling
- Monorepos: Please Don't (2019)
-
Twenty Years Is Nothing
I am personally surprised that TFA didn't mention either jj or Sapling [0] given its emphasis on how both Git and svn were both made to be backwards compatible!
[0] https://github.com/facebook/sapling
-
Jj init – getting serious about replacing Git with Jujutsu
Lots to digest here! I have been keeping an eye on Pijul so it is cool to see some of its features implemented in jj. Sapling[0], similarly, is a new VCS tool out there which can work with a git repo. It also has anonymous branches, no staging area, supports stacked commits and can track the history of a commit over time. I've been using a similar workflow to the article's author: git with a UI to handle commits of hunks of a file to group related changes. My working branch often has unrelated changes that get tossed from branch to branch as I am able to commit. I haven't figured out where these new tools fit into my workflow yet, but I am glad there's new options that will help making working on a project more flexible and organized.
[0]: https://sapling-scm.com
- Sapling – A VCS from Meta
- Sapling: A Scalable, User-Friendly Source Control System
-
Ask HN: Can we do better than Git for version control?
yep both extended it and have versions that can work against GitHub/git servers.
sapling scm from meta has I think the best cli and VS code UX https://sapling-scm.com/
jj from google is also mercurial derived with very similar cli features like histedit and has support for deferring conflict resolution https://github.com/martinvonz/jj
- Your GitHub pull request workflow is slowing you down
- Sapling – A Scalable, User-Friendly Source Control System
- Mononoke
What are some alternatives?
git-stack - Stacked branch management for Git
go-git - A highly extensible Git implementation in pure Go.
typeformer - A typescript code terraformer
nextjs-template - A bit personalized version of the `with-typescript-eslint-jest` template.
acyl - Testing Environments On Demand
FTC-for-VS-Code - A VS Code extension for accessing FTC snippets, debugger, and Android cmdline tools from a button
jj - A Git-compatible VCS that is both simple and powerful
buck2-prelude - Prelude for the Buck2 project
soft-serve - The mighty, self-hostable Git server for the command line🍦
reactide - Reactide is the first dedicated IDE for React web application development.
cli - GitHub’s official command line tool
dulwich - Pure-Python Git implementation