From da74019b41f107e8738149c5796c5b3ab38150f9 Mon Sep 17 00:00:00 2001 From: Morgan Aldridge Date: Sat, 12 Sep 2015 23:07:46 -0400 Subject: [PATCH] Updated README to note how to use HTTPS clone URLs. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 361c973..7c559cb 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ USAGE 1. You must create at least one page in your GitHub project's wiki (I just created the default `Home` page). 2. If you intend to use SSH clone URLs, as opposed to HTTPS clone URLs, you must [generate SSH keys](https://help.github.com/articles/generating-ssh-keys/). 3. 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). -4. Run `finishGoogleCodeGitHubWikiMigration git@github.com:/.git` (replacing `` & `` with the user & project names, respectively, of the repository to be cloned from GitHub). +4. Run `finishGoogleCodeGitHubWikiMigration git@github.com:/.git` (replacing `` & `` with the user & project names, respectively, of the repository to be cloned from GitHub; you can also use HTTPS clone URLs and would run `finishGoogleCodeGitHubWikiMigration https://github.com//.git` in that case). 5. It should clone the repositories & do its work, leaving you with two locally-modified repositories `` & `.wiki`, having committed its changes to each. 6. You should then go into each repository & review all the changes. I suggest at least a `git log` & `git diff HEAD^1` on each. 7. 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.