depends on function for me: - new features tend to be one clean PR since there's so much experimentation on what will work and lots of commits tends to slow th

depends on function for me: - new features tend to be one clean PR since there's so much experimentation on what will work and lots of commits tends to slow things down -- a nominal disk backup is helpful, or even just a commit when taking a break on a branch of your own, no PRs until clean - refactoring tends to be lots of test / experimental / ugly branches with incremental PRs, since tends to be easier to say, ok, change this one thing - been experimenting with some third in-between mode, say add X with a bit more of a planning / sprint mindset vs. oh wow, let's see if this works - feels like this approach is more of works for startups, probably harder to do in enterprise / large teams?