Repository navigation
INTER-2535: ci: deploy docs and coverage via shared Pages workflow - #286
Conversation
The shared docs-and-coverage workflow publishes by pushing a commit to the gh-pages branch with JamesIves/github-pages-deploy-action. That commit is unsigned, so the repository ruleset requiring verified signatures on gh-pages rejects the push and the job fails. Replace the reusable workflow call with a local job that runs the same build, docs, coverage and badge steps, then publishes through the official Pages pipeline (configure-pages, upload-pages-artifact, deploy-pages). This uploads an artifact instead of pushing a branch commit, so the signature rule no longer applies. Requires the repository Pages source to be set to "GitHub Actions". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVQ7VL2PnxZcxTU4AZt43h
|
Coverage report
Test suite run success130 tests passing in 30 suites. Report generated by 🧪jest coverage report action from 015ff88 Show full coverage report
|
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved blocking issues were identified.
Pull request overview
Replaces branch-based docs and coverage publishing with GitHub Pages artifact deployment.
Changes:
- Runs build, docs, coverage, and badge generation locally.
- Uploads and deploys the assembled site via GitHub Pages.
- Adds required permissions, environment, and concurrency settings.
File summaries
| File | Description |
|---|---|
.github/workflows/coverage-report.yml |
Implements the docs, coverage, and GitHub Pages deployment pipeline. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
pnpm exec changesetto create a changeset. |
docs-and-coverage.yml@v1Pages artifact pipelineRequired repository setting
Set Settings → Pages → Build and deployment → Source to GitHub Actions before merging. After the first successful deployment, the unused
gh-pagesbranch can be removed.