From 1aa82241d25ef72942f76b594105ea237eb58327 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Wed, 20 Jul 2022 15:43:25 -0700 Subject: [PATCH 01/10] First pass a documenting Pages on Actions GA --- ...lishing-source-for-your-github-pages-site.md | 10 ++-------- ...ekyll-build-errors-for-github-pages-sites.md | 17 +++-------------- data/features/build-pages-with-actions.yml | 5 +++++ data/reusables/pages/check-workflow-run.md | 10 +++------- ...es-builds-with-github-actions-public-beta.md | 5 ----- 5 files changed, 13 insertions(+), 34 deletions(-) create mode 100644 data/features/build-pages-with-actions.yml delete mode 100644 data/reusables/pages/pages-builds-with-github-actions-public-beta.md diff --git a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index bf76deca2f..66158678f6 100644 --- a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -49,17 +49,11 @@ shortTitle: Configure publishing source If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. -To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} +To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." {% endif %} diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index b76538436f..c277060f5e 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,27 +30,16 @@ shortTitle: Jekyll build errors for Pages {% endnote %} -If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. -- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. -- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion fpt %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} {% endif %} -## Viewing your repository's build failures on {% data variables.product.product_name %} - -You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. - ## Viewing Jekyll build error messages locally We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." @@ -63,7 +52,7 @@ We recommend testing your site locally, which allows you to see build error mess ## Viewing Jekyll build errors by email -{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} +{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. {% data reusables.pages.build-failure-email-server %} {% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %} diff --git a/data/features/build-pages-with-actions.yml b/data/features/build-pages-with-actions.yml new file mode 100644 index 0000000000..458017e24d --- /dev/null +++ b/data/features/build-pages-with-actions.yml @@ -0,0 +1,5 @@ +# Issue 7584 +# Building Pages sites with Actions [GA] +versions: + fpt: '*' + ghec: '*' diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index f4f66b6f9f..664639dd7f 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,8 +1,4 @@ -{% ifversion fpt %} -1. Unless your {% data variables.product.prodname_pages %} site is built from a private or internal repository and published from a branch, your site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." +{% ifversion build-pages-with-actions %} +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the amount of free minutes they are given each. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)" and "{% data variables.product.prodname_actions %} [Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)". -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %}{% endif %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/data/reusables/pages/pages-builds-with-github-actions-public-beta.md deleted file mode 100644 index 0daefdc979..0000000000 --- a/data/reusables/pages/pages-builds-with-github-actions-public-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% ifversion fpt %} - -**Note:** {% data variables.product.prodname_actions %} workflow runs for your {% data variables.product.prodname_pages %} sites are in public beta for public repositories and subject to change. {% data variables.product.prodname_actions %} workflow runs are free for public repositories. - -{% endif %} From 633622f6a34e5e81373704fd1adaac655ae73747 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Wed, 20 Jul 2022 15:55:25 -0700 Subject: [PATCH 02/10] Add billing change --- data/reusables/gated-features/environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/gated-features/environments.md b/data/reusables/gated-features/environments.md index a74a249da7..97b6b0c679 100644 --- a/data/reusables/gated-features/environments.md +++ b/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** repositories, you must use {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} +Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** and **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} From bd52f8d34ec27b4daad75f640fb48e86a12f9999 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:35:12 -0700 Subject: [PATCH 03/10] Update data/reusables/gated-features/environments.md Co-authored-by: Sarah Edwards --- data/reusables/gated-features/environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/gated-features/environments.md b/data/reusables/gated-features/environments.md index 97b6b0c679..87a40b9ed1 100644 --- a/data/reusables/gated-features/environments.md +++ b/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** and **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} +Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} From 6e841736cebe80c39a11063bbc5df991092947ac Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:37:07 -0700 Subject: [PATCH 04/10] Update content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md Co-authored-by: Sarah Edwards --- .../about-jekyll-build-errors-for-github-pages-sites.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index c277060f5e..962299c2ed 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,7 +30,13 @@ shortTitle: Jekyll build errors for Pages {% endnote %} +{% ifversion build-pages-with-actions %} If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. +{% else %} +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. +- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. +- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +{% endif %} For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." From 7039d016db7544ec15fd8b380407825af6f83f40 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:39:05 -0700 Subject: [PATCH 05/10] Update data/reusables/pages/check-workflow-run.md Co-authored-by: Sarah Edwards --- data/reusables/pages/check-workflow-run.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index 664639dd7f..4b44fa889c 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,4 +1,10 @@ {% ifversion build-pages-with-actions %} -1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the amount of free minutes they are given each. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)" and "{% data variables.product.prodname_actions %} [Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)". +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". + +{% note %} + +{% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". + +{% endnote %} {% endif %} \ No newline at end of file From ca7820cab6eb86119b3f2ba2ca995d1aaad22471 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:39:44 -0700 Subject: [PATCH 06/10] Update content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md Co-authored-by: Sarah Edwards --- .../about-jekyll-build-errors-for-github-pages-sites.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index 962299c2ed..741830eda9 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -40,7 +40,7 @@ If Jekyll does attempt to build your site and encounters an error, you will rece For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." From 570fcb71a5fc284a6cb651d3d7ffbdad89140695 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:47:51 -0700 Subject: [PATCH 07/10] Gate some content instead of removing it completly --- .../about-jekyll-build-errors-for-github-pages-sites.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index 741830eda9..9e84172aa2 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -46,6 +46,12 @@ For more information about troubleshooting build errors, see "[Troubleshooting J By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." {% endif %} +{% ifversion build-pages-with-actions %}{% else %} +## Viewing your repository's build failures on {% data variables.product.product_name %} + +You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. +{% endif %} + ## Viewing Jekyll build error messages locally We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." From 2edca69c0ebaae10b680d4d378d7cff687186e99 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 17:22:41 -0700 Subject: [PATCH 08/10] More billing changes --- .../using-environments-for-deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index a51cc186df..2e7850abd1 100644 --- a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ You can configure environments with protection rules and secrets. When a workflo **Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. -Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %} +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% endnote %} {% endif %} @@ -74,7 +74,7 @@ Secrets stored in an environment are only available to workflow jobs that refere {% ifversion fpt or ghec %} {% note %} -**Note:** To create an environment in a private repository, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +**Note:** Creation of an environment in a private repository is available to organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %}. {% endnote %} {% endif %} From 2089b25821d48ad9d23967370cbd6c10bd090379 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Fri, 22 Jul 2022 09:30:44 -0700 Subject: [PATCH 09/10] Update content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md Co-authored-by: Sarah Edwards --- .../using-environments-for-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index 2e7850abd1..68c4e5b4e5 100644 --- a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ You can configure environments with protection rules and secrets. When a workflo **Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. -Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% endnote %} {% endif %} From 76a6d67dfe7d6994976c32af197c2cb4b952ca67 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Fri, 22 Jul 2022 09:36:32 -0700 Subject: [PATCH 10/10] Fix indentation --- data/reusables/pages/check-workflow-run.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index 4b44fa889c..1af0012c40 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,10 +1,10 @@ {% ifversion build-pages-with-actions %} 1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -{% note %} + {% note %} -{% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". + **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". -{% endnote %} + {% endnote %} {% endif %} \ No newline at end of file