Sebastian Thiel

I think previously there was data-loss when the code operated on Git indices with submodules, hence it was quickly forbidden entirely. However, I also see why submodule support is important...

That's great to hear! I also think that's the expected behaviour, as it ignores all submodule changes outright.

Thanks! Closing as duplicate with the note that [this PR](https://github.com/gitbutlerapp/gitbutler/pull/3573) is going to improve the error message, making it much more specific.

By now it's possible to use the Git executable for authentication. The setting is available in the project settings of existing projects are can be set when adding new ones....

Just as an update, the error messages improved since then. As of Version 0.11.3 (20240419.070253) , it looked like this: And one of the next releases should show something like...

Thanks for sharing, it seems failing to find a merge-base is one reason this error occurs.

GitButler Version 0.11.3 (20240419.070253) has also gained the option to authenticate with the Git binary, and overall authentication was improved a lot. Is there a chance you could retry with...

It seems that as of Version 0.11.3 (20240419.070253), this isn't the case anymore and removing/re-adding a project keeps virtual branches (please see the video below). https://github.com/gitbutlerapp/gitbutler/assets/63622/f416dfb9-b928-4481-aad7-51aff8c7ddc0 Maybe there is something...

Meantime, GitButler 0.11 is available and I wonder if the `tauri` fixes trickled through. Could you try to reproduce the issue with the latest version?

By now the application does a good job at communicating the error and offering help: Based on this, I am closing the issue but invite you to keep commenting if...