When there are no code changes, flags like `--draf...
# report-bugs
t
When there are no code changes, flags like
--draft
don’t do anything
p
(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>
Hey Tyler, this sounds right, its a no op. What are you expecting to happen here / what are you attempting to do?
t
I was expecting it to unpublish the PR. Some of the other flags do seem to take effect in such a scenario, such as publishing.
p
ah interesting, i dont think
--draft
will unpublish even if there was a change.
the docs say
all new PRs will be created in draft mode
and my test confirmed this. I will check in the code to see how its configured
confirmed the code will ignore
--draft
on an update
t
Ah, so it isn’t because I had no code changes. It’s still counterintuitive, though. I expected it to be the inverse operation of
--publish
.
As someone who lives 95% of the day in the terminal, I’d like to have a way to unpublish if I (or Claude) prematurely send out a PR
p
I hear you, I can check in with the team to see why we explicitly made this decision.
👍 1
alright so seems like this is part of some legacy logic and it would be possible. There is a small project that relates to this that i think the team may add this functionality into in the near future
❤️ 1