refactor(@angular/cli): removed the github pages deploy command

BREAKING CHANGE: This command is being removed from the core of the CLI
There are several options for deploying CLI-based applications outside the scope of this project.
One of which being https://github.com/angular-buch/angular-cli-ghpages
This functionality is likely to return in the form of an addon/plugin in the future

README.md

@@ -45,7 +45,6 @@ with NPM 3 or higher.
 * [Running Unit Tests](#running-unit-tests)
 * [Running End-to-End Tests](#running-end-to-end-tests)
 * [Proxy To Backend](#proxy-to-backend)
-* [Deploying the App via GitHub Pages](#deploying-the-app-via-github-pages)
 * [Linting code](#linting-code)
 * [Commands autocompletion](#commands-autocompletion)
 * [Project assets](#project-assets)
@@ -237,37 +236,6 @@ and then we edit the `package.json` file's start script to be
 
 now run it with `npm start`
 
-### Deploying the app via GitHub Pages
-
-You can deploy your apps quickly via:
-
-```bash
-ng github-pages:deploy --message "Optional commit message"
-```
-
-This will do the following:
-
-- creates GitHub repo for the current project if one doesn't exist
-- rebuilds the app in production mode at the current `HEAD`
-- creates a local `gh-pages` branch if one doesn't exist
-- moves your app to the `gh-pages` branch and creates a commit
-- edit the base tag in index.html to support GitHub Pages
-- pushes the `gh-pages` branch to GitHub
-- returns back to the original `HEAD`
-
-Creating the repo requires a token from GitHub, and the remaining functionality
-relies on ssh authentication for all git operations that communicate with github.com.
-To simplify the authentication, be sure to [setup your ssh keys](https://help.github.com/articles/generating-ssh-keys/).
-
-If you are deploying a [user or organization page](https://help.github.com/articles/user-organization-and-project-pages/), you can instead use the following command:
-
-```bash
-ng github-pages:deploy --user-page --message "Optional commit message"
-```
-
-This command pushes the app to the `master` branch on the GitHub repo instead
-of pushing to `gh-pages`, since user and organization pages require this.
-
 
 ### Linting code
 

packages/@angular/cli/addon/index.js

@@ -32,7 +32,6 @@ module.exports = {
       'version': require('../commands/version').default,
       'completion': require('../commands/completion').default,
       'doc': require('../commands/doc').default,
-      'github-pages-deploy': require('../commands/github-pages-deploy').default,
 
       // Easter eggs.
       'make-this-awesome': require('../commands/easter-egg').default,

packages/@angular/cli/blueprints/ng2/files/README.md

@@ -22,10 +22,6 @@ Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.
 Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
 Before running the tests make sure you are serving the app via `ng serve`.
 
-## Deploying to GitHub Pages
-
-Run `ng github-pages:deploy` to deploy to GitHub Pages.
-
 ## Further help
 
 To get more help on the `angular-cli` use `ng help` or go check out the [Angular-CLI README](https://github.com/angular/angular-cli/blob/master/README.md).