Skip to content

Commit

Permalink
No commit message
Browse files Browse the repository at this point in the history
  • Loading branch information
morgant committed Mar 15, 2015
1 parent ee5f211 commit a93eacc
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,9 @@ There's nothing I can do about the former, but I was able to easily automate res
USAGE
-----

1. Change to a directory where you _do not_ already have the GitHub project in question checked out (for safety reasons, it wants to work on a fresh copy and will not proceed if you already have a copy).
2. Run `./finishGoogleCodeGitHubWikiMigration [email protected]:<username>/<project>.git` (replacing `<username>` & `<project>` with the username & project name, respectively, to be cloned from GitHub).
1. You must creat at least one page in your GitHub project's wiki (I just created the default `Home` page).
2. Change to a directory where you _do not_ already have the GitHub project in question checked out (for safety reasons, it wants to work on a fresh copy and will not proceed if you already have a copy).
2. Run `finishGoogleCodeGitHubWikiMigration [email protected]:<username>/<project>.git` (replacing `<username>` & `<project>` with the username & project name, respectively, to be cloned from GitHub).
3. It should clone the repositories & do it's work, leaving you with two locally-modified repositories `<project>` & `<project>.wiki`, having committed its changes to each.
4. You should then go into each repository & review all the changes. I suggest at least a `git log` & `git diff HEAD^1` on each.
5. If, **and only if**, you feel the changes are correct, you can perform a `git push` on each to commit the changes back to the repository on GitHub.
Expand Down

0 comments on commit a93eacc

Please sign in to comment.