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
In GitHub Pages, the default deployment takes place from the root directory of the main branch, but it's also possible to specify the docs directory for deployment:
However, this creates an issue with paths. When deploying from docs, the generated URLs for files like index.html still reference the root directory rather than accounting for the docs folder. For example, instead of the file being accessible via http://example.com/docs/index.html, GitHub Pages expects it at http://example.com/index.html, even though it's located in the docs folder.
This mismatch breaks the paths. It would be useful if this GitHub Action could allow specifying a prefix to adjust for this, so that the URLs reflect the actual directory structure or ignore the docs prefix when serving files. Ideally, adding support for such prefixes could help resolve this issue and make future deployments smoother. Or it might be better to use relative paths instead of absolute paths in GitHub Pages to avoid issues like this in the future.
The text was updated successfully, but these errors were encountered:
In GitHub Pages, the default deployment takes place from the root directory of the main branch, but it's also possible to specify the docs directory for deployment:
However, this creates an issue with paths. When deploying from docs, the generated URLs for files like index.html still reference the root directory rather than accounting for the docs folder. For example, instead of the file being accessible via http://example.com/docs/index.html, GitHub Pages expects it at http://example.com/index.html, even though it's located in the docs folder.
This mismatch breaks the paths. It would be useful if this GitHub Action could allow specifying a prefix to adjust for this, so that the URLs reflect the actual directory structure or ignore the docs prefix when serving files. Ideally, adding support for such prefixes could help resolve this issue and make future deployments smoother. Or it might be better to use relative paths instead of absolute paths in GitHub Pages to avoid issues like this in the future.
The text was updated successfully, but these errors were encountered: