The linked branch now has a fix for revert. It also has explicit tests for pull, merge, switch and revert.
Up until now at least, it's been an explicit design choice that commit:
* would apply 'read' filtering to get the content to be committed
* wouldn't apply 'write' content filtering and update the working tree.
The feeling was that content filters requiring the latter ought to register a post-commit-hook. I'll look at adding one of those to the keywords plugin.
The linked branch now has a fix for revert. It also has explicit tests for pull, merge, switch and revert.
Up until now at least, it's been an explicit design choice that commit:
* would apply 'read' filtering to get the content to be committed
* wouldn't apply 'write' content filtering and update the working tree.
The feeling was that content filters requiring the latter ought to register a post-commit-hook. I'll look at adding one of those to the keywords plugin.