-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated README to note how to use HTTPS clone URLs.
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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 [email protected]:<username>/<project>.git` (replacing `<username>` & `<project>` with the user & project names, respectively, of the repository to be cloned from GitHub). | ||
4. Run `finishGoogleCodeGitHubWikiMigration [email protected]:<username>/<project>.git` (replacing `<username>` & `<project>` 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/<username>/<project>.git` in that case). | ||
5. It should clone the repositories & do its work, leaving you with two locally-modified repositories `<project>` & `<project>.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. | ||
|