In my last article I presented a simple tool for discovering senior developers from source code history, which imports Git history into a search engine. This lets you do searches like “who is our Sharepoint expert,” or “who fixed all our Oracle problems.” There are a few code search products that handle similiar problems, e.g. Krugle,Github, and Fisheye, however they tend to be focused on who made specific changes, rather than finding out who ran a project.
Version control history typically shows file changes using text diffs – in theory we could instead reconstruct a file before and after a change, then compare the parse trees instead. This is impractical in the general case, and if you read on I’ll show how to handle this correctly.
These results can be obtained from commit history, which includes metadata for commits (e.g. the author and commit comments), as well as the actual changes.
Your new post is loading...