On private development branches, favour rebase over merge, and encourage rewriting history for a clean tree
Abierto
@cmnrd ya está trabajando en esto.
Desde el 14/6/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
I've complained in the past on Zulip about the cleanliness of our git history trees.
Since our contributing guideline is rather indicative, I think it might be worth it to outline some suggestions to make our git history cleaner, such as:
- If working on a branch which nobody is actively using in a productive environment and pulling from the main branch is common, prefer
git pull --rebaseinstead of merge to keep the history linear - Be comfortable to rewrite history by using
rebasewithsquash/fixup/git commit --amendwhen solving linting/styling/typo problems, instead of have several "fix typo" or "minor fix" commits hanging around - Configure pre-commit hooks and ensure each commit is linted, instead of linting everything in one commit
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 0
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
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.