top | item 41506977 (no title) Forge36 | 1 year ago Commits aren't always perfect.Sometimes I'll make the unit test first, which fails CI and the next set of commits implements the behavior. discuss order hn newest trashburger|1 year ago By doing this, you break commit atomicity and make bisects hell. Please don’t do this. Commits aren’t perfect at first for sure, but they should be by the time you make them reviewable. snatchpiesinger|1 year ago It's fine to break commit atomicity on feature branches. You can use git bisect --first-parent on you development/master branch. load replies (1)
trashburger|1 year ago By doing this, you break commit atomicity and make bisects hell. Please don’t do this. Commits aren’t perfect at first for sure, but they should be by the time you make them reviewable. snatchpiesinger|1 year ago It's fine to break commit atomicity on feature branches. You can use git bisect --first-parent on you development/master branch. load replies (1)
snatchpiesinger|1 year ago It's fine to break commit atomicity on feature branches. You can use git bisect --first-parent on you development/master branch. load replies (1)
trashburger|1 year ago
snatchpiesinger|1 year ago