Closed notnitsuj closed 10 months ago
Has to do with #22467, @frede791 is on it.
@notnitsuj Hey so the issue is that gz is now a submodule on main whereas on your own branch dev
you are still using the old folder structure meaning Git will complain when you are trying to switch branches, as there are files in your working directory that are not tracked by Git, but they exist in the branch you're trying to switch to. Depending on what you have changed, you can force the checkout using -f
or make a new branch from main and cherry-pick your own commits.
Yeah I was able to bypass all that as my changes are unrelated to gz
. Just wanted to let you guys know in case there are any hidden conflicts with making gz
a submodule. Thanks for your replies.
Describe the bug
After I git pulled the latest commits from origin/main to the main branch which seems to have added a new submodule, I couldn't check out to my development branch. The error message is below:
When I used
git status
it only showed my uncommitted changes in the other branch and none of the above.To Reproduce
I don't know which commit I last pulled but it should be
f38fe24a98e05e5ecada347c32e108a12afb03aa
as I pull everyday.Expected behavior
Checkout normally like everyday
Screenshot / Media
No response
Flight Log
N/A
Software Version
main 1.14
Flight controller
N/A
Vehicle type
None
How are the different components wired up (including port information)
No response
Additional context
No response