René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Failed to create GitHub repo. Error: 422 Unprocessable Entity","articleBody":"### OS?\r\nWindows 10\r\n\r\n### Versions.\r\nangular-cli: 1.0.0-beta.25.5\r\nnode: 6.9.2\r\nos: win32 x64\r\n@angular/common: 2.4.3\r\n@angular/compiler: 2.4.3\r\n@angular/core: 2.4.3\r\n@angular/forms: 2.4.3\r\n@angular/http: 2.4.3\r\n@angular/platform-browser: 2.4.3\r\n@angular/platform-browser-dynamic: 2.4.3\r\n@angular/router: 3.4.3\r\n@angular/compiler-cli: 2.4.3\r\n\r\n\r\n### Repro steps.\r\nuse cli to create app.\r\ncreate repo on github.\r\nadd repo as remote to newly created app\r\ntry `ng github-pages:deploy`\r\nfollow instructions\r\n=\u003e error: `Failed to create GitHub repo. Error: 422 Unprocessable Entity`\r\n\r\n### The log given by the failure.\r\n\u003e Normally this include a stack trace and some more information.\r\n\r\n\r\n### Mention any other details that might be useful.\r\n\r\nIt looks like this happens because the cli attempts to create a repo itself (which already exists). Can the cli not check to see if a remote is already attached and if so just create the new branch with the deployed app?  This error is not clear and requiring users to delete their repo on github (my workaround) seems like it is not the best solution.\r\n","author":{"url":"https://github.com/goleary","@type":"Person","name":"goleary"},"datePublished":"2017-01-17T05:08:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/4061/angular-cli/issues/4061"}