From 8261ac36f16915d06bd7d79a568bc0f77118dca2 Mon Sep 17 00:00:00 2001 From: David Beitey Date: Tue, 6 Feb 2018 14:06:37 +1000 Subject: [PATCH] Use HTTPS over git:// when cloning starters (#3820) `git://` (which is what `hostInfo.git(...)` gets you) uses unencrypted transport isn't recommended as a way to clone GitHub repositories (https://help.github.com/articles/which-remote-url-should-i-use/). This change uses HTTPS instead. --- packages/gatsby-cli/src/init-starter.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/gatsby-cli/src/init-starter.js b/packages/gatsby-cli/src/init-starter.js index 2bed30e3a8288..8f1d7569b00c3 100644 --- a/packages/gatsby-cli/src/init-starter.js +++ b/packages/gatsby-cli/src/init-starter.js @@ -82,7 +82,7 @@ const clone = async (hostInfo: any, rootPath: string) => { url = hostInfo.ssh({ noCommittish: true }) // Otherwise default to normal git syntax. } else { - url = hostInfo.git({ noCommittish: true }) + url = hostInfo.https({ noCommittish: true }) } const branch = hostInfo.committish ? `-b ${hostInfo.committish}` : ``