IdeaWell

Project ideas from Hacker News discussions.

Stacked PRs are now live on GitHub

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. A tool that stays focused and simple

“It does exactly what you want and, importantly, no more than that.” – perspectivezoom
“I’d recommend git‑spice, it’s very easy to use and powerful, and of course open‑source.” – theappsecguy

2. Unclear added value & UI‑quality concerns

“If you thought git was complex, wait until you get your 5‑deep stacked PR from that nice coworker!” – OJFord
“Good. This change was unexpected and so unprofessional I thought my browser was compromised.” – cebert

3. Workflow gains: atomic reviews and per‑commit CI

“I’ve had that same ‘what’s the point’ thought … but the benefit is you get CI for each commit!” – mmlb
“If you buy the idea that stacking produces better software, then this also has the opportunity to really help out quite a few people.” – steveklabnik

🚀 Project Ideas

Cross-Repo Stack Manager (CRSM)

Summary

  • Enables stacked pull requests that span multiple GitHub repositories while preserving review state and merge sequencing.
  • Provides a unified UI and CLI to create, track, and merge cross‑repo stacks with conflict‑aware rebase handling.

Details

Key Value
Target Audience Distributed teams building multi‑repo features; maintainers who need atomic merges across services.
Core Feature Automatic base‑linking of PRs across forks/repos, conflict detection, and one‑click stack merge.
Tech Stack Full‑stack: React front‑end, Node.js/Express API, GraphQL, PostgreSQL; GitHub Apps + Octokit for PR management.
Difficulty Medium
Monetization Revenue-ready: {tiered SaaS: Free tier for ≤5 stacks, $9/user/mo for professional, $29/user/mo for enterprise}

Notes

  • HN commenters repeatedly asked for cross‑fork stacking support (e.g., “Is support for cross-fork stacked PRs coming?”).
  • Solves the pain of manually rebasing multiple dependent PRs and missing merge conflicts when squash‑merging stacks.
  • Could spark discussion on best practices for atomic cross‑repo changes and improve adoption of stacked workflows.

PR Signpost Annotation Service (PSAS)

Summary

  • Lets authors attach “signposts” – persistent, non‑code annotations or discussion threads – to specific lines or files in a PR for organized reviewer feedback.
  • Provides unique IDs and a UI overlay that separates conversation context from code review comments.

Details

Key Value
Target Audience Engineering managers and reviewers who need clearer separation of feature design discussions from functional code review.
Core Feature Inline annotation blocks with editable metadata, versioned across rebases, and searchable UI widget.
Tech Stack Front‑end: Vue.js + TypeScript; Back‑end: Go microservice; Storage: Redis + PostgreSQL; Integration via GitHub REST & GraphQL APIs.
Difficulty High
Monetization Revenue-ready: {SaaS pricing: $5/user/mo (team), $15/user/mo (company)}

Notes

  • Directly addresses “sign‑post” suggestions from the discussion (“It’d be so easy to just have a 'sign post' feature”).
  • Would be useful for annotating non‑code rationale, linking to external specs, or holding author notes without cluttering review comments.
  • Generates conversation around UI/UX for code review and could integr... (Truncated for brevity)

Stacked CI Orchestration Platform (SCIP)

Summary

  • Automates per‑commit CI execution and reporting for stacked PR workflows, surfacing results inline with each stack entry.
  • Guarantees that every change in a stack passes CI before merge, reducing “big PR breaks CI” friction.

Details

Key Value
Target Audience CI/CD engineers and teams that enforce strict CI on each stacked change; companies impacted by AI‑generated PR bloat.
Core Feature Queues CI jobs per stack entry, stores results against commit SHA, and displays a stack‑aware CI status badge in GitHub UI.
Tech Stack Backend: Rust microservice; Scheduler: Temporal.io; Front‑end: React; Integration: GitHub Actions and Webhooks.
Difficulty Medium
Monetization Hobby

Notes

  • Commenters highlighted the need for “CI for each commit” and concerns about cross‑platform testing (e.g., “mac/windows/linux/whatever”).
  • Provides a practical solution to the “stacked PRs need per‑commit CI” pains expressed in the thread.
  • Could inspire debate on tooling complexity versus native GitHub CI enhancements.

Read Later