Add GitHub Actions workflow for static site deployment#7
Conversation
This workflow automates the deployment of static content to GitHub Pages on pushes to the main branch or manually via the Actions tab.
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to deploy static content from this repo to GitHub Pages, triggered on pushes to main or via manual dispatch.
Changes:
- Introduces a
static.ymlworkflow to configure GitHub Pages and deploy an uploaded artifact. - Uploads static files from
./examples/resumefor deployment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| uses: actions/upload-pages-artifact@v3 | ||
| with: | ||
| path: './examples/resume' |
There was a problem hiding this comment.
The uploaded Pages artifact points at ./examples/resume, but that directory doesn’t contain an index.html. GitHub Pages will serve index.html at the site root; without it, / will 404 (users would have to know to visit /resume.html). Consider adding an index.html (or a build/rename step to create one) in the deployed artifact so the Pages root is usable.
| environment: | ||
| name: github-pages | ||
| url: ${{ steps.deployment.outputs.page_url }} | ||
| runs-on: ubuntu-latest |
There was a problem hiding this comment.
This workflow uses runs-on: ubuntu-latest, which can change over time and introduce unexpected breakages. The repo’s CI workflow pins the runner (ubuntu-22.04); consider pinning here as well for reproducibility.
| runs-on: ubuntu-latest | |
| runs-on: ubuntu-22.04 |
This workflow automates the deployment of static content to GitHub Pages on pushes to the main branch or manually via the Actions tab.