`gt get --force` is not working as specified Here...
# report-bugs
d
gt get --force
is not working as specified Here's what I'm doing
Copy code
❯ gt checkout @max/09-05-add_fiberloom_to_sutro-2_monorepo
Checked out @max/09-05-add_fiberloom_to_sutro-2_monorepo.
This branch has been updated remotely since you last submitted it.
Last submitted version: v6 (remote at v8).
Run gt get to fetch remote changes.

❯ gt get --force
🌲 Fetching branches from remote...
Running git fetch: [========================================] 100% | Done
main is up to date.

🔄 Syncing branches...
Branch @max/09-05-add_fiberloom_to_sutro-2_monorepo is up to date with remote (PR #1030 v8).
Branch @max/09-05-replace_langgraph_with_fiberloom is up to date with remote (PR #1031 v17).
Branch @dan/09-09-remove_custom_column_names is up to date with remote (PR #1046 v10).
Branch @dan/09-09-convert_to_tsdown is up to date with remote (PR #1047 v10).
Branch @dan/09-09-get_repo_building_with_fiberloom is up to date with remote (PR #1048 v14).
Branch @dan/09-09-sut-1914_switch_to_postgresstorageadapter is up to date with remote (PR #1051 v14).
Branch @dan/09-09-sut-1913_emit_events_for_the_important_initial_app_flow_steps is up to date with remote (PR #1052 v14).
Branch @max/09-09-unify_personas_and_app_overview_step is up to date with remote (PR #1045 v17).
Branch @max/09-09-re-add_app_edit_tools is up to date with remote (PR #1049 v11).
Branch @max/09-09-langfuse_integration is up to date with remote (PR #1050 v10).

🥞 Restacking branches...
@max/09-05-add_fiberloom_to_sutro-2_monorepo does not need to be restacked on main.
@max/09-05-replace_langgraph_with_fiberloom does not need to be restacked on @max/09-05-add_fiberloom_to_sutro-2_monorepo.
@dan/09-09-remove_custom_column_names does not need to be restacked on @max/09-05-replace_langgraph_with_fiberloom.
@dan/09-09-convert_to_tsdown does not need to be restacked on @dan/09-09-remove_custom_column_names.
@dan/09-09-get_repo_building_with_fiberloom does not need to be restacked on @dan/09-09-convert_to_tsdown.
@dan/09-09-sut-1914_switch_to_postgresstorageadapter does not need to be restacked on @dan/09-09-get_repo_building_with_fiberloom.
@dan/09-09-sut-1913_emit_events_for_the_important_initial_app_flow_steps does not need to be restacked on @dan/09-09-sut-1914_switch_to_postgresstorageadapter.
@max/09-09-unify_personas_and_app_overview_step does not need to be restacked on @dan/09-09-sut-1913_emit_events_for_the_important_initial_app_flow_steps.
@max/09-09-re-add_app_edit_tools does not need to be restacked on @max/09-09-unify_personas_and_app_overview_step.
@max/09-09-langfuse_integration does not need to be restacked on @max/09-09-re-add_app_edit_tools.

Already on @max/09-05-add_fiberloom_to_sutro-2_monorepo.

❯ gt status
Passing command through to git...
Running: "git status"

On branch @max/09-05-add_fiberloom_to_sutro-2_monorepo
Your branch and 'origin/@max/09-05-add_fiberloom_to_sutro-2_monorepo' have diverged,
and have 1 and 1 different commits each, respectively.
  (use "git pull" if you want to integrate the remote branch with yours)
I expected to be on the same commit as remote, but I'm not What's going on here?
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 Dan, could you please run
gt feedback --with-debug-context <message>
to send us your CLI logs? We can take a closer look.
d
@Connor Norris I'll look out for it again; I ended up just popping the offending branches and then using
gt checkout
to get the latest
👍 1