support.github.com => github.com/contact

4 files changed, 5 insertions, 5 deletions

diff --git a/_posts/2008-01-06-move-a-repo.markdown b/_posts/2008-01-06-move-a-repo.markdown
index c95d3f6..14d94f3 100644
--- a/_posts/2008-01-06-move-a-repo.markdown
+++ b/_posts/2008-01-06-move-a-repo.markdown
@@ -10,7 +10,7 @@ This guide details the process of moving a repo to another account.
 Direct move
 -----------
 
-If you wish to move a repo between users or organizations, please [contact support](http://support.github.com/) following the details below.
+If you wish to move a repo between users or organizations, please [contact support](https://github.com/contact) following the details below.
 
 **What to check before creating the support request**
 
@@ -43,7 +43,7 @@ If you wish to move a repo between users or organizations, please [contact suppo
 Existing forks
 --------------
 
-If a fork of the repo you wish to move already exists on the target account, you can [contact support](http://support.github.com/) to have the roots switched.  Note that deleting the root repo will either delete all forks if the repo is private, or automatically pick a new root if the repo is public.  You cannot pick which repo will become the root, so please contact support if you want a specific repo to become the new root.
+If a fork of the repo you wish to move already exists on the target account, you can [contact support](https://github.com/contact) to have the roots switched.  Note that deleting the root repo will either delete all forks if the repo is private, or automatically pick a new root if the repo is public.  You cannot pick which repo will become the root, so please contact support if you want a specific repo to become the new root.
 
 Note that if the repo is private the new owner will need a paid plan to support the repo.  Issues, wikis, pages, commits comments and non-repo downloads **will not** be transferred to the new root.  Make sure you do not delete your old repo if you have any of these you wish to keep.
 
diff --git a/_posts/2008-03-03-remove-sensitive-data.markdown b/_posts/2008-03-03-remove-sensitive-data.markdown
index 8f7b9f3..c0c8535 100644
--- a/_posts/2008-03-03-remove-sensitive-data.markdown
+++ b/_posts/2008-03-03-remove-sensitive-data.markdown
@@ -106,7 +106,7 @@ You may have collaborators that pulled your tainted branch and created their own
 Cached data on GitHub
 ---------------------
 
-Be warned that force-pushing does not erase commits on the remote repo, it simply introduces new ones and moves the branch pointer to point to them.  If you are worried about users accessing the bad commits directly via SHA1, you will have to delete the repo and recreate it.  If the commits were viewed online the pages may also be cached.  Check for cached pages after you recreate the repo, if you find any open a ticket on [GitHub Support](http://support.github.com) and provide links so staff can purge them from the cache.
+Be warned that force-pushing does not erase commits on the remote repo, it simply introduces new ones and moves the branch pointer to point to them.  If you are worried about users accessing the bad commits directly via SHA1, you will have to delete the repo and recreate it.  If the commits were viewed online the pages may also be cached.  Check for cached pages after you recreate the repo, if you find any open a ticket on [GitHub Support](https://github.com/contact) and provide links so staff can purge them from the cache.
 
 Avoiding accidental commits in the future
 -----------------------------------------
diff --git a/_posts/2008-04-04-fix-egit-corruption.markdown b/_posts/2008-04-04-fix-egit-corruption.markdown
index 1c3a6fc..ae93eb9 100644
--- a/_posts/2008-04-04-fix-egit-corruption.markdown
+++ b/_posts/2008-04-04-fix-egit-corruption.markdown
@@ -49,7 +49,7 @@ remote: Total 1815 (delta 1139), reused 1552 (delta 961)
 Receiving objects: 100% (1815/1815), 537.69 KiB | 549 KiB/s, done.
 Resolving deltas: 100% (1139/1139), done.</pre>
 
-If you have re-pushed all branches in your repo and cloning still fails, please [contact support](http://support.github.com) and open a ticket.  Be sure to include a link to your repo and mention that you've already performed the steps on this page.
+If you have re-pushed all branches in your repo and cloning still fails, please [contact support](https://github.com/contact) and open a ticket.  Be sure to include a link to your repo and mention that you've already performed the steps on this page.
 
 Avoiding future corruption
 --------------------------
diff --git a/_posts/2008-06-02-github-support.md b/_posts/2008-06-02-github-support.md
index c9c62a4..e348e61 100644
--- a/_posts/2008-06-02-github-support.md
+++ b/_posts/2008-06-02-github-support.md
@@ -3,5 +3,5 @@ layout: redirect
 title: GitHub Support
 description: Resolve issues with GitHub or get help with basic git issues.
 categories: github_resources
-redirect_to: http://support.github.com/
+redirect_to: https://github.com/contact
 ---
\ No newline at end of file