From 369abbbe117f3ba1d8869279b99e9740d1917a53 Mon Sep 17 00:00:00 2001 From: ozakione <29860391+OzakIOne@users.noreply.github.com> Date: Mon, 25 Mar 2024 19:23:35 +0100 Subject: [PATCH 1/2] docs: remove old github action description --- website/docs/deployment.mdx | 5 ----- 1 file changed, 5 deletions(-) diff --git a/website/docs/deployment.mdx b/website/docs/deployment.mdx index 9048c4a4d1ae..419b1449a04a 100644 --- a/website/docs/deployment.mdx +++ b/website/docs/deployment.mdx @@ -355,11 +355,6 @@ Our goal is that: 1. When a new pull request is made to `main`, there's an action that ensures the site builds successfully, without actually deploying. This job will be called `test-deploy`. 2. When a pull request is merged to the `main` branch or someone pushes to the `main` branch directly, it will be built and deployed to GitHub Pages. This job will be called `deploy`. -Here are two approaches to deploying your docs with GitHub Actions. Based on the location of your deployment branch (`gh-pages`), choose the relevant tab below: - -- Source repo and deployment repo are the **same** repository. -- The deployment repo is a **remote** repository, different from the source. Instructions for this scenario assume [publishing source](https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) is the `gh-pages` branch. - ```mdx-code-block From 67574071b5fc7ba13b03e8380be061ff8889f24b Mon Sep 17 00:00:00 2001 From: ozakione <29860391+OzakIOne@users.noreply.github.com> Date: Thu, 4 Apr 2024 16:01:27 +0200 Subject: [PATCH 2/2] docs: review --- website/docs/deployment.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/website/docs/deployment.mdx b/website/docs/deployment.mdx index 419b1449a04a..527208a69c10 100644 --- a/website/docs/deployment.mdx +++ b/website/docs/deployment.mdx @@ -355,6 +355,11 @@ Our goal is that: 1. When a new pull request is made to `main`, there's an action that ensures the site builds successfully, without actually deploying. This job will be called `test-deploy`. 2. When a pull request is merged to the `main` branch or someone pushes to the `main` branch directly, it will be built and deployed to GitHub Pages. This job will be called `deploy`. +Here are two approaches to deploying your docs with GitHub Actions. Based on the location of your deployment repository, choose the relevant tab below: + +- Source repo and deployment repo are the **same** repository. +- The deployment repo is a **remote** repository, different from the source. Instructions for this scenario assume [publishing source](https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) is the `gh-pages` branch. + ```mdx-code-block