Commit Hero analyzes a repository for commits and awards achievements based on each author's work. It works on a number of version control systems thanks to anyvc.
Install Commit Hero through setuptools:
python setup.py install
It depends on anyvc (which is automatically installed by Setuptools) and the backend for the repository in question, including but not limited to:
Check anyvc's Dependencies for a comprehensive and up-to-date list.
Run it like so:
commithero --help
The shipped Makefile offers to install Commit Hero into a virtual
environment. See make help for details. If you, for example, wish to run
it on your Mercurial repository ~/myrepo, use:
make install-hg run R=~/myrepo
Achievements are unlocked when committing to a repository and subsequently running Commit Hero over it.
Results from previous runs are cached for performance reasons. Technically, a
commithero.state.Repository is pickled to a file called .commithero (see
--cache to modify its name) and loaded in consecutive passes. Use
--nocache to skip the cache.
If your committers screw up their settings -- and boy, they do! -- you can
supply a file mapping author names to real identities via --pseudonyms
(defaults to .names). It is a simple file with the fields committer and
real author delimited either by a space or, if necessary, by an equality
sign. [1] Committer is checked for with the complete originating address (eg.
John Doe <[email protected]>), only the email, and only the username, in that
order.
| [1] | This is compatible with the format used by hgchurn. Use your
repository's .hgchurn file with the --mercurial option. |
By default, only achievements unlocked since the last run are displayed.
Supplying --all will show all achievements (but still hit the cache so it
is lightning fast); --table shows all achievements ordered by author
instead of date unlocked.
You can define additional achievements in a very simple manner: Define a class
derived from commithero.achievements.Achievement and implement its
on_commit method which takes an author (a string) and a commit (a
anyvc.common.repository.Revision). Whenever you return True from such a
method the system considers this particular achievement unlocked. Implementing
on_change, which takes two strings old and new with file contents,
allows you to implement per-file achievements.
The achievement description is automatically retrieved from its docstring and
its name is generated from its class name (eg. a class WellDone becomes
Well Done). See commithero/achievements/ for examples.
- You are free to set
nameon your achievement class if you are unhappy with restrictions imposed by Python. - If you need to generate several achievements from a single class you can return a tuple of title and description on every single invocation.
- When returning an integer from any of the
on_*methods the corresponding author will be awarded the maximum goal as set in the equally-named class attributegoals. - See ProgressiveAchievement for achievements which have multiple levels.
Achievements are currently limited to one repository and can not be shared among several repositories. While there is technically no problem with walking multiple repository histories from one shared state, some achievements assume they are operating on a single repository for semantic purposes.
- git-achievements lets users acquire achievements while using Git. It
enables achievements based solely on local actions such as supplying
--helptogitwhich Commit Hero can never do. Commit Hero is targeted to be run post-factum on already-written version histories and supports a wide range of version control systems. - Python Achievements, tentatively tagged #pychievements, are a collection of achievements invented by the Python community.
- IT achievements/trophies are a collection of achievements invented by the Something Awful forums.