Hacker News: sameenkarim

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Tue, 14 Apr 2026 00:07:45 +0000

Yes, we handle this both in the CLI and server using git rebase --onto

  git rebase --onto

So for ex in this scenario:

  PR1: main <- A, B              (branch1)
  PR2: main <- A, B, C, D        (branch2)
  PR3: main <- A, B, C, D, E, F  (branch3)

When PR 1 and 2 are squash merged, main now looks like:

  S1 (squash of A+B), S2 (squash of C+D)

Then we run the following:

  git rebase --onto S2 D branch3

Which rewrites branch3 to:

  S1, S2, E, F

This operation moves the unique commits from the unmerged branch and replays them on top of the newly squashed commits on the base branch, avoiding any merge conflicts.

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 23:52:21 +0000

We're shipping a skill file with the CLI: https://skills.sh/github/gh-stack/gh-stack

Everyone will have their own way of structuring stacks, but I've found it great for the agent to plan a stack structure that mirrors the work to be done.

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 23:44:52 +0000

Stacked PRs can be created via the UI, API, or CLI.

You can also run a combination of these. For ex, use another tool like jj to develop locally, push up the branches, and use the gh CLI to batch create a stack of n PRs, without touching local state.

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 23:11:50 +0000

> So, if I have three patches in the stack, and I want to merge the bottom two, I'd merge one, wait for tests to run on the other, merge the second vs. merge just those two in one step

As we have it designed currently, you would have to wait for CI to pass on the bottom two and then you can merge the bottom two in one step. The top of the stack would then get rebased, which will likely trigger another CI run.

Thanks for the callout - we'll update those docs to make it clear multiple PRs can be merged at once.

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 23:03:17 +0000

Yup, there will be an API for stacks, just like there is one for regular PRs.

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 23:01:59 +0000

The CLI is not required and you can push up your bookmarks as branches and open stacked PRs via the UI. You can also use the gh CLI to just create the stacked PRs on github.com (essentially an API wrapper), without using it to manage local state.

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 22:17:20 +0000

The CLI is completely optional, you can create stacked PRs purely via the UI.

Also the rationale for having a chain of branches pointing to each other was so the diff in a PR shows just the relevant changes from the specific branch, not the entire set of changes going back to the parent/trunk.

Curious how you're thinking about it?

New comment by sameenkarim in "GitHub Stacked PRs"

sameenkarim — Mon, 13 Apr 2026 22:11:42 +0000

Yeah features need to be released as GA (general availability) before they can be included in GHES. I don't have a definitive timeline, but it will likely be end of this year or early next.

New comment by sameenkarim in "Show HN: Auto-document your analytics setup (npx package)"

sameenkarim — Wed, 11 Sep 2024 21:28:36 +0000

Wow, that's a lot of events! Hope this helps with keeping track of it all now.

New comment by sameenkarim in "Show HN: Auto-document your analytics setup (npx package)"

sameenkarim — Wed, 11 Sep 2024 21:19:54 +0000

Glad to hear I'm not alone in the frustration! Thanks and let me know how it goes.

Show HN: Auto-document your analytics setup (npx package)

sameenkarim — Wed, 11 Sep 2024 19:56:47 +0000

Hey HN, sharing an npx package that I’ve been working on to help teams automatically document their analytics setups.

It crawls any JS/TS codebase and generates a YAML schema that catalogs all the events, properties, and triggers. Currently supporting GA, Amplitude, Mixpanel, Amplitude, Rudderstack, mParticle, PostHog, Pendo, Heap, Snowplow. Let me know if there’s any more I should add to the list!

Came out of a personal pain where I was struggling to keep tabs on all the analytics events we had implemented. The “tracking plan” spreadsheets just weren’t cutting it, and I wanted something that would automatically update as the code changed.

Hoping it’ll be helpful to other folks as well. Also open to suggestions for things I can build on top of this! Perhaps a code check tool to detect breaking changes or some UI to view this info when you’re querying your analytics data?

Hacker News: sameenkarim

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "GitHub Stacked PRs"

New comment by sameenkarim in "Show HN: Auto-document your analytics setup (npx package)"

New comment by sameenkarim in "Show HN: Auto-document your analytics setup (npx package)"

Show HN: Auto-document your analytics setup (npx package)

Show HN: I made an app to set my status emoji in Slack