-
Notifications
You must be signed in to change notification settings - Fork 58.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update troubleshooting-404-errors-for-github-pages-sites.md #33683
base: main
Are you sure you want to change the base?
Conversation
Added troubleshooting for Github Page with private repository of an expired GitHub Pro, GitHub Team, GitHub Enterprise Cloud,or GitHub Enterprise Server user.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ���️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
@Yuchen-Song Thanks so much for opening a PR! I'll get this triaged for review ✨ |
...pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites.md
Show resolved
Hide resolved
@@ -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. | |||
* Check if your GitHub Pro, GitHub Team, GitHub Enterprise Cloud, or GitHub Enterprise Server access has expired if you are using a private repository for the Github Page Site. If so, please make sure to renew it or change your repository's visibility to public. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For product names and brands there are variables to be used:
* Check if your GitHub Pro, GitHub Team, GitHub Enterprise Cloud, or GitHub Enterprise Server access has expired if you are using a private repository for the Github Page Site. If so, please make sure to renew it or change your repository's visibility to public. | |
* Check if your {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, or {% data variables.product.prodname_ghe_server %} subscription is still active if you are using a private repository for the {% data variables.product.prodname_pages %} site. Otherwise please make sure to renew it or change your repository's visibility to public. |
(I've also slightly reformatted the condition wording.)
Why: Added troubleshooting for Github Page 404 error with private repository of an expired GitHub Pro, GitHub Team, GitHub Enterprise Cloud,or GitHub Enterprise Server user.
Closes: https://github.com/orgs/community/discussions/36070
What's being changed (if available, include any code snippets, screenshots, or gifs): Added one line in the doc
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.