A program that helps with checking in code. It automates common git or svn commands.
Latest commit 26929fe Apr 9, 2016 @pgr0ss Merge pull request #29 from leighmcculloch/leighmcculloch/word-wrap-s…

Add a option `-l` for setting the word wrap limit.



Gem Version Build Status

This gem automates a pretty standard workflow when committing code to git, svn, and git-svn. Run rake_commit in your current project, which does the following, depending on source control:


  1. Checks in current changes into a temp commit just in case
  2. Resets soft back to origin/branch (in order to collapse changes into one commit)
  3. Adds new files to git and removes deleted files
  4. Prompts for a commit message
  5. Commits to git
  6. Pulls changes from origin (and does a rebase to keep a linear history)
  7. Runs the default rake task (which should run the tests)
  8. Pushes the commit to origin


  1. Adds new files to git and removes deleted files
  2. Prompts for a commit message
  3. Commits to local git
  4. Pulls changes from SVN
  5. Runs the default rake task (which should run the tests)
  6. Pushes the commit to SVN


  1. Prompts for a commit message
  2. Adds new files to subversion
  3. Deletes missing files from subversion
  4. svn update
  5. Runs the default rake task (which should run the tests)
  6. Checks in the code

The first version started with the code posted at Jay Field's Blog: http://blog.jayfields.com/2006/12/ruby-rake-commit.html. Improvements have been added in from several more projects.


gem install rake_commit


cd /path/to/project

Command line arguments


Print help information.


This will prompt as normal and then commit without running tests or pushing. This is useful for make incremental commits while working.


This tells rake_commit not to prompt and make a new commit. This is useful when you've done a merge by hand and want to preserve the commit. It will stil run rake and then push if rake succeeds.

--without-prompt <prompt>

This will cause rake_commit to skip the named prompt. For example, if you are working by yourself and do not need to prompt for an author, you can use --without-prompt author.


If the same command line arguments are always used, they can be added to a .rake_commit file in the root of the project. For example, this .rake_commit file will tell rake_commit to only prompt for message:

--without-prompt author
--without-prompt feature


rake_commit is released under the MIT license.