asciidoctor / jekyll-asciidoc-quickstart

A template project for creating AsciiDoc-based websites using Jekyll.
https://asciidoctor.github.io/jekyll-asciidoc-quickstart/
MIT License
119 stars 159 forks source link

gh-pages did not produce the corresponding file #41

Closed breeze4u closed 9 months ago

breeze4u commented 1 year ago

You need to adjust the workflow permission to read-write

mojavelinux commented 1 year ago

The website for this repository is deploying fine. See https://asciidoctor.github.io/jekyll-asciidoc-quickstart/ If you use it as a template, then it is in your repository that you may need to adjust the permissions.

breeze4u commented 1 year ago

The website for this repository is deploying fine. See https://asciidoctor.github.io/jekyll-asciidoc-quickstart/ If you use it as a template, then it is in your repository that you may need to adjust the permissions.

Thank you very much for your reply, I am very happy now because I have successfully deployed my web page, I suggest you to add workflow permission adjustment to the tutorial, hopefully it will help beginners like me to save a lot of time to deal with this problem.

mojavelinux commented 1 year ago

If you'd like to contribute an update to explain what needs to be done, I'd be happy to review and merge it.

MarkusTiede commented 1 year ago

Thanks @breeze4u for your hint - @mojavelinux; after using this as a template you need to (maybe due to changes in default behavior / values after cloning?) change the workflow permissions as following - this also helped for me:

image

mojavelinux commented 9 months ago

I think it's possible to configure this in the GitHub Actions workflow file. If anyone can verify that, I'd be glad to accept a PR to add it there.

mojavelinux commented 9 months ago

I think this is now resolved.

mojavelinux commented 9 months ago

Unfortunately, there is an additional step that is needed after creating a new repository using this template. That seems to be a limitation of GitHub's permission model. I have documented this step in the README.