From 26c245eb3e584966bc8061c42704d5f35718ad49 Mon Sep 17 00:00:00 2001 From: Cameron McEfee Date: Mon, 6 Jun 2011 17:47:43 -0700 Subject: add redirects for old pages --- _posts/2008-01-01-set-up-git-redirect.markdown | 9 +++ _posts/2008-03-01-deploy-capistrano.textile | 89 ---------------------- _posts/2008-03-01-deploy-with-capistrano.textile | 89 ++++++++++++++++++++++ .../2008-03-04-split-a-subpath-into-a-new-repo.md | 29 +++++++ _posts/2008-03-04-split-a-subpath-to-a-new-repo.md | 29 ------- _posts/2009-01-01-set-up-git-redirect.markdown | 9 --- _posts/2009-06-24-creating-a-repo.markdown | 18 +---- _posts/2010-01-01-capistrano.textile | 5 ++ _posts/2010-01-01-changing-author-info.markdown | 5 ++ _posts/2010-01-01-dealing-with-lineendings.textile | 5 ++ _posts/2010-01-01-deleting-a-repo.markdown | 5 ++ _posts/2010-01-01-dmca.md | 5 ++ _posts/2010-01-01-egit-bad-tree.markdown | 5 ++ _posts/2010-01-01-egit-corruption.markdown | 5 ++ _posts/2010-01-01-git-email-settings.markdown | 5 ++ _posts/2010-01-01-git-html-help.markdown | 5 ++ _posts/2010-01-01-git-ignore.markdown | 5 ++ _posts/2010-01-01-leave-a-repo.markdown | 5 ++ _posts/2010-01-01-managing-clients.markdown | 5 ++ _posts/2010-01-01-moving-a-repo.markdown | 5 ++ _posts/2010-01-01-multiple-keys.markdown | 5 ++ _posts/2010-01-01-privacy.markdown | 5 ++ _posts/2010-01-01-pull-requests.md | 5 ++ _posts/2010-01-01-removing-sensitive-data.markdown | 5 ++ ...2010-01-01-splitting-a-subpath-to-a-new-repo.md | 5 ++ _posts/2010-01-01-svn-importing.markdown | 5 ++ _posts/2010-01-01-terms.markdown | 5 ++ _posts/2010-01-01-testing-webhooks.textile | 5 ++ _posts/2010-01-01-troubleshooting-common-issues.md | 5 ++ _posts/2010-01-01-troubleshooting-ssh.textile | 5 ++ ...2010-01-01-working-with-key-passphrases.textile | 5 ++ 31 files changed, 249 insertions(+), 143 deletions(-) create mode 100644 _posts/2008-01-01-set-up-git-redirect.markdown delete mode 100644 _posts/2008-03-01-deploy-capistrano.textile create mode 100644 _posts/2008-03-01-deploy-with-capistrano.textile create mode 100644 _posts/2008-03-04-split-a-subpath-into-a-new-repo.md delete mode 100644 _posts/2008-03-04-split-a-subpath-to-a-new-repo.md delete mode 100644 _posts/2009-01-01-set-up-git-redirect.markdown create mode 100644 _posts/2010-01-01-capistrano.textile create mode 100644 _posts/2010-01-01-changing-author-info.markdown create mode 100644 _posts/2010-01-01-dealing-with-lineendings.textile create mode 100644 _posts/2010-01-01-deleting-a-repo.markdown create mode 100644 _posts/2010-01-01-dmca.md create mode 100644 _posts/2010-01-01-egit-bad-tree.markdown create mode 100644 _posts/2010-01-01-egit-corruption.markdown create mode 100644 _posts/2010-01-01-git-email-settings.markdown create mode 100644 _posts/2010-01-01-git-html-help.markdown create mode 100644 _posts/2010-01-01-git-ignore.markdown create mode 100644 _posts/2010-01-01-leave-a-repo.markdown create mode 100644 _posts/2010-01-01-managing-clients.markdown create mode 100644 _posts/2010-01-01-moving-a-repo.markdown create mode 100644 _posts/2010-01-01-multiple-keys.markdown create mode 100644 _posts/2010-01-01-privacy.markdown create mode 100644 _posts/2010-01-01-pull-requests.md create mode 100644 _posts/2010-01-01-removing-sensitive-data.markdown create mode 100644 _posts/2010-01-01-splitting-a-subpath-to-a-new-repo.md create mode 100644 _posts/2010-01-01-svn-importing.markdown create mode 100644 _posts/2010-01-01-terms.markdown create mode 100644 _posts/2010-01-01-testing-webhooks.textile create mode 100644 _posts/2010-01-01-troubleshooting-common-issues.md create mode 100644 _posts/2010-01-01-troubleshooting-ssh.textile create mode 100644 _posts/2010-01-01-working-with-key-passphrases.textile diff --git a/_posts/2008-01-01-set-up-git-redirect.markdown b/_posts/2008-01-01-set-up-git-redirect.markdown new file mode 100644 index 0000000..afecf45 --- /dev/null +++ b/_posts/2008-01-01-set-up-git-redirect.markdown @@ -0,0 +1,9 @@ +--- +layout: os_redirect +title: Set Up Git +description: A quick guide to help you get started with Git +categories: beginner +redirect_win: /win-set-up-git +redirect_mac: /mac-set-up-git +redirect_linux: /linux-set-up-git +--- diff --git a/_posts/2008-03-01-deploy-capistrano.textile b/_posts/2008-03-01-deploy-capistrano.textile deleted file mode 100644 index 8d54682..0000000 --- a/_posts/2008-03-01-deploy-capistrano.textile +++ /dev/null @@ -1,89 +0,0 @@ ---- -layout: default -title: Deploy with Capistrano -description: How to set up capistrano to pull from a GitHub repo -categories: advanced ---- - -To prepare your project for "Capistrano":http://www.capify.org/, go into the root directory of that project and run @capify@: - -
-$ cd my_project
-$ capify .
-
- -h2. Generate Public Key - -It would probably be a good idea to add a special user on your server(s) specifically for deployment. Once created, make sure to generate a public key for the server and add it to your github account. You may also want to add your personal public key to this new user's @~/.ssh/authorized_keys@ to ease deployment. - -For more help with deploy keys, see "this guide":/deploy-keys. - -h2. Settings - -Here are the 5 most notable Capistrano config options (found in deploy.rb): - -{% highlight ruby %} -default_run_options[:pty] = true # Must be set for the password prompt from git to work -set :repository, "git@github.com:vanpelt/rails-app.git" # Your clone URL -set :scm, "git" -set :user, "deployer" # The server's user for deploys -set :scm_passphrase, "p@ssw0rd" # The deploy user's password -{% endhighlight %} - -h3. Agent Forwarding - -If you're using your own private keys for git you might want to tell Capistrano to use agent forwarding with this command. Agent forwarding can make key management much simpler as it uses your local keys instead of keys installed on the server. - -{% highlight ruby %}ssh_options[:forward_agent] = true{% endhighlight %} - -h3. Set Branch - -You need to tell cap the branch to checkout during deployment: - -{% highlight ruby %}set :branch, "master"{% endhighlight %} - -Older versions of cap need the full branch name: - -{% highlight ruby %}set :branch, "origin/master"{% endhighlight %} - -Older versions of git (e.g. 1.4.4.2) don't support @git checkout -q@, this will cause your deployment to fail. To fix either upgrade git or: - -{% highlight ruby %}set :scm_verbose, true{% endhighlight %} - -h3. Remote Cache - -In most cases you want to use this option, otherwise each deploy will do a full repository clone every time. - -{% highlight ruby %}set :deploy_via, :remote_cache{% endhighlight %} - -Remote caching will keep a local git repo on the server you're deploying to and simply run a fetch from that rather than an entire clone. This is probably the best option as it will only fetch the changes since the last. - -h3. Shallow Clone - -As an alternative to the remote cache approach, you can use shallow cloning. - -{% highlight ruby %}set :git_shallow_clone, 1{% endhighlight %} - -Shallow cloning will do a clone each time, but will only get the top commit, not the entire repo. This makes it a bit closer to how an svn checkout works. Be warned, shallow clone won't work well with the @set :branch@ option. - -h3. Submodules - -If you're using git submodules you must tell cap to fetch them. - -{% highlight ruby %}set :git_enable_submodules, 1{% endhighlight %} - -h2. Migrating from SVN - -Migrating from SVN-based deploys? "Check this thread":http://groups.google.com/group/github/browse_frm/thread/c5d2620c541e4e1a if you run into any problems. - -h2. Known Hosts bug - -If you are not using agent forwarding, the first time you deploy may fail due to Capistrano not prompting with this message: - -
-The authenticity of host 'github.com (207.97.227.239)' can't be established.
-RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
-Are you sure you want to continue connecting (yes/no)?
-
- -To fix this, ssh into your server as the user you will deploy with, run ssh git@github.com and confirm the prompt. diff --git a/_posts/2008-03-01-deploy-with-capistrano.textile b/_posts/2008-03-01-deploy-with-capistrano.textile new file mode 100644 index 0000000..8d54682 --- /dev/null +++ b/_posts/2008-03-01-deploy-with-capistrano.textile @@ -0,0 +1,89 @@ +--- +layout: default +title: Deploy with Capistrano +description: How to set up capistrano to pull from a GitHub repo +categories: advanced +--- + +To prepare your project for "Capistrano":http://www.capify.org/, go into the root directory of that project and run @capify@: + +
+$ cd my_project
+$ capify .
+
+ +h2. Generate Public Key + +It would probably be a good idea to add a special user on your server(s) specifically for deployment. Once created, make sure to generate a public key for the server and add it to your github account. You may also want to add your personal public key to this new user's @~/.ssh/authorized_keys@ to ease deployment. + +For more help with deploy keys, see "this guide":/deploy-keys. + +h2. Settings + +Here are the 5 most notable Capistrano config options (found in deploy.rb): + +{% highlight ruby %} +default_run_options[:pty] = true # Must be set for the password prompt from git to work +set :repository, "git@github.com:vanpelt/rails-app.git" # Your clone URL +set :scm, "git" +set :user, "deployer" # The server's user for deploys +set :scm_passphrase, "p@ssw0rd" # The deploy user's password +{% endhighlight %} + +h3. Agent Forwarding + +If you're using your own private keys for git you might want to tell Capistrano to use agent forwarding with this command. Agent forwarding can make key management much simpler as it uses your local keys instead of keys installed on the server. + +{% highlight ruby %}ssh_options[:forward_agent] = true{% endhighlight %} + +h3. Set Branch + +You need to tell cap the branch to checkout during deployment: + +{% highlight ruby %}set :branch, "master"{% endhighlight %} + +Older versions of cap need the full branch name: + +{% highlight ruby %}set :branch, "origin/master"{% endhighlight %} + +Older versions of git (e.g. 1.4.4.2) don't support @git checkout -q@, this will cause your deployment to fail. To fix either upgrade git or: + +{% highlight ruby %}set :scm_verbose, true{% endhighlight %} + +h3. Remote Cache + +In most cases you want to use this option, otherwise each deploy will do a full repository clone every time. + +{% highlight ruby %}set :deploy_via, :remote_cache{% endhighlight %} + +Remote caching will keep a local git repo on the server you're deploying to and simply run a fetch from that rather than an entire clone. This is probably the best option as it will only fetch the changes since the last. + +h3. Shallow Clone + +As an alternative to the remote cache approach, you can use shallow cloning. + +{% highlight ruby %}set :git_shallow_clone, 1{% endhighlight %} + +Shallow cloning will do a clone each time, but will only get the top commit, not the entire repo. This makes it a bit closer to how an svn checkout works. Be warned, shallow clone won't work well with the @set :branch@ option. + +h3. Submodules + +If you're using git submodules you must tell cap to fetch them. + +{% highlight ruby %}set :git_enable_submodules, 1{% endhighlight %} + +h2. Migrating from SVN + +Migrating from SVN-based deploys? "Check this thread":http://groups.google.com/group/github/browse_frm/thread/c5d2620c541e4e1a if you run into any problems. + +h2. Known Hosts bug + +If you are not using agent forwarding, the first time you deploy may fail due to Capistrano not prompting with this message: + +
+The authenticity of host 'github.com (207.97.227.239)' can't be established.
+RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
+Are you sure you want to continue connecting (yes/no)?
+
+ +To fix this, ssh into your server as the user you will deploy with, run ssh git@github.com and confirm the prompt. diff --git a/_posts/2008-03-04-split-a-subpath-into-a-new-repo.md b/_posts/2008-03-04-split-a-subpath-into-a-new-repo.md new file mode 100644 index 0000000..608c994 --- /dev/null +++ b/_posts/2008-03-04-split-a-subpath-into-a-new-repo.md @@ -0,0 +1,29 @@ +--- +layout: default +title: Split a subpath into a new repo +description: How to generate a new repo from a subpath, retaining history. +categories: advanced +--- + +

