-
Notifications
You must be signed in to change notification settings - Fork 59.8k
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 instructions in [Configuring a subdomain] help article #2184
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@peterjuma Thanks for opening an issue! I'll get this triaged for the right team to take a look 👀 |
Hi, can I take this issue? |
This comment has been minimized.
This comment has been minimized.
You're welcome to open a PR @Yuliadocs 💖 |
Hi @Yuliadocs - I'm just checking through issues and found the timeline on this one really confusing. None of the various pull requests listed in the issue history above are relevant. This issue is still available to work on. |
Clarify that users should create a CNAME in repo settings, rather than creating it directly. This PR closes github#2184.
What article on docs.github.com is affected?
https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain
What part(s) of the article would you like to see updated?
Current:
It should probably be changed to something like:
Additional information
Users should NOT create the CNAME file themselves, this is done automatically once they update their custom domain settings with the domain name and hence the need for this change.
If we can get the wording that would explicitly convey to users that they should NOT create the CNAME file, that will be even better
CC for visibility
@github/support-technical
@github/business-support-all
The text was updated successfully, but these errors were encountered: