Sorry if this is already answered elsewhere. Is there a way to push a stack to the remote without opening a PR?

The

--update-only

flag (or

-u

for short) will only update branches that already have PRs. Is that what you're looking for?

No I don’t think so I have a new stack that I’d like to make sure is on the remote so I don’t risk losing work. But I don’t care to open a PR

Does pushing as draft

gt branch/stack submit --draft

not address this? No reviewers will see this

I’m aware of

--draft

but the issue is that I don’t want to open several stacks of PR’s Here’s my use case: I’m running a bake off of several different tools that we might use in a codebase. I want to be able to share those POCs. Some of the competing tools share some “plumbing”, so my stack branches a few times. Opening so many PRs seems unnecessary since this code is just for evaluation purposes and wont get merged to main

We use PRs to maintain the stack dependencies, so there is no way to do this

Got it, thanks! thats good to know Out of curiosity, I have a few questions if you dont mind • Is this type of feature a “never” thing or a “not now” type thing? • What metadata is tracked on the PR? I thought all that was captured locally bc I can happily use graphite without ever creating a PR

I think it's a "not until we are far less reliant on GitHub" thing to be candid — we want to avoid footguns that result in confusing behavior when working with PRs of stacked changes

Thanks @Jacob Gold! Appreciate it Y’all rock 🤘