3 ms·
Very true. I knew a lead developer once that with the majority of his commits to TFS would give it some variation on the commit "latest and greatest" (If he did
by cableshaft 11y ago
Very true. I knew a lead developer once that with the majority of his commits to TFS would give it some variation on the commit "latest and greatest" (If he didn't want to type that it might be "l&g").
I didn't speak up about it because I was only a contractor at the time, but it made me wince to see a whole history list of his commits with like 20 "latest and greatest" and maybe three commits that actually said what he did.
But most places I've been to, people have been pretty good about explaining what they've committed, when version control was being used.
- Shorel 11y agoI use this in an alias: git log --pretty=oneline --abbrev-commit --graph --stat Seeing the names of the changed files in each commit gives me a lot more of context than simply the commit description.
- cableshaft 11y agoAnd I could double-click any commit and get the 'changeset details' with all the files modified and their diffs, but it's still better to provide an overview of what you're checking in instead of forcing people to interpret your code. At my current job we have dev tasks associated with the changesets (if applicable), so that helps provide context also.