jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #51904 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2024-08-05 08:32:01 -07:00
committed by GitHub
parent 5ee82204c1 ea4183cfe7
commit 2e52a72c26
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/actions/security-guides/using-secrets-in-github-actions.md
View File

@@ -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.

1
content/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites.md
View File

@@ -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.