From time to time you may find that you want to make a new repo from a subpath of an existing repo. Perhaps you're moving some code out into a library or just want to have a common submodule across projects. Thanks to git, it's easy to do this without losing the history of that subpath in the process.

+ +The Good Stuff +-------------- + +Splitting a subpath into a repo is a fairly straightforward process, even if the command is hard to remember. For this example, we split lib/ out of the "GitHub gem":http://github.com/defunkt/github-gem repo, removing empty commits but retaining the path's history. + +
[tekkub@tekBook: ~/tmp] $ git clone git://github.com/defunkt/github-gem.git
+Initialized empty Git repository in /Users/tekkub/tmp/github-gem/.git/
+remote: Counting objects: 1301, done.
+remote: Compressing objects: 100% (769/769), done.
+remote: Total 1301 (delta 724), reused 910 (delta 522)
+Receiving objects: 100% (1301/1301), 164.39 KiB | 274 KiB/s, done.
+Resolving deltas: 100% (724/724), done.
+
+[tekkub@tekBook: ~/tmp] $ cd github-gem/
+
+[tekkub@tekBook: ~/tmp/github-gem master] $ git filter-branch --prune-empty --subdirectory-filter lib master
+Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
+Ref 'refs/heads/master' was rewritten
+ +Now we have a re-written master branch that contains the files that were in lib/. We can simply add a remote to the new repo and push, or do whatever we want with the repo. diff --git a/_posts/2008-03-04-split-a-subpath-to-a-new-repo.md b/_posts/2008-03-04-split-a-subpath-to-a-new-repo.md deleted file mode 100644 index 608c994..0000000 --- a/_posts/2008-03-04-split-a-subpath-to-a-new-repo.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -layout: default -title: Split a subpath into a new repo -description: How to generate a new repo from a subpath, retaining history. -categories: advanced ---- - -

