by ezekg 4 days ago

My only complaint off the bat is the reliance on the GH CLI, which I don't use either. But maybe by the time it's GA they'll have added UI support.

ameliaquining 4 days ago | [-2 more]
ezekg 4 days ago | [-0 more]

I must have missed that. Amazing! From a reviewer's POV, this will be so nice to at the very least remove diff noise for PRs built on top of another PR. I usually refrain from reviewing child PRs until the parent is merged and the child can be rebased, for the sole reason that the diffs are hard to review i.r.t. what came from where.

NooneAtAll3 4 days ago | [-0 more]

damn, I missed it as well

presenting only cli commands in announcement wasn't a good choice

sameenkarim 4 days ago | [-1 more]

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.

ezekg 4 days ago | [-0 more]

Amazing. Though this wasn't super obvious from the landing page or docs I read.

ZeWaka 4 days ago | [-0 more]

It seems partially exposed in the UI with that dropdown. There's an 'add' and 'unstack' button.

Probably relies on some internal metadata.

SamuelAdams 4 days ago | [-1 more]

CLI is great because now I can tell my AI agent to do it. “Fix all dependabot security issues (copy logs) and run tests to validate functionality. Create each dependency as its own stack (or commit) so that contributors may review each library update easily.”

Wait 10 minutes and you’re done.

sameenkarim 4 days ago | [-0 more]

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.

bmitc 4 days ago | [-4 more]

Why don't you use the CLI?

ezekg 3 days ago | [-3 more]

Because git is all I need.

bmitc 3 days ago | [-2 more]

Then why are you using GitHub? :)

My point is that Git is just a component of the GitHub tool, and the GitHub CLI is quite good and helps automate many things in GitHub. For example, even just using `gh browse` and `gh pr create --web` and `gh pr view --web` are fantastic tools.

ezekg 3 days ago | [-1 more]

I don't need to automate anything in GitHub, I have a web browser for when I need to use GitHub. Installing and learning another CLI seems like a waste of my time for very, very little return.

bmitc 3 days ago | [-0 more]

You would rather manually browse to the repo you're working on in the web interface rather than typing `gh browse`? I hate CLIs, in general, but the GitHub CLI has some very useful commands.