(1) Do the

--edit

/

--edit-description

/ etc. options work? I see this:

➜  isometric git:(10-21-foo_5) gt submit --edit-description
🥞 Validating that this Graphite stack is ready to submit...

✏️ Preparing to submit PRs for the following branches...
▸ 10-21-foo_5 (Create)

Enter info for new pull request for 10-21-foo_5 ▸ main:

🚀 Pushing branches to remote...
Running git push: [========================================] 100% | Done

📨 Creating/updating PRs...
10-21-foo_5: created
<https://app.graphite.dev/submit/isometric/isometric/27025>

Enter info for new pull request for 10-21-foo_5 ▸ main:

appears, but the CLI zooms past it and goes on to submit. (2) What's the difference between

--edit(...)

and

--cli

? It's hard to say from the help docs

(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

happens consistently, repro copy in the message!

Hey Konrad, what version of the CLI are you on?

gt --version

--cli

allows me to manipulate the current branch im submitting whereas

--edit

pompts for every branch in the stack

Oops, sorry missed that!

➜  ~ gt --version
1.7.3

Ah, I see – missed the "current vs all branches" distinction. Do I understand it correctly that

--edit

then implies

--cli

? (only that it doesn't work in my case)

Hey Konrad, I can actually reproduce this now, will flag to the CLI team.  In the short term, seems like using both

--edit

 and

--cli

 should trigger the prompt.

nice, thanks!

Hey Konrad, writing to let you know our latest release of the CLI fixes this issue! See changelog here. Cheers, Brett

Thanks a lot!