Plotting the source code “TODO” history of the most popular open source projects
1–10 of 114 posts
Re: Plotting the source code “TODO” history of the most popular open source projects
#2Re: Plotting the source code “TODO” history of the most popular open source projects
#3Re: Plotting the source code “TODO” history of the most popular open source projects
#4Re: Plotting the source code “TODO” history of the most popular open source projects
#5Re: Plotting the source code “TODO” history of the most popular open source projects
#6Anyone got a (git-based) one liner to get this info for an arbitrary repo?
git rebase -i --exec 'ack TODO | wc -l >> log' HEAD~20
(create a temp branch first!, then substitute your starting revision, and save-quit the editor that'll pop up)Re: Plotting the source code “TODO” history of the most popular open source projects
#7Anyone got a (git-based) one liner to get this info for an arbitrary repo?
git log --format=format:"%at %H" | sort -nr
gives a list, with the oldest entry first, of just "hash timestamp" pairs, one per line.You can then use e.g.
date -I --date='@1620720025'
to convert the timestamp back to a human-readable date in ISO format, i.e. "2021-05-11".The next step would be to loop over the list, checkout each revision, grep and wc the TODOs, and collect into date buckets. Anyone? :)
Re: Plotting the source code “TODO” history of the most popular open source projects
#8Re: Plotting the source code “TODO” history of the most popular open source projects
#9Anyone got a (git-based) one liner to get this info for an arbitrary repo?
This prints the years - you can the group and plot them as you wish (it should be fairly easy, but I wrestled enough with git). It's a non-rigorous script (eg. it assumes nobody's email/name includes an `YYYY-MM-DD`-like string, and that filenames don't include the colon character):
grep -P '\bTODO\b' -n -R -- * | awk -F: '{ system("git blame "$1" -L "$2","$2) }' | perl -lne 'print /(\d{4})-\d\d-\d\d/'
The working is actually fairly simple:- grep prints filenames and lines
- awk captures the filename and line, and executes a git blame on it
- perl matches the year and prints it
In the Perl matching expression, month and day are not strictly necessary, but disambiguate potential 4-digit numbers in the email/name.
I'm very underwhelmed by the lack of customization of the `git blame` command - `--porcelain` is also uncustomizable, which makes things even uglier.
Note that `git blame` also mishandles some edges (printing "fatal: file [...] has only 1 line").