Comment by wps
3 hours ago
While I see the utility of partial file commits, I think that it promotes committing untested code. Fossil scm doesn’t have an equivalent feature because of this very issue.
3 hours ago
While I see the utility of partial file commits, I think that it promotes committing untested code. Fossil scm doesn’t have an equivalent feature because of this very issue.
Committing untested code doesn’t matter at all. Merging untested code absolutely does. What you commit locally doesn’t need to correspond at all to what is even shown to others, let alone merged.
Sometimes I think the use cases for “version control I use locally on my machine” and “version control that goes up to the public repo and is reviewed” are so wildly different, it’s a wonder we even use the same tool for both.
This isn’t partial commits. It’s partial staging. This does not promote committing untested code. Committing also doesn’t promote a lack of testing, there’s no justification for that assumption.