This message was deleted.
# how-do-i
s
This message was deleted.
g
I'd even accept temporarily untracking main and making staging my only base, but I can't seem to find the docs to do this anymore.
a
You can use
gt init
to change your base branch.
g
Ah I see. And while it's obviously not your reccomended workflow, there's no expected issues with running
init
frequently?
a
Correct, no expected issues
g
Awesome, thank you 🙏
j
We're going to be adding better multi-trunk support toward the end of the year, let us know if you find anything while working this way that you'd like us to address!
👍 2
g
Will do!
I'd just like to add a little praise here: It's so nice that it merged into
staging
-- the number of times I've created a branch off of staging, and github insists the PR should be based off
main
and I forget to change it... Setting the base for a branch at branch creation time makes SO MUCH SENSE rather than at PR creation time. This is one of the things that has caused me to use graphite for 100% of my PR management these days!
❤️ 3
let us know if you find anything while working this way that you'd like us to address
Just following up on this, I've been using this method for 3 weeks now, multiple times a day, and frankly have had no issues or problems. It's working great! The only downside is that when I init, any stacks on the other branch usually get lost (though sometimes they come back when I init the other way, spooky). But that's to be expected.
So long as I'm focused on one trunk at a time, this has basically been good enough.
I also think it's worth noting that the workflow has been good enough, too: a separate command to change trunk, and subsequent operations happen against that trunk. The only bit of missing magic would be if
gt move
let me move the branch across trunks, I've wanted that a couple times. (Have gotten around it by untrack > rebase in git > init > track)
p
Wooo! Glad this is working for you @Graham Jans :') Will let you know when we have some multi-trunk improvements down the line!
🙌 1