From c91ae39e9a3867adbef6b339f808e02af1b229d8 Mon Sep 17 00:00:00 2001 From: Yuchen Song <103324298+Yuchen-Song@users.noreply.github.com> Date: Mon, 5 Aug 2024 07:55:22 -0700 Subject: [PATCH 1/2] Update troubleshooting-404-errors-for-github-pages-sites.md (#33683) Co-authored-by: Tommy Byrd Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> --- .../troubleshooting-404-errors-for-github-pages-sites.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites.md b/content/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites.md index 3222c033fe..f603c25750 100644 --- a/content/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites.md +++ b/content/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites.md @@ -69,5 +69,6 @@ Check whether your repository meets the following requirements. * The branch you are using to publish your site must be the `main` or default branch. * The repository must have a commit pushed to it by someone with admin permissions for the repository, such as the repository owner. * Switching the repository's visibility from public to private or vice versa will change the URL of your {% data variables.product.prodname_pages %} site, which will result in broken links until the site is rebuilt. +* If you are using a private repository for the {% data variables.product.prodname_pages %} site, please check if your {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} subscription is still active. If you renew the plan, the {% data variables.product.prodname_pages %} site will be automatically re-deployed. Otherwise, you can change your repository's visibility to public to continue using {% data variables.product.prodname_pages %} for free. If you are still receiving a 404 error, start a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/pages) in the Pages category. From ea4183cfe76c4175fdef351146488c6793318d45 Mon Sep 17 00:00:00 2001 From: Pooya Parsa Date: Mon, 5 Aug 2024 18:49:06 +0330 Subject: [PATCH 2/2] docs: remove unnecessary `"` (#34190) Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> --- .../actions/security-guides/using-secrets-in-github-actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/security-guides/using-secrets-in-github-actions.md b/content/actions/security-guides/using-secrets-in-github-actions.md index a7dceb814a..513fc9b910 100644 --- a/content/actions/security-guides/using-secrets-in-github-actions.md +++ b/content/actions/security-guides/using-secrets-in-github-actions.md @@ -195,7 +195,7 @@ gh secret set --org ORG_NAME SECRET_NAME --visibility all To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag. ```shell -gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2" +gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2 ``` To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.