No artifact

[cavallofurioso]

When try to publish website via github pages, reployment returnes these errors

deployError: No uploaded artifact was found!
deployEnvironment URL '' is not a valid http(s) URL, so it will not be shown as a link in the workflow graph.

[tajmone]

In your repository, GHPages needs to be configured to serve the website from the docs/ folder in master branch.

The build script in the repository is handled via a Bash script (docs_src/build.sh) that simply converts the final document into an HTML file in the docs/ folder: docs/index.html.

Since it's a static website, you'll also need to add a .nojekyll file in the GHPages root directory (in this repository, docs/.nojekyll) so that GHPages will disable Jekyll for the website (i.e. not wait for Markdown source files).

From the errors you mention, I get the impression you're using GitHub Actions to publish the website. If that's the case, you'll need to ensure that the above settings are correctly in place in your repository, or that you adapt them accordingly (e.g. if serving from the gh-pages branch, etc.), and that your GH Action also works accordingly, for a static website.

I can't really comment much on the errors you've mentioned, since I don't known the context were you've encountered — but it doesn't look like they are from a verbatim fork of this repository.

In any case, whether you're building the HTML book from AsciiDoc, or publishing the ready-converted file elsewhere, GHPages should have no problems handling a static HTML website, as long as you include an empty .nojekyll file in the website root. If you're not building the document from the AsciiDoc source, you shouldn't need any GitHub Actions either, just configure your repository how to serve the GHPages website (the default gh-pages branch, a custom branch, or the docs/ folder from main) and simply copy the converted document, renamed as index.html (unless you have a navigation menu and other pages) and you should be good to go.

Was any of this helpful?