|
|
|
|
|
by scelerat
6 days ago
|
|
I agree with the sentiments -- knowing the scope of a change is more essential, in most cases, than knowing whether the change was a "fix" or a "feature" -- but much of the scope in a project can be gleaned from the files which were touched. So the use case of, "i need to quickly at a glance determine what commits touched what parts of the project" can be answered with some variation on git log --pretty=format:"%n%h %s" --name-only
|
|