{"slug": "stgit", "name": "StGit", "category": "git", "category_name": "Git and code hosting", "description": "", "recommenders": 3, "commenters": 4, "warners": 0, "score": 3.02, "rising": 0.35, "first": "2025-12-05", "latest": "2026-08-03", "why": "StGit/Stacked Git is a proven tool for this and has worked wonders", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 1, "compare": 0, "warn": 0}, "spark": [0, 1, 0, 0, 0, 1, 0, 0, 1, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "StGit/Stacked Git is a proven tool for this and has worked wonders", "kind": "", "icon": true, "domain": null, "github_repo": null, "official_url": "https://stacked-git.github.io", "pricing": "", "aliases": ["StGit", "stgit"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 786552848, "item_id": 49159553, "url": "https://news.ycombinator.com/item?id=49159553", "by": "Fabricio20", "date": "2026-08-03", "version": null, "stance": "recommend", "quote": "StGit/Stacked Git is a proven tool for this and has worked wonders", "excerpt": "> Then you\u2019re maintaining a stack of patches on top of the upstream until the end of time because the maintainers of the projects don\u2019t want AI slop contributions, but now you depend on these changes for your own use so now you\u2019ve created more work for yourself keeping your own fork up to date. I thought about this but I currently maintain a fork of about ~6 things I use on my own, none of which I have any interest o", "context": "maintains personal forks of about 6 tools", "use_case": "maintaining patch stacks on forks", "switched_from": "", "story": "Devtools must be open source"}, {"id": 782438448, "item_id": 48902403, "url": "https://news.ycombinator.com/item?id=48902403", "by": "smcameron", "date": "2026-07-13", "version": null, "stance": "recommend", "quote": "just use stgit[1] to maintain a stack of patches instead of parallel branches, it's so much better", "excerpt": "> Working with lots of changes in parallel on git can be painful. You end up juggling branches and commits, and running scary rebase -i commands that can leave your tree in a half-broken state if you so much as sneeze. I mean, just use stgit[1] to maintain a stack of patches instead of parallel branches, it's so much better. You can easily wrangle thousands of patches (aka commits) with stgit. A lot of people, on fir", "context": "", "use_case": "", "switched_from": "", "story": "The Git history command deserves more attention"}, {"id": 764335232, "item_id": 47770952, "url": "https://news.ycombinator.com/item?id=47770952", "by": "boisterousness", "date": "2026-04-14", "version": null, "stance": "recommend", "quote": "Stacked Git (StGit) [1] is a git CLI add-on for working with stacked commits in your local repo.", "excerpt": "Stacked Git (StGit) [1] is a git CLI add-on for working with stacked commits in your local repo. Why are stacked commits useful? Multiple patches can be developed concurrently and efficiently, with each patch focused on a single concern, for a clean Git commit history and improved productivity. The tutorial [2] says: > One common use of StGit is to \u201cpolish\u201d a Git branch before publishing it to another public reposito", "context": "", "use_case": "stacked commits in git", "switched_from": "", "story": "GitHub Stacked PRs"}, {"id": 738581488, "item_id": 46161343, "url": "https://news.ycombinator.com/item?id=46161343", "by": "smcameron", "date": "2025-12-05", "version": null, "stance": "recommend", "quote": "For me, the answer is stgit.", "excerpt": "For me, the answer is stgit. https://stacked-git.github.io/", "context": "", "use_case": "Stacked git patches", "switched_from": "", "story": "Stacked Diffs with git rebase \u2014onto"}]}], "caveats": [], "who": [{"by": "Fabricio20", "context": "maintains personal forks of about 6 tools", "url": "https://news.ycombinator.com/item?id=49159553", "date": "2026-08-03"}], "tags": [], "use_cases": ["maintaining patch stacks on forks", "stacked commits in git", "stacked git patches"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49156111", "title": "Devtools must be open source", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48901010", "title": "The Git history command deserves more attention", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47757495", "title": "GitHub Stacked PRs", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47499245", "title": "Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46103571", "title": "Stacked Diffs with git rebase \u2014onto", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"recommend": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {"neutral": 1}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {"recommend": 1}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 786552848, "item_id": 49159553, "url": "https://news.ycombinator.com/item?id=49159553", "by": "Fabricio20", "date": "2026-08-03", "version": null, "stance": "recommend", "quote": "StGit/Stacked Git is a proven tool for this and has worked wonders", "excerpt": "> Then you\u2019re maintaining a stack of patches on top of the upstream until the end of time because the maintainers of the projects don\u2019t want AI slop contributions, but now you depend on these changes for your own use so now you\u2019ve created more work for yourself keeping your own fork up to date. I thought about this but I currently maintain a fork of about ~6 things I use on my own, none of which I have any interest o", "context": "maintains personal forks of about 6 tools", "use_case": "maintaining patch stacks on forks", "switched_from": "", "story": "Devtools must be open source"}, {"id": 782438448, "item_id": 48902403, "url": "https://news.ycombinator.com/item?id=48902403", "by": "smcameron", "date": "2026-07-13", "version": null, "stance": "recommend", "quote": "just use stgit[1] to maintain a stack of patches instead of parallel branches, it's so much better", "excerpt": "> Working with lots of changes in parallel on git can be painful. You end up juggling branches and commits, and running scary rebase -i commands that can leave your tree in a half-broken state if you so much as sneeze. I mean, just use stgit[1] to maintain a stack of patches instead of parallel branches, it's so much better. You can easily wrangle thousands of patches (aka commits) with stgit. A lot of people, on fir", "context": "", "use_case": "", "switched_from": "", "story": "The Git history command deserves more attention"}, {"id": 764335232, "item_id": 47770952, "url": "https://news.ycombinator.com/item?id=47770952", "by": "boisterousness", "date": "2026-04-14", "version": null, "stance": "recommend", "quote": "Stacked Git (StGit) [1] is a git CLI add-on for working with stacked commits in your local repo.", "excerpt": "Stacked Git (StGit) [1] is a git CLI add-on for working with stacked commits in your local repo. Why are stacked commits useful? Multiple patches can be developed concurrently and efficiently, with each patch focused on a single concern, for a clean Git commit history and improved productivity. The tutorial [2] says: > One common use of StGit is to \u201cpolish\u201d a Git branch before publishing it to another public reposito", "context": "", "use_case": "stacked commits in git", "switched_from": "", "story": "GitHub Stacked PRs"}, {"id": 760006786, "item_id": 47500424, "url": "https://news.ycombinator.com/item?id=47500424", "by": "keybored", "date": "2026-03-24", "version": null, "stance": "neutral", "quote": "Look at Stacked Git: https://stacked-git.github.io/", "excerpt": "> The binary name for `ripgrep` is `rg`. I don\u2019t understand when people typeset some name in verbatim, lowercase, but then have another name for the actual command. That\u2019s confusing to me. Programmers are too enarmored with lower-case names. Why not Ripgrep? Then I can surmise that there might not be som program ripgrep(1) (there might be a shorter version), since using capital letters is not traditional for CLI prog", "context": "", "use_case": "", "switched_from": "", "story": "Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}"}, {"id": 738581488, "item_id": 46161343, "url": "https://news.ycombinator.com/item?id=46161343", "by": "smcameron", "date": "2025-12-05", "version": null, "stance": "recommend", "quote": "For me, the answer is stgit.", "excerpt": "For me, the answer is stgit. https://stacked-git.github.io/", "context": "", "use_case": "Stacked git patches", "switched_from": "", "story": "Stacked Diffs with git rebase \u2014onto"}]}