actions / actions/starter-workflows
"pages-build-deployment" workflow is missing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
When you enable GitHub Pages on a repository and configure it to be published from a branch (instead of via GitHub Actions), it, in fact, still uses a GitHub Actions workflow to build and publish. If the (branch based) publishing source does not contain a ".nojekyll" file at the root, the files are built as a Jekyll site and published, using a workflow named "pages-build-deployment".
Under the "Actions" tab, the runs of this "pages-build-deployment" are present. However, unlike a conventional action, it is not possible to view the workflow file of this action.
I would like to learn where can I access the workflow file of this "pages-build-deployment" workflow. I assumed that it would be available in this repository, but that doesn't seem to be the case. There is a workflow named "Deploy Jekyll with GitHub Pages dependencies preinstalled" in "jekyll-gh-pages.yml" file under "pages" in this repository, but that doesn't seem to be the same with the "pages-build-deployment" workflow, since the "build" job of the "Deploy Jekyll with GitHub Pages dependencies preinstalled" workflow contains a step that runs the "configure-pages" action, whereas the "build" job of the "pages-build-deployment" workflow has no such step.
So, I would like to learn where can I access the workflow file of this "pages-build-deployment" workflow.
Best
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pages/jekyll-gh-pages.yml and compare it with the pages-build-deployment workflow described in the issue, including the configure-pages step and the build job. Determine where the workflow definition can be accessed, then document that location and explain how it differs from the repository workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, jekyll
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100