2012-05-26 10:11:03 +00:00
|
|
|
gilog2timesheet
|
|
|
|
|
===============
|
|
|
|
|
|
2012-05-30 20:17:14 +00:00
|
|
|
gitlog2timesheet is a tool to general timesheet from git repositories.
|
2012-05-26 10:11:03 +00:00
|
|
|
|
2012-05-26 10:37:58 +00:00
|
|
|
The hours spent per user per repository can be displayed. This can
|
2012-05-30 20:17:14 +00:00
|
|
|
be useful if you have to complete regular timesheet for european research
|
2012-05-26 10:37:58 +00:00
|
|
|
project or alike.
|
|
|
|
|
|
2012-05-26 10:11:03 +00:00
|
|
|
Usage
|
|
|
|
|
-----
|
|
|
|
|
|
2012-05-30 20:17:14 +00:00
|
|
|
Usage: gitlog2timesheet.py path_to_git_repos path_to_git_repos...
|
2012-05-26 12:27:26 +00:00
|
|
|
|
2012-05-26 10:11:03 +00:00
|
|
|
Options:
|
|
|
|
|
-h, --help show this help message and exit
|
|
|
|
|
-d, --debug output debug messages
|
|
|
|
|
-w COMMITFACTOR, --commitfactor=COMMITFACTOR
|
|
|
|
|
work time factor per commit, default is 4 hours
|
2012-05-26 10:37:58 +00:00
|
|
|
-t, --total total hours worked for each user per
|
|
|
|
|
repository/project
|
2012-05-26 12:27:26 +00:00
|
|
|
-f FORMAT, --outputformat=FORMAT
|
|
|
|
|
output format text, csv (default is text)
|
2012-05-29 07:40:48 +00:00
|
|
|
-u USER, --user=USER limit timesheet to the user specified
|
2012-05-26 10:37:58 +00:00
|
|
|
|
2012-05-26 10:11:03 +00:00
|
|
|
|
|
|
|
|
Sample output
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 20:17:14 +00:00
|
|
|
gitlog2timesheet.py -t -w 4 /home/adulau/git/forban
|
2012-05-26 10:11:03 +00:00
|
|
|
|
|
|
|
|
From Mon Apr 9 15:12:02 2012 to Mon Apr 9 16:12:02 2012
|
|
|
|
|
Alexandre Dulaunoy (a@foo.be) worked on forban
|
|
|
|
|
and did the following: Fixed #12 test if loot directory exists
|
|
|
|
|
|
|
|
|
|
From Mon Apr 9 13:30:30 2012 to Mon Apr 9 14:30:30 2012
|
|
|
|
|
Alexandre Dulaunoy (a@foo.be) worked on forban
|
|
|
|
|
and did the following: Fixed #9 lootcleanup added
|
|
|
|
|
|
|
|
|
|
From Mon Apr 9 12:41:42 2012 to Mon Apr 9 13:41:42 2012
|
|
|
|
|
Alexandre Dulaunoy (a@foo.be) worked on forban
|
|
|
|
|
and did the following: Fixed #10 The browsing is now naturally sorted.
|
|
|
|
|
|
|
|
|
|
From Sun Apr 8 10:35:10 2012 to Sun Apr 8 11:35:10 2012
|
|
|
|
|
Alexandre Dulaunoy (a@foo.be) worked on forban
|
|
|
|
|
and did the following: Fixed #7 cleanup mode added
|
2012-05-30 20:17:14 +00:00
|
|
|
...
|
|
|
|
|
Forban:Philippe Teuwen->12 hours.
|
|
|
|
|
Forban:Alexandre Dulaunoy->964 hours.
|
|
|
|
|
Forban:Olaf TNSB->4 hours.
|
2012-05-26 10:11:03 +00:00
|
|
|
|
|
|
|
|
Software required
|
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
|
|
* Python 2.4 and up
|
|
|
|
|
* git
|
|
|
|
|
|
|
|
|
|
Note
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
Usually assuming that a commit has an amount of time spent on it is usually wrong.
|
|
|
|
|
|
|
|
|
|
But the tool is usually used for organizational structure requiring timesheet in a
|
|
|
|
|
strict format like who did what and when. You have been warned.
|
|
|
|
|
|
2012-05-30 20:17:14 +00:00
|
|
|
Similar tools
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
* http://wadobo.com/trac/dtt manage time dedication per task / project using distributed version control systems.
|
|
|
|
|
|
|
|
|
|
dtt is a real tracking system when you are doing development. gitlog2timesheet objective is to avoid the burden of creating
|
|
|
|
|
timesheets when you have already git repositories around.
|
