From 7e97a75688854e4fc0bf898c69e101df076589aa Mon Sep 17 00:00:00 2001 From: Kevin Pham Date: Sun, 13 Mar 2022 00:36:42 +1100 Subject: [PATCH 1/2] docs(gh-pages): improve separate repository instructions --- .../how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md b/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md index 2f692d1f09b8f..6fad58fef01ff 100644 --- a/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md @@ -69,7 +69,7 @@ For a repository named like `username.github.io`, you don't need to specify `pat > `git checkout -b source main` > 2. Change the default branch in your repository settings ("Branches" menu item) from `main` to `source` > - **Note**: GitHub Pages lets you use any branch for deployment, see [this docs page](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source) on how to do this. This means you do not necessarily have to change your default branch. -> - Have a separate repository for your source code (so `username.github.io` is used only for deployment and not really for tracking your source code) +> - Have a separate repository for your source code (so `username.github.io` is used only for deployment and not really for tracking your source code). If going down this route, you will need to add extra option for `--repo ` (works for https and git urls) in the gh-pages command below. ```json:title=package.json { From 19c05152a8112cf1c7202ac307b9599732f4c9db Mon Sep 17 00:00:00 2001 From: Ty Hopp Date: Mon, 14 Mar 2022 11:38:57 +0800 Subject: [PATCH 2/2] Adjust sentence slightly --- .../how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md b/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md index 6fad58fef01ff..6f4b4797ba109 100644 --- a/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-to/previews-deploys-hosting/how-gatsby-works-with-github-pages.md @@ -69,7 +69,7 @@ For a repository named like `username.github.io`, you don't need to specify `pat > `git checkout -b source main` > 2. Change the default branch in your repository settings ("Branches" menu item) from `main` to `source` > - **Note**: GitHub Pages lets you use any branch for deployment, see [this docs page](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source) on how to do this. This means you do not necessarily have to change your default branch. -> - Have a separate repository for your source code (so `username.github.io` is used only for deployment and not really for tracking your source code). If going down this route, you will need to add extra option for `--repo ` (works for https and git urls) in the gh-pages command below. +> - Have a separate repository for your source code (so `username.github.io` is used only for deployment and not really for tracking your source code). If you go down this route, you will need to add an extra option for `--repo ` (works for https and git urls) in the gh-pages command below. ```json:title=package.json {