Add support for moved file recognition

Abierto
#338 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
47/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, git, godot
Área
devtools

Línea de trabajo

Start by locating how the plugin reads Git status and maps added and deleted files into Godot's version control UI. Compare that path with the Git CLI's rename detection for identical or similar contents, then identify where a moved file could be represented as one change. Done means moved files are recognized and displayed as a single change with an appropriate status indicator.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Godot version

4.7 stable

Godot Git Plugin version

Unsure, can't find it anywhere in the plugin files in the project

System information

Linux Fedora 44 KDE Plasma Edition Wayland

Problem statement

I have reorganized my project structure. The git CLI command recognized the files I've moved and so sees them as renamed, treating a "deleted" file and "new" file somewhere else with the same contents correctly as a move of a single file. The Godot Git plugin does not and has a deleted file change and an added file change for every single affected file.

Proposed solution

The Godot Git plugin should recognize moved files correctly based on same or similar file contents in a deletion and added context.

It could then mark these occurrences in the UI correctly as a single change instead of two for each and maybe use another color / icon just like it currently has for different actions (new file green with a checkmark, deleted red with an X, etc.).

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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de godotengine/godot-git-plugin

Todos los issues de godotengine/godot-git-plugin

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.