1 Answer
- Newest
- Most votes
- Most comments
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
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
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".