Skip to content
This repository was archived by the owner on Sep 1, 2022. It is now read-only.

Commit 42f0f70

Browse files
authored
Merge pull request #11 from githubtraining/2019-08-28-audit
Work in progress: Fixing broken links
2 parents 8fd60b0 + 423f15a commit 42f0f70

File tree

2 files changed

+6
-7
lines changed

2 files changed

+6
-7
lines changed

Diff for: responses/01_make-a-plan.md

+6-5
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ If you are moving your project to GitHub as a public project, you may want to co
4242

4343
Mapping users, keeping commit comments, and other data migrations are more complex, but not impossible. For most version control systems there are helpful Open Source <sup>[:book:](https://help.github.com/articles/github-glossary/#open-source)</sup> tools available. Here are a few resources:
4444

45-
- [GitHub's documentation on importing from other VCS](https://help.github.com/enterprise/2.12/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)
45+
- [GitHub's documentation on importing from other VCS](https://help.github.com/en/enterprise/admin/migrations/importing-data-from-third-party-version-control-systems)
4646
- [Blog post about GitHub Migrator tool](https://github.com/blog/2110-migrate-your-code-with-the-github-importer)
4747

4848
### Other scenarios
@@ -53,7 +53,7 @@ Mapping users, keeping commit comments, and other data migrations are more compl
5353

5454
### Moving your project from another site not using version control
5555

56-
If you are moving your project from a site not using version control, such as CodePen or Glitch, the steps are a bit different that migrating your project from a source that is using version control. Because of this, we have a dedicated course for uploading your local project to GitHub. If this is your situation, please join the [Uploading your local project to GitHub]({{ host }}/courses/uploading-your-local-project) course to learn how to handle your case.
56+
If you are moving your project from a site not using version control, such as CodePen or Glitch, the steps are a bit different that migrating your project from a source that is using version control. Because of this, we have a dedicated course for uploading your local project to GitHub. If this is your situation, please join the [Uploading your local project to GitHub](https://lab.github.com/githubtraining/uploading-your-project-to-github) course to learn how to handle your case.
5757

5858
<hr>
5959
</details>
@@ -73,7 +73,10 @@ Mapping users, keeping commit comments, and other data migrations are more compl
7373

7474
### :keyboard: Activity: Next steps
7575

76-
Choose the drop-down below that best fits your current situation or for a printable version of the steps in this course, check out the [Quick Reference Guide]({{ host }}/public/{{ course.slug }}.pdf).
76+
Choose the drop-down below that best fits your current situation.
77+
78+
If you don't have a repository to use for this activity, you are welcome to use this one: https://github.com/githubtraining/github-move
79+
7780

7881
<details>
7982
<summary>Using the GitHub Importer</summary>
@@ -111,8 +114,6 @@ Choose the drop-down below that best fits your current situation or for a printa
111114

112115
These migrations are more nuanced and outside the scope of this course. I recommend you go through these steps with a simple repository so you can learn best practices and then apply them to your more complex migration.
113116

114-
If you don't have a repository to use for this activity, you are welcome to use this one: https://github.com/githubtraining/github-move
115-
116117
<hr>
117118
</details>
118119

Diff for: responses/07_confirm-visibility.md

-2
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ You can change the visibility of a repository to Private or Public at any time i
77
### Private Repositories
88
If your repository is private, the only people who can see your code are you and the collaborators <sup>[:book:](https://help.github.com/articles/github-glossary/#collaborator)</sup> you've invited.
99

10-
There is a small charge associated with Private repositories, but if your project has sensitive information, it's worth it.
11-
1210
### Public Repositories
1311
In public repositories, anybody can see your code. Millions of open source repositories on GitHub are public, too!
1412

0 commit comments

Comments
 (0)