Unified command line interface for git, mercurial and subversion.
Usage:
ci "message" commits all changes
st shows all changes
up updates the current directory
Options:
-h --help show this help screen
--debug enable logging of debug messages
--version show version information
committer is best used in combination with ssh keys or credential-cache.
sudo pip install committer
More ways to install committer
How many times did you forget to update before committing your changes?
ci "This is the commit message."
Updates the repository in the current working directory. Only commits your changes when no update-changes have been found.
st
Executes the "status" command known by all version control systems.
up
Updates the current working directory.
It is possible to force committer to execute a command (with arguments)
before performing any other action. Put a INI file called .committerrc
in your current
working directory. Example configuration to execute flake8:
[DEFAULT]
execute_before = flake8
If you want to execute a command only before commit please create a section called commit like this:
[COMMIT]
execute_before = pyb -v
Another good example of the usage of this is to pull from upstream master when you are working in a fork
[COMMIT]
execute_before = git pull upstream master
See .committerrc
in the committer repository.
Committing in a high frequency has advantages:
- prevents merging,
- makes code reviews easier, and
- commit messages for smaller commits "tell a story".
Read more on best practices:
- Micro commits
- A note about git commit messages
- Should I use past or present tense in git commit messages?
Read how to build committer yourself
Did you know all Git repositories on GitHub can be handled using a subversion client?
svn checkout https://github.com/aelgru/committer
Collaborating on GitHub with Subversion
If you do not like the workflow committer implies, you may be interested in hg-git or git-svn.