kaleidoscope

Expectation In an ideal world, One should be able to identify the product maturity model by merely looking at the commit logs for the  main/master  branch in the git. But it's possible only if, each commit represent a feature  Feature or  change  or  bugfix  or at least for an  incremental atomic change . Problem Having only meaningful commits directly contradicts what I call as “ no code left behind ” principle. Developers shouldn’t leave any code on their development machines. Instead, the code should be committed and pushed to the remote repo, every day before logging off. But sometimes one day is not enough to complete even  incremental atomic changes  suitable for a PR, let alone the code for the full feature. In those cases, this everyday push to the remote repo brings a lot of commits in the final Pull Request aka PR. In this post, I will show how can we combine all these commits before raising a PR, or as they call MR in GitLab. Solution There are two ways, I’ve used in the