The following list is in approximately my order of implementation intention. Any comments or other suggestion are welcome at gnustavo AT cpan.org.
Implement a plugin to check the safety of rewrites, by detecting when we're amending or rebasing commits that have already been pushed. Here are some discussion about this:
The rebase check could be performed in a pre-rebase hook. But there is no way to check for an amended commit before it's done. One idea would be to record the HEAD's parents in a file during a pre-commit hook and produce an alert during a post-commit hook if the HEAD's parents are the same. In this case, the alert should provide the command that should be performed to revert the amend.
Git::More module currently inherits from
augmenting its functionality with some methods useful for hooks and caching information to speed up things.
App::gh::Git has some problems,
which led me to want to substitute another Git wrapper for it as a base for
Two of the finest candidates on CPAN are
Currently we abort the build on
Along the lines of NFSv4 ACLs (http://tools.ietf.org/html/rfc5661#section-6). I'm thinking about prefixing the what component with a '!'.
In http://search.cpan.org/dist/SVN-Hooks/. Currently we're missing DenyFilenames and UpdateConfFile. Actually, I'm thinking that UpdateConfFile is too much specific. Perhaps something along the lines of this post-update hook would be more interesting: http://stackoverflow.com/questions/279169/deploy-a-project-using-git-push.
Let the user tell which configuration files Git::Hooks should consider.
Currently it considers the three default ones (system,
without knowing which one sets what.
Perhaps we could have a new option
githooks.extra_config that could be set with an array of filenames to invoke
git config --file with in succession.
if set in the default configuration files,
could tell Git::Hooks to grok an extra set of configuration from specific files.
CheckLog.spelling should have a way to register stop words.
I'd have to ask for a change in Text::SpellChecker.
The Gerrit default
commit-msg implements some checks that could be used here.
Some other things to check:
Implement a hook to make it easy to perform some checks on added/modified files. For instance, Perl files should be syntax checked. This could be configured somewhat like this:
CheckFile.rule "\.p[lm]$ perl -c"
The first 'word' in the value would be a regexp used to match the files we're interested in. All that follows would be a command to which the filename would be passed.
This would allow for all kinds of checks specific for some kinds of files. Some interesting ideas here: http://tech.yipit.com/2011/11/16/183772396/.