Comment by thomashabets2 1 month ago Well, unless you inhibit them with `-n`. Which I would for WIP commits. 6 comments thomashabets2 Reply badgersnake 1 month ago Then what’s the point? Just leave them off and run the tests when you want to run them. thomashabets2 1 month 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 1 month ago Some people write tests first. 3 replies →
badgersnake 1 month ago Then what’s the point? Just leave them off and run the tests when you want to run them. thomashabets2 1 month 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 1 month ago Some people write tests first. 3 replies →
thomashabets2 1 month 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 1 month ago Some people write tests first. 3 replies →
Then what’s the point? Just leave them off and run the tests when you want to run them.
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.
3 replies →