-
-
Notifications
You must be signed in to change notification settings - Fork 396
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
support: The URL of the GitHub pages changes on its own #846
Comments
It looks like a feature of the GitHub Enterprise Cloud. (called We can configure a custom domain to access a constant domain pattern. |
Hi!
According to this article. Should I post it on actions/deploy-pages@v1 GitHub issue? |
yes.
It is a specification of the GitHub Pages on the GitHub Enterprise Cloud. Currently, we have no way to deploy our site to an URL that never will be changed on a private Enterprise Cloud repository except to configure a custom domain. (I am also using the GitHub Pages on the GitHub Enterprise Cloud and use a URL like If we have our custom domain, the GitHub Pages support CNAME files so we can put a CNAME file or set our domain as follows with this action. https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-add-cname-file-cname
The above previous discussions may help you. And we can request new features to GitHub at community/community. Of course, the actions/deploy-pages repository is also a good place to ask about that, I think. |
According to the thread, actually, we can access a static URL |
Thank you so much! I tried this https://<ORG_NAME>.github.io/<REPO_NAME> then it worked. But changing the URL is not cool... I gonna post about URLs on the GitHub community. Again thank you so much. |
Checklist
Describe your question
When I deploy a private static website in a private repository using GithubAction, the URL sometimes changes.
Is this a specification of this GitHubActions? (Or is it a GitHub Pages specification?) .
I would like to know why the URL sometimes changes and how to prevent the URL from changing.
Relevant links
Relevant log output
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered: