gitsum | parse and summarise git repository history | Parser library
kandi X-RAY | gitsum Summary
kandi X-RAY | gitsum Summary
This package parses a git repository history to collect comprehensive information about the activity in the repo. The parsed data is made available to the user in a tabular format. The package can also generate reports based on the parse data. You can install the development version from GitHub.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gitsum
gitsum Key Features
gitsum Examples and Code Snippets
Community Discussions
Trending Discussions on gitsum
QUESTION
I am working on an R package that is supposed to parse git repository history on a granular level. When validating some of the parsing results with an open source project from GitHub, I encountered something unexpected. In previous validation efforts of my package, I managed reconstruct the number of lines of each file in several git repositories correctly via the output of git log, so I thought using git log
to obtain comprehensive information about changed files is a valid path to follow.
However, I found a commit in the aforementioned project where git log does not seem to convey all information about changed files: The commit with the hash 184f6c71dee03c66c7adaacb024b70d99075ea75
. When resetting HEAD to this commit and running both git log --stat
and git show --log
, I get this:
ANSWER
Answered 2018-Jan-27 at 23:02By default, git log
skips showing diffs for merge commits, while git show
shows combined diffs for merge commits. Adding --cc
(show combined diffs) to the git log
options tells git log
to show combined diffs (or stats for them) for merges.
Note that combine diffs have limited usefulness. For proper analysis you may want -m
, which is an option that both git log
and git show
accept. It tells the commands to, in effect, split each merge into multiple virtual commits. A merge commit has n parents where n ≥ 2, and -m
makes Git turn commit A with parents P1, P2, ..., Pn into commit A-P1 with parent P1; commit A-P2 with parent P2; ...; commit A-Pn with parent Pn, then show (or --stat
) each of those commits individually.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gitsum
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page