I totally agree that stacked PRs are the way to go, but I am really against using squash or rebase PR merges: if the issue is that is more difficult to find a change in the git history, how many times do you do that compared to the times you commit. I also disagree that it pollutes the git history.
Creating a feature branch that smaller PRs are merged into before merging into the main Dev could also be a solution.
Is this solution a bit too over engineered? how much time is dedicated to maintain it and how much would we have to update it when time passes?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally agree that stacked PRs are the way to go, but I am really against using squash or rebase PR merges: if the issue is that is more difficult to find a change in the git history, how many times do you do that compared to the times you commit. I also disagree that it pollutes the git history.
Creating a feature branch that smaller PRs are merged into before merging into the main Dev could also be a solution.
Is this solution a bit too over engineered? how much time is dedicated to maintain it and how much would we have to update it when time passes?