File changes cannot be moved because part of this file was already committed, Virtual Branch Created from Initial Repo Commit. App Experiences serious Lags #3579
Assignees
Labels
Comments
|
Thanks for reporting. On Windows, the experience is particularly rough, still, and large repositories are an area to be improved as well. Could you help me reproduce the issue? How did it happen that a virtual branch was created with the same name as the initial commit, if you can recall some details? Thanks for your help. |
Byron
added
the
feedback requested
|
I’d be happy to assist! I’ve encountered this issue twice in a row on the same project. The first time, I was baffled. All app features became unbearably slow—setting the default branch, creating virtual branches, moving files, and even simple drag-and-drop actions took 1-2 minutes to reflect. The virtual branch that appeared had an older commit message and displayed all commits under ‘Local,’ even though those commits were originally from the origin remote. To troubleshoot, I created a new project, and there were no performance issues whatsoever. But suddenly, the same issue resurfaced, impacting performance. For anyone facing a similar problem:
Following these steps resolved the issue for me. Deleting the branch seems to fix the performance problem. I’ve delved into the logs and found some related log entries
|
Byron
removed
the
feedback requested
|
Thanks so much for sharing! 2 minutes for a virtual branch update! Is the repository particularly large, or are there continuous changes to the worktree? Thus far I tried to operate on the Linux kernel repository which often is prohibitive/unusable, so it would be great if I could find an intermediate repository to try things out on. |
|
I don’t believe the repository is any larger than the GitButler repo itself. I apologize for not being able to share the repo details since it’s a closed-source product. However, I’m happy to provide more information and assist in reproducing the issue in any way possible. Here is the log session when the issue branch was created : |
|
Hi @krlvi, I wanted to let you know that it looks like this problem has been fixed in version 0.12.0+ on windows. I tested it for three days on a repository where this issue used to occur within a couple of hours in the previous versions, and I haven't encountered the problem since updating. Thank you for your work on this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unexpectedly, a virtual branch is created with the same name as the initial commit. All files are automatically moved to this new virtual branch and become locked, preventing further movement.
Locked Message :
File changes cannot be moved because part of this file was already committed into this branchNote :
“The initial commit occurred two years ago, and the codebase is considerably large.”
OS : Windows
Build : Nightly Version@0.5.422
The text was updated successfully, but these errors were encountered: