From dfd390e789a4f6dc77d74eed5d867c2876849149 Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Tue, 26 May 2020 22:10:30 +0300 Subject: [PATCH 1/7] Close #24479 --- docs/docs/how-gatsby-works-with-github-pages.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index e6dc627d52bd0..447dedc703f1f 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -61,6 +61,12 @@ When you run `npm run deploy` all contents of the `public` folder will be moved ### Deploying to a GitHub Pages subdomain at github.io For a repository named like `username.github.io`, you don't need to specify `pathPrefix` and your website needs to be pushed to the `master` branch. +>:warning: Keep in mind that Github Pages forces deployment of user\organization pages to master branch. So if you use master branch for development you need to do one of this: +>- change the default branch from master to something else, and use master just as site deployment directory: +> 1) to create new branch called `source` run this command: +>`git checkout -b source master` +> 2) change default branch in repository settings ("Branches" menu item) from master to source +>- have separate repository for your source code (so .github.io is used only for deployment and not really for tracking your source code) ```json:title=package.json { From 69824f23909c8c7adab6e6c6fff0354f58213a40 Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Wed, 27 May 2020 08:32:16 +0300 Subject: [PATCH 2/7] chore: format --- docs/docs/how-gatsby-works-with-github-pages.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index 447dedc703f1f..90ccf90b2e0b8 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -61,12 +61,14 @@ When you run `npm run deploy` all contents of the `public` folder will be moved ### Deploying to a GitHub Pages subdomain at github.io For a repository named like `username.github.io`, you don't need to specify `pathPrefix` and your website needs to be pushed to the `master` branch. ->:warning: Keep in mind that Github Pages forces deployment of user\organization pages to master branch. So if you use master branch for development you need to do one of this: ->- change the default branch from master to something else, and use master just as site deployment directory: -> 1) to create new branch called `source` run this command: ->`git checkout -b source master` -> 2) change default branch in repository settings ("Branches" menu item) from master to source ->- have separate repository for your source code (so .github.io is used only for deployment and not really for tracking your source code) + +> :warning: Keep in mind that Github Pages forces deployment of user\organization pages to master branch. So if you use master branch for development you need to do one of this: +> +> - change the default branch from master to something else, and use master just as site deployment directory: +> 1. to create new branch called `source` run this command: +> `git checkout -b source master` +> 2. change default branch in repository settings ("Branches" menu item) from master to source +> - have separate repository for your source code (so .github.io is used only for deployment and not really for tracking your source code) ```json:title=package.json { From ea88196fce6d68f65f131aa27e7ef4118e81cd6e Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Sat, 6 Jun 2020 08:08:53 +0300 Subject: [PATCH 3/7] Update docs/docs/how-gatsby-works-with-github-pages.md Co-authored-by: Marcy Sutton --- docs/docs/how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index 90ccf90b2e0b8..d8e10169bbf68 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -62,7 +62,7 @@ When you run `npm run deploy` all contents of the `public` folder will be moved For a repository named like `username.github.io`, you don't need to specify `pathPrefix` and your website needs to be pushed to the `master` branch. -> :warning: Keep in mind that Github Pages forces deployment of user\organization pages to master branch. So if you use master branch for development you need to do one of this: +> :warning: Keep in mind that GitHub Pages forces deployment of user/organization pages to the `master` branch. So if you use `master` for development you need to do one of these: > > - change the default branch from master to something else, and use master just as site deployment directory: > 1. to create new branch called `source` run this command: From d3feea0c8adbc71662896d15ec8eb928041ab9aa Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Sat, 6 Jun 2020 08:10:01 +0300 Subject: [PATCH 4/7] Update docs/docs/how-gatsby-works-with-github-pages.md Co-authored-by: Marcy Sutton --- docs/docs/how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index d8e10169bbf68..d8a86c7ddda3b 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -64,7 +64,7 @@ For a repository named like `username.github.io`, you don't need to specify `pat > :warning: Keep in mind that GitHub Pages forces deployment of user/organization pages to the `master` branch. So if you use `master` for development you need to do one of these: > -> - change the default branch from master to something else, and use master just as site deployment directory: +> - Change the default branch from `master` to something else, and use `master` as a site deployment directory only: > 1. to create new branch called `source` run this command: > `git checkout -b source master` > 2. change default branch in repository settings ("Branches" menu item) from master to source From f96d783b2db09634c5d0ef92d0c64fb328ac39bf Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Sat, 6 Jun 2020 08:10:42 +0300 Subject: [PATCH 5/7] Update docs/docs/how-gatsby-works-with-github-pages.md Co-authored-by: Marcy Sutton --- docs/docs/how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index d8a86c7ddda3b..6ab6d1329903d 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -65,7 +65,7 @@ For a repository named like `username.github.io`, you don't need to specify `pat > :warning: Keep in mind that GitHub Pages forces deployment of user/organization pages to the `master` branch. So if you use `master` for development you need to do one of these: > > - Change the default branch from `master` to something else, and use `master` as a site deployment directory only: -> 1. to create new branch called `source` run this command: +> 1. To create a new branch called `source` run this command: > `git checkout -b source master` > 2. change default branch in repository settings ("Branches" menu item) from master to source > - have separate repository for your source code (so .github.io is used only for deployment and not really for tracking your source code) From 93cfd417cf1d6d069a1f42a68167b73393cb4b0d Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Sat, 6 Jun 2020 08:11:22 +0300 Subject: [PATCH 6/7] Update docs/docs/how-gatsby-works-with-github-pages.md Co-authored-by: Marcy Sutton --- docs/docs/how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index 6ab6d1329903d..3c5ce8a6adb01 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -67,7 +67,7 @@ For a repository named like `username.github.io`, you don't need to specify `pat > - Change the default branch from `master` to something else, and use `master` as a site deployment directory only: > 1. To create a new branch called `source` run this command: > `git checkout -b source master` -> 2. change default branch in repository settings ("Branches" menu item) from master to source +> 2. Change the default branch in your repository settings ("Branches" menu item) from `master` to `source` > - have separate repository for your source code (so .github.io is used only for deployment and not really for tracking your source code) ```json:title=package.json From c8e3f4c2705c50a1ec3fffdbd1e61ef56deffd1c Mon Sep 17 00:00:00 2001 From: ILdar Nogmanov Date: Sat, 6 Jun 2020 08:11:49 +0300 Subject: [PATCH 7/7] Update docs/docs/how-gatsby-works-with-github-pages.md Co-authored-by: Marcy Sutton --- docs/docs/how-gatsby-works-with-github-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-gatsby-works-with-github-pages.md b/docs/docs/how-gatsby-works-with-github-pages.md index 3c5ce8a6adb01..17cf7b2a435bf 100644 --- a/docs/docs/how-gatsby-works-with-github-pages.md +++ b/docs/docs/how-gatsby-works-with-github-pages.md @@ -68,7 +68,7 @@ For a repository named like `username.github.io`, you don't need to specify `pat > 1. To create a new branch called `source` run this command: > `git checkout -b source master` > 2. Change the default branch in your repository settings ("Branches" menu item) from `master` to `source` -> - have separate repository for your source code (so .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) ```json:title=package.json {