Skip to content

Instantly share code, notes, and snippets.

@todb-r7
Created March 20, 2012 02:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save todb-r7/2130260 to your computer and use it in GitHub Desktop.
Save todb-r7/2130260 to your computer and use it in GitHub Desktop.
Very short version of setting up a personal fork of Metasploit
This is what I did. It seems to work nicely.
This doc needs to be wikified.
Step zero: Set up your ssh config.
In ~/.ssh/config, add:
Host github_r7
Hostname github.com
User git
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_dsa_github
Step one: Fork and clone
Fork rapid7/metasploit on the Github website
mkdir ~/git/todb-7
git clone github_r7:todb-r7/metasploit-framework
cd todb-r7
Step two: Add a remote tracker to rapid7's metasploit-framework
git remote add rapid7 git://github.com/rapid7/metasploit-framework
git fetch rapid7
git branch --track rapid7 rapid7/master
Step three: Periodically rebase against upstream's master:
git checkout rapid7
git pull -r
git checkout master
git rebase rapid7
git push origin master
This is the moment where you'll notice if your fork is way out of sync
with the remote fork.
Step four: Add code!
Feature branches: you should use them.
Step five: Get someone to land your pull request
Remember that pull requests point to branches, not to commits.
Pull requests should be generated when code is done.
Github notifies automatically, but squeaky wheels have been known to get grease.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment