spr: Stacked Pull Requests on GitHub
Git spr is a tool designed to manage stacked pull requests on GitHub, allowing developers to create pull requests for each commit on a single branch. This approach facilitates faster reviews and reduces the complexity of managing multiple branches. By using git spr, developers can streamline their workflow and merge changes incrementally without the hassle of traditional branching methods.
- ▪Each commit becomes a pull request, eliminating the need for juggling branches.
- ▪Small pull requests are reviewed faster, leading to more meaningful feedback.
- ▪Git spr integrates seamlessly with GitHub, requiring no additional services or custom merge bots.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/ejoffe/spr |
| Publication time | Sun, 17 May 2026 23:22:48 -0500 |
| Retrieval time | 2026-05-18T04:34:54.418Z |
| Last seen | 2026-05-18T04:34:54.418Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | QCSuPPZGZ3Rc |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Each commit becomes a pull request. Stop juggling branches. git spr manages stacked pull requests on GitHub so you don't have to. Write commits on a single branch, and spr turns each one into its own pull request -- kept in sync, correctly ordered, and ready to merge. Why stacked PRs? Small PRs get reviewed faster. A 50-line change gets meaningful feedback; a 500-line change gets "looks good." No more branch gymnastics. Stop creating feature-part-1, feature-part-2, rebasing one onto the other, and resolving conflicts between them. Ship incrementally. Land the database migration today, the API tomorrow, the UI the day after -- each reviewed and merged independently. Works with native GitHub. No extra services, no custom merge bots. Just pull requests and branches, managed for you.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.