This message was deleted.

"nice way" not yet, but you can any time switch the trunk with

gt init --trunk foo

and then manage the branches with that "trunk".

I tried that, but then got the following:

$ gt log
ERROR: Cannot perform this operation on untracked branch my_project_branch.
You can track it by specifying its parent with gt track.

Is

my_project_branch

part of a stack on the previous trunk branch or the new trunk branch?

It is the new trunk

Hm, seems

gt init --trunk foo

does not directly use

foo

but still asks and infers

master

. But if I then select

foo

from the list and make

gt ls

, it works.

I used

gt init

and selected from the list

gt --version

?

I've moved on, so I can't look too deeply into this now. Is it perhaps because

my_project_branch

already had children?

Same version here. And with a different branch name, the

--trunk

option also worked. So no idea.

No worries 🙂

I just tried to set some mid-stack branch as

trunk

and it also worked.

Hm, that's really weird

The “trunk untracked” issue is the same bug that a few others have hit recently (there’s a message in #bug-reports of someone who hit it today) — I fixed it over the weekend and added regression protection to ensure it doesn’t break again, we will release a new version with the fix soon. To answer the original question, we’re working on rolling better multi-trunk support, including simultaneous multi-trunk on the CLI, before the end of the year.

Awesome! Thanks 🙂