fast git config switcher for pair-programming-friendly sessions.
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



Alt text

For Git-friendly Pair-Programming sessions.
Sign your commits with your pair 2-part name and email : andy_john /
When you're done, restore your local git config in a snap.

Quick Usage :

	$ ppgit john andy
	$ ppgit clear
	$ ppgit info

	$ ppgit john andy

	$ ppgit ara nva  --email_root base+*    # ==>  =
    $ ppgit ara nva  --names_separator _and_         # ==>   =  ara_and_nva  (default = '+')

remark : 'ppgit' is a synonym of 'git pp' => you can write

	$ git pp john andy
	$ git pp clear

Usage :

Alt text

1 - When the pairing session starts, quickly set and to the pair values :

	$ ppgit john andy

=> this will update the .git/config of your project to

		name = andy+john
		email =
		name = Your Name
		email =

2 - When the session is finished, restore .git/config to your original local values :

	$ ppgit clear

=> will restore your .git/config to :

		name = Your Name
		email =

3 - TIP : create unique email addresses for each pair based on a common address pattern

	$ ppgit --email_root   base+*

=> you can use the short syntax :

	$ ppgit bob al
	$ ppgit dan cid

are now equivalent to :

	$ ppgit bob al
	$ ppgit dan cid

This info is stored in ~/.gitconfig => it works for all your projects.

Tip : use 1 gmail address + n aliases, so you can choose 1 unique gravatar for each pair (see 1st illustration above) :

    # 1: create the gmail address :

    # 2: use it as a base for your PP pairs :
	$ ppgit --email_root   mycompany+*

    # 3: on, upload and associate an avatar/pair-mugshot with each pair email address.
	# ex: upload 1 image for
	#     upload 1 image for
	#     upload 1 image for

=> you'll get etc.. for free, and each can have a unique gravatar.

Installation :

	$ gem install ppgit

Update :

You are warned when a new version is available :

Alt text

Report bugs to


== Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

== Copyright

Copyright (c) 2010 Alain Ravet. See LICENSE for details. ·