feat: Update deployment configuration to publish from root directory …#37
Conversation
…and exclude unnecessary assets
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Pages deployment workflow to publish the site from the repository root while attempting to omit non-site files from the deployed artifact.
Changes:
- Switch GitHub Pages
publish_dirfrom./pagesto the repository root (.). - Add an
exclude_assetslist to avoid deploying selected non-site files.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| with: | ||
| github_token: ${{ secrets.GITHUB_TOKEN }} | ||
| publish_dir: ./pages No newline at end of file | ||
| publish_dir: . |
There was a problem hiding this comment.
With publish_dir: ., the GitHub Pages deployment will include the entire repository root (e.g., data/, docs/, tests/, backup/, lockfiles, etc.) except for the few patterns in exclude_assets. If the intention is to publish only the website (index.html + pages/), consider either deploying a dedicated output directory containing just the site, or expanding exclude_assets to exclude the large/non-site directories that are now being deployed.
| publish_dir: . | |
| publish_dir: ./pages |
…and exclude unnecessary assets