← Back to context Comment by badgersnake 2 months ago Then what’s the point? Just leave them off and run the tests when you want to run them. 5 comments badgersnake Reply thomashabets2 2 months ago Because 99% of my commits are not WIP commits. So I almost always want to run them.Hell, even most WIP commits will pass the tests (e.g. tests are not yet added for the new code), so I'd run them then too. normie3000 2 months ago Some people write tests first. thomashabets2 2 months ago And commit in such that the final timeline has broken tests for half of commits?Sounds like an awful way to live your life. 2 replies →
thomashabets2 2 months ago Because 99% of my commits are not WIP commits. So I almost always want to run them.Hell, even most WIP commits will pass the tests (e.g. tests are not yet added for the new code), so I'd run them then too. normie3000 2 months ago Some people write tests first. thomashabets2 2 months ago And commit in such that the final timeline has broken tests for half of commits?Sounds like an awful way to live your life. 2 replies →
normie3000 2 months ago Some people write tests first. thomashabets2 2 months ago And commit in such that the final timeline has broken tests for half of commits?Sounds like an awful way to live your life. 2 replies →
thomashabets2 2 months ago And commit in such that the final timeline has broken tests for half of commits?Sounds like an awful way to live your life. 2 replies →
Because 99% of my commits are not WIP commits. So I almost always want to run them.
Hell, even most WIP commits will pass the tests (e.g. tests are not yet added for the new code), so I'd run them then too.
Some people write tests first.
And commit in such that the final timeline has broken tests for half of commits?
Sounds like an awful way to live your life.
2 replies →