[3.6 Git Branching - Rebasing] - C3' is missing in Figure 40
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- git
- Área
- documentation
Línea de trabajo
Start with the source files for Figures 39–41 in the Pro Git book and reproduce the git rebase --onto master server client sequence described in the issue. Compare the diagrams with the expected commit sequence, then verify that the corrected Figures 40 and 41 render correctly on the website and in the PDF.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
There's no existing/similar bug report.
- I have searched the existing issues
This report is about a single actionable bug.
- I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
- This bug is not about a translation or old version
Bug covers book website/pdf
- I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
- This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?
Source files
Describe the bug:
After the command
git rebase --onto master server client
The commit C3 is also re-based in top of master C6. The lack of C3' in Figure 40 and Figure 41 is a bug and causes confusion in the understanding of the topic.
Steps to reproduce:
- Do all git commands to reproduce Figure 39 in your local test repository
- run:
git rebase --onto master server client
After solving the merge conflicts, you will notice that C3 is part of the rebase.
Expected behavior:
At Figure 40 and Figure 41, the master line shall be:
C1 - C2 - C5 - C6 - C3' - C8' - C9'
Screenshots:
No response
Additional context:
No response
Device
No response
Operating system
No response
Browser/application + version
No response
- Lenguaje dominante
- CSS
- Estrellas
- 6.6k
- Forks
- 2.1k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
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 progit/progit2
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Semi-stale link for GitHosting Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
-
enhancement
Dificultad 1/5 1-3 horas Aptitud para principiantes 65/100
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
Todos los issues de progit/progit2
Issues similares
-
sync-en
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
agilepathway/label-checker#640 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
BasedHardware/omi#15662 · 1 comentario ·
-
documentation help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100