-
It would be really helpful to have this documented prominently on your readme! And also to explain whether you need to go to https://github.com/you/repo/settings/pages to enable it or if it will Just Work once you run this Action. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Ah okay you do document
But this is kind of confusingly worded. Why would you want to use this Action if you weren't trying to use a different static site generator than jekyll? Having this enabled by default causes Github to 404 all accesses to files in folders named with leading |
Beta Was this translation helpful? Give feedback.
-
This is enabled by default because that's the default behavior of GitHub Pages when an event occurs on the gh-pages branch as you found out in https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#static-site-generators So when the action push content on your GitHub Pages branch a GitHub bot will trigger an internal workflow that will look like this: As you can see in https://github.com/crazy-max/ghaction-github-pages/runs/4773640592?check_suite_focus=true, this workflow will pull a jekyll image to build the website on that branch because there is no If you add a |
Beta Was this translation helpful? Give feedback.
This is enabled by default because that's the default behavior of GitHub Pages when an event occurs on the gh-pages branch as you found out in https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#static-site-generators
So when the action push content on your GitHub Pages branch a GitHub bot will trigger an internal workflow that will look like this:
As you can see in https://github.com/crazy-max/ghaction-github-pages/runs/4773640592?check_suite_focus=true, this workflow will pull a jekyll image to buil…