You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm actually not sure if this is the right place for this issue, but here it is.
I've recently switched the pages setting of my repository to use github actions:
When I was using the "deploy from a branch" option, GitHub was automatically seeing the cname file in the docs folder (pages folder) to set up custom domain. This was useful because the file was being automatically generated based on static site generator configuration.
I have noticed this cname file is no longer useful since I switched to using actions/deploy-pages. It would be sweet if cname file just worked like before, or alternatively, if the action had an input for cname.
Just to be clear, the problem is having to enter the custom domain by hand in the github pages settings UI when using actions/deploy-pages.
The text was updated successfully, but these errors were encountered:
Because apparently a cname file in the deployment artifacts of the gh-action doesn't automatically work like it did before when deployment was done from a directory in master branch
Hi, I'm actually not sure if this is the right place for this issue, but here it is.
I've recently switched the pages setting of my repository to use github actions:
When I was using the "deploy from a branch" option, GitHub was automatically seeing the cname file in the
docs
folder (pages folder) to set up custom domain. This was useful because the file was being automatically generated based on static site generator configuration.I have noticed this cname file is no longer useful since I switched to using
actions/deploy-pages
. It would be sweet if cname file just worked like before, or alternatively, if the action had an input for cname.Just to be clear, the problem is having to enter the custom domain by hand in the github pages settings UI when using
actions/deploy-pages
.The text was updated successfully, but these errors were encountered: