Viewing profile — sameenkarim

Yes it will be coming! The reason it's taking a bit longer is because of the automated rebase that happens after you merge part of a stack. There are some legitimate security conce…

The draft one can't be merged, but the one below it isn't affected and can be merged as long as it's green. The dependency goes bottom-up.

Thanks, definitely sounds like a bug. Will look into this.

Yes that was one of our top priorities. For one, there's a fully public API for all stack operations. So if you don't want to use the `gh stack` CLI, you can build your own: https:…

We've been using the pancake emoji internally so we thought it was a fun easter egg. It'll only be up for a few hours and then will go back to the regular icons :)

I hear you. We had to start with something a bit more minimal, but we are working on a much broader revamp for the PR UI. Part of that will include a persistent view of the stack s…

We're rolling out a series of bug fixes for the issues with squash merging. There's an internal system we have called CPRMC (Create Pull Request Merge Commit) that is used to evalu…

Hey from the GitHub Stacked PRs team! Excited to release this more broadly so anyone can start stacking: https://gh.io/stacks Would love to hear any feedback, especially with the U…

When you're using the UI to open a PR, if you set the base to a branch that has an open PR there'll be an "Add to Stack" option: https://github.github.com/gh-stack/guides/ui/#step-…

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 When PR 1 and 2 are squash merged, main now looks lik…

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 t…

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 …

> 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 …

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

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 (es…

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…

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 ea…

[dead]

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

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

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 …