Bug: Files vanish when deleting current branch in Git plugin
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
Comienza en la acción "Remove Branch" del Commit Dock y reproduce la secuencia de crear, seleccionar y eliminar la rama actual en Godot 4.3 con Git plugin 3.1.1. Rastrea cómo se gestiona la rama activa durante la eliminación y, a continuación, verifica que la UI impide eliminar la rama seleccionada y que los archivos siguen siendo recuperables después de las operaciones con ramas.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Environment where the phenomenon occurred
GodotEngine v4.3.stable.official [77dcf97d8]
Git plugin v3.1.1
Windows10 Home (64bit)
Steps taken and the problem encountered
Using the "Create New Branch" option in the bottom-right menu of the Commit Dock, I created a branch named publish.
The selected branch in the bottom-left of the Commit Dock automatically switched from master to publish.
I committed several files to the publish branch.
Using the "Remove Branch" option in the bottom-right menu of the Commit Dock, I deleted the currently selected publish branch.
Immediately afterward, two error dialogs were displayed, and some of the files I had just committed disappeared.
The first dialog displayed the message: "Cannot open file 'filename.tscn'. The file may have been moved or deleted."
The second dialog displayed the message: "Cannot load due to a missing dependency: filename.gd."
When I closed the dialogs, the editor forcibly closed itself.
Even after restarting the editor, the files remained missing, and errors related to the missing files were displayed.
The deleted files were not found in the recycle bin either.
Workaround
If you select a different branch (e.g., master) and then delete the publish branch, the branch is removed successfully without errors.
Request
Please prevent the deletion of the currently selected branch.
For example, by excluding the currently selected branch from the "Remove Branch" list or by displaying a dialog to interrupt the process.
The Issue is Not File Deletion, but the Ability to Delete the Currently Selected Branch
(Added on 2025/04/23)
When switching branches, it was confirmed that TortoiseGit also deletes files or folders that were tracked in the previous branch (e.g., publish) but not in the branch after switching (e.g., master).
However, these deleted files or folders can be restored by switching back to the original branch (e.g., publish).
master branch
a.txt
publish branch
a.txt
b.txt
File states during branch switching
publish -> master -> publish
a.txt -> a.txt -> a.txt
b.txt -> (deleted) -> b.txt
The main point of this issue is not that files or folders were deleted when the selected branch (e.g., publish) was removed and the remaining branch (e.g., master) was automatically switched to.
Instead, the point is that after the original branch (e.g., publish) was deleted, the files or folders cannot be restored.
File states when the selected branch is deleted, and it is automatically switched to the `master` branch
publish -> master -> publish (deleted)
a.txt -> a.txt -> Cannot switch back.
b.txt -> (deleted) -> Cannot switch back.
Therefore, it would be safer if the list displayed in the "Remove branch" option prevents selecting the currently active branch (e.g., publish).
That is all for my report.
This text was translated from Japanese to English using Windows 10 Copilot.
It was then retranslated back into Japanese with Google Translate to verify its accuracy before posting.
- Lenguaje dominante
- C++
- Estrellas
- 966
- Forks
- 100
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de godotengine/godot-git-plugin
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 47/100
godotengine/godot-git-plugin#338 ·
-
Error when switching branchAbiertobug
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
godotengine/godot-git-plugin#337 · 2 comentarios ·
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 66/100
godotengine/godot-git-plugin#335 ·
-
bug confirmed
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
godotengine/godot-git-plugin#334 · 3 comentarios ·
-
Edit commit messageAbiertoenhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
godotengine/godot-git-plugin#332 ·
Todos los issues de godotengine/godot-git-plugin
Issues similares
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
microsoft/DirectXShaderCompiler#9155 ·
Los mantenedores suelen responder en 2 días
-
Errors in 1.20 proseAbiertoCampaign DiD Campaign EI Campaign HttT Campaign TDG Campaign TSG Campaign WoF Enhancement Help Prose Stable 1.20
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
wesnoth/wesnoth#11749 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
trabucayre/openFPGALoader#767 ·
Los mantenedores suelen responder en 1 día
-
agent:Windows bug in progress pri:medium sev:low testing windows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 91/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
protocolbuffers/protobuf#31768 ·
Los mantenedores suelen responder en 1 día