Our workflow involves checking out branches based on master, then breaking up feature/bug fixes into multiple small commits. Adding the tests, code review comments, the actual fixes or feature(s). Then we squash and merge through the github interface.A commitzen/husky approach seems like it might conflict with this approach since it apparently expects each and every commit to have a full set of details.How have you worked around this? Am I missing something?Edit: A good example of the types of commits I'm referring to: https://cdn-images-1.medium.com/max/1600/1*H78wgOYCyDH1njyW0LOokg.pngEdit 2: if using this format and you group multiple code review comments into one single commit, which type to you choose?
Submitted January 12, 2019 at 11:13PM by MyyHealthyRewards
No comments:
Post a Comment