I personally think one should aim for small commits that try and do one change or achieve one goal. This means the commit message and maybe a line or two should be complementary and describe the contents.
For large PR lots of commits are imho wrong. Nobody in the future is interested in seeing all the individual commits or steps to achieve the final PR. I believe if you are going to refactor (non breaking change) or fix a test or two, those should be separate and their own individual PRs.
I also believe merging in to catch up to head is also not ideal because it addsa. lot of entries to history which are effectively noise. I believe the best solution is to fetch and cherry-pick ones work on the end, so the history is as brief as possible.
I personally think one should aim for small commits that try and do one change or achieve one goal. This means the commit message and maybe a line or two should be complementary and describe the contents.
https://github.com/mP1
For large PR lots of commits are imho wrong. Nobody in the future is interested in seeing all the individual commits or steps to achieve the final PR. I believe if you are going to refactor (non breaking change) or fix a test or two, those should be separate and their own individual PRs.
I also believe merging in to catch up to head is also not ideal because it addsa. lot of entries to history which are effectively noise. I believe the best solution is to fetch and cherry-pick ones work on the end, so the history is as brief as possible.