1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
0
Hi,
You may want to read this very detailled article about git merge / rebase to define the right process for your use case: https://www.algolia.com/blog/engineering/master-git-rebase/
It provides different paths to create the proper commit history in your repo.
Best,
Didier
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 2 anos
I appreciate the link. However, we already have a definition of how a commit history looks like. That definition says "rebase before merging and no squash commits".