From time to time you may find that you want to make a new repo from a subpath of an existing repo. Perhaps you're moving some code out into a library or just want to have a common submodule across projects. Thanks to git, it's easy to do this without losing the history of that subpath in the process.

- -The Good Stuff --------------- - -Splitting a subpath into a repo is a fairly straightforward process, even if the command is hard to remember. For this example, we split lib/ out of the "GitHub gem":http://github.com/defunkt/github-gem repo, removing empty commits but retaining the path's history. - -
[tekkub@tekBook: ~/tmp] $ git clone git://github.com/defunkt/github-gem.git
-Initialized empty Git repository in /Users/tekkub/tmp/github-gem/.git/
-remote: Counting objects: 1301, done.
-remote: Compressing objects: 100% (769/769), done.
-remote: Total 1301 (delta 724), reused 910 (delta 522)
-Receiving objects: 100% (1301/1301), 164.39 KiB | 274 KiB/s, done.
-Resolving deltas: 100% (724/724), done.
-
-[tekkub@tekBook: ~/tmp] $ cd github-gem/
-
-[tekkub@tekBook: ~/tmp/github-gem master] $ git filter-branch --prune-empty --subdirectory-filter lib master
-Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
-Ref 'refs/heads/master' was rewritten
- -Now we have a re-written master branch that contains the files that were in lib/. We can simply add a remote to the new repo and push, or do whatever we want with the repo. diff --git a/_posts/2009-01-01-set-up-git-redirect.markdown b/_posts/2009-01-01-set-up-git-redirect.markdown deleted file mode 100644 index afecf45..0000000 --- a/_posts/2009-01-01-set-up-git-redirect.markdown +++ /dev/null @@ -1,9 +0,0 @@ ---- -layout: os_redirect -title: Set Up Git -description: A quick guide to help you get started with Git -categories: beginner -redirect_win: /win-set-up-git -redirect_mac: /mac-set-up-git -redirect_linux: /linux-set-up-git ---- diff --git a/_posts/2009-06-24-creating-a-repo.markdown b/_posts/2009-06-24-creating-a-repo.markdown index 98e3d64..0c87474 100644 --- a/_posts/2009-06-24-creating-a-repo.markdown +++ b/_posts/2009-06-24-creating-a-repo.markdown @@ -1,20 +1,6 @@ --- -layout: default +layout: redirect title: Creating a repo description: How to create a new repo on GitHub redirect_to: /create-a-repo ---- - -Creating a new repo is a simple process. Log in and go to the [dashboard](https://github.com/). - -Click "New Repository" on the right side of the page: - -![](http://img.skitch.com/20100527-nbjhrwesgdjye6nieddmqfigbt.png) - -Fill in the form (only the name is required): - -![](http://img.skitch.com/20100527-dih5dmamhfqhwr65hsa3eek6aj.png) - -After the repo is created, you'll be presented with the empty repo page. This page provides instructions on how to create a new local repo, push an existing repo, or import from an SVN repo. - -![](http://img.skitch.com/20100527-r6h2yp7m8tuxdfhppepjdsetfb.png) \ No newline at end of file +--- \ No newline at end of file diff --git a/_posts/2010-01-01-capistrano.textile b/_posts/2010-01-01-capistrano.textile new file mode 100644 index 0000000..f2b3aea --- /dev/null +++ b/_posts/2010-01-01-capistrano.textile @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Capistrano +redirect_to: /deploy-with-capistrano +--- \ No newline at end of file diff --git a/_posts/2010-01-01-changing-author-info.markdown b/_posts/2010-01-01-changing-author-info.markdown new file mode 100644 index 0000000..37ed782 --- /dev/null +++ b/_posts/2010-01-01-changing-author-info.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Changing author info +redirect_to: /change-author-info +--- \ No newline at end of file diff --git a/_posts/2010-01-01-dealing-with-lineendings.textile b/_posts/2010-01-01-dealing-with-lineendings.textile new file mode 100644 index 0000000..8b695e3 --- /dev/null +++ b/_posts/2010-01-01-dealing-with-lineendings.textile @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Dealing with line endings +redirect_to: /line-endings +--- \ No newline at end of file diff --git a/_posts/2010-01-01-deleting-a-repo.markdown b/_posts/2010-01-01-deleting-a-repo.markdown new file mode 100644 index 0000000..65d27de --- /dev/null +++ b/_posts/2010-01-01-deleting-a-repo.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Deleting a repo +redirect_to: /delete-a-repo +--- diff --git a/_posts/2010-01-01-dmca.md b/_posts/2010-01-01-dmca.md new file mode 100644 index 0000000..9a950e6 --- /dev/null +++ b/_posts/2010-01-01-dmca.md @@ -0,0 +1,5 @@ +--- +layout: redirect +title: DMCA Takedown +redirect_to: /dmca-takedown +--- \ No newline at end of file diff --git a/_posts/2010-01-01-egit-bad-tree.markdown b/_posts/2010-01-01-egit-bad-tree.markdown new file mode 100644 index 0000000..256537e --- /dev/null +++ b/_posts/2010-01-01-egit-bad-tree.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Fixing bad tree +redirect_to: /fix-a-bad-tree +--- \ No newline at end of file diff --git a/_posts/2010-01-01-egit-corruption.markdown b/_posts/2010-01-01-egit-corruption.markdown new file mode 100644 index 0000000..5839252 --- /dev/null +++ b/_posts/2010-01-01-egit-corruption.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Fixing egit corruption +redirect_to: /fix-egit-corruption +--- \ No newline at end of file diff --git a/_posts/2010-01-01-git-email-settings.markdown b/_posts/2010-01-01-git-email-settings.markdown new file mode 100644 index 0000000..cd85a2b --- /dev/null +++ b/_posts/2010-01-01-git-email-settings.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Setting user name, email and GitHub token +redirect_to: /set-your-user-name-email-and-github-token +--- \ No newline at end of file diff --git a/_posts/2010-01-01-git-html-help.markdown b/_posts/2010-01-01-git-html-help.markdown new file mode 100644 index 0000000..c54f035 --- /dev/null +++ b/_posts/2010-01-01-git-html-help.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Installing Git HTML help +redirect_to: /install-git-html-help +--- \ No newline at end of file diff --git a/_posts/2010-01-01-git-ignore.markdown b/_posts/2010-01-01-git-ignore.markdown new file mode 100644 index 0000000..69f9847 --- /dev/null +++ b/_posts/2010-01-01-git-ignore.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Ignoring files +redirect_to: /ignore-files +--- \ No newline at end of file diff --git a/_posts/2010-01-01-leave-a-repo.markdown b/_posts/2010-01-01-leave-a-repo.markdown new file mode 100644 index 0000000..14c5484 --- /dev/null +++ b/_posts/2010-01-01-leave-a-repo.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Leave a repo +redirect_to: /leave-a-collaborative-repo +--- \ No newline at end of file diff --git a/_posts/2010-01-01-managing-clients.markdown b/_posts/2010-01-01-managing-clients.markdown new file mode 100644 index 0000000..31d8198 --- /dev/null +++ b/_posts/2010-01-01-managing-clients.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Managing multiple clients +redirect_to: /manage-multiple-clients +--- \ No newline at end of file diff --git a/_posts/2010-01-01-moving-a-repo.markdown b/_posts/2010-01-01-moving-a-repo.markdown new file mode 100644 index 0000000..c3d238a --- /dev/null +++ b/_posts/2010-01-01-moving-a-repo.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Moving a repo +redirect_to: /move-a-repo +--- \ No newline at end of file diff --git a/_posts/2010-01-01-multiple-keys.markdown b/_posts/2010-01-01-multiple-keys.markdown new file mode 100644 index 0000000..80c8651 --- /dev/null +++ b/_posts/2010-01-01-multiple-keys.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Multiple SSH keys +redirect_to: /multiple-ssh-keys +--- \ No newline at end of file diff --git a/_posts/2010-01-01-privacy.markdown b/_posts/2010-01-01-privacy.markdown new file mode 100644 index 0000000..9a9e0bd --- /dev/null +++ b/_posts/2010-01-01-privacy.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: GitHub Privacy Policy +redirect_to: /privacy-policy +--- \ No newline at end of file diff --git a/_posts/2010-01-01-pull-requests.md b/_posts/2010-01-01-pull-requests.md new file mode 100644 index 0000000..ddaedac --- /dev/null +++ b/_posts/2010-01-01-pull-requests.md @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Sending pull requests +redirect_to: /send-pull-requests +--- \ No newline at end of file diff --git a/_posts/2010-01-01-removing-sensitive-data.markdown b/_posts/2010-01-01-removing-sensitive-data.markdown new file mode 100644 index 0000000..ea4a467 --- /dev/null +++ b/_posts/2010-01-01-removing-sensitive-data.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Removing sensitive data +redirect_to: /remove-sensitive-data +--- \ No newline at end of file diff --git a/_posts/2010-01-01-splitting-a-subpath-to-a-new-repo.md b/_posts/2010-01-01-splitting-a-subpath-to-a-new-repo.md new file mode 100644 index 0000000..4b77996 --- /dev/null +++ b/_posts/2010-01-01-splitting-a-subpath-to-a-new-repo.md @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Splitting a subpath out into a new repo +redirect_to: /split-a-subpath-into-a-new-repo +--- \ No newline at end of file diff --git a/_posts/2010-01-01-svn-importing.markdown b/_posts/2010-01-01-svn-importing.markdown new file mode 100644 index 0000000..e12c5ca --- /dev/null +++ b/_posts/2010-01-01-svn-importing.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Importing from Subversion +redirect_to: /import-from-subversion +--- \ No newline at end of file diff --git a/_posts/2010-01-01-terms.markdown b/_posts/2010-01-01-terms.markdown new file mode 100644 index 0000000..9cad0fa --- /dev/null +++ b/_posts/2010-01-01-terms.markdown @@ -0,0 +1,5 @@ +--- +layout: redirect +title: GitHub Terms of Service +redirect_to: /terms-of-service +--- \ No newline at end of file diff --git a/_posts/2010-01-01-testing-webhooks.textile b/_posts/2010-01-01-testing-webhooks.textile new file mode 100644 index 0000000..bfb7892 --- /dev/null +++ b/_posts/2010-01-01-testing-webhooks.textile @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Testing webhooks +redirect_to: /test-webhooks +--- \ No newline at end of file diff --git a/_posts/2010-01-01-troubleshooting-common-issues.md b/_posts/2010-01-01-troubleshooting-common-issues.md new file mode 100644 index 0000000..3a6a9f3 --- /dev/null +++ b/_posts/2010-01-01-troubleshooting-common-issues.md @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Troubleshooting Common Issues +redirect_to: /common-issues-and-questions +--- \ No newline at end of file diff --git a/_posts/2010-01-01-troubleshooting-ssh.textile b/_posts/2010-01-01-troubleshooting-ssh.textile new file mode 100644 index 0000000..0a28143 --- /dev/null +++ b/_posts/2010-01-01-troubleshooting-ssh.textile @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Troubleshooting SSH issues +redirect_to: /ssh-issues +--- \ No newline at end of file diff --git a/_posts/2010-01-01-working-with-key-passphrases.textile b/_posts/2010-01-01-working-with-key-passphrases.textile new file mode 100644 index 0000000..52f2685 --- /dev/null +++ b/_posts/2010-01-01-working-with-key-passphrases.textile @@ -0,0 +1,5 @@ +--- +layout: redirect +title: Working with SSH key passphrases +redirect_to: /ssh-key-passphrases +--- \ No newline at end of file -- cgit v1.3.1