feat(ci): reapply of capybara pages deployment and fix issues#1049
Merged
feat(ci): reapply of capybara pages deployment and fix issues#1049
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the linux-eic-shell GitHub Actions workflow to (re-)enable publishing Capybara report artifacts into the GitHub Pages site, including collecting artifacts from open PRs and main.
Changes:
- Renames/standardizes the merged Capybara artifact to
capybaraand adds jobs to collect Capybara artifacts from open PRs and frommain. - Adjusts the GitHub Pages build job to merge “staging” artifacts into the Jekyll
_site/output before uploading the Pages artifact. - Extends the deploy job to post/update a “Capybara summary” PR comment (and modifies job permissions accordingly).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
wdconinc
commented
Feb 26, 2026
d422667 to
db46568
Compare
3dfb8ca to
6c7673e
Compare
Contributor
Capybara summary for PR 1049
|
wdconinc
commented
Apr 22, 2026
wdconinc
commented
Apr 22, 2026
Reverts 6821c01 (re-applies a604499) with the following fixes: - Fix matrix.head_sha reference in get-docs-from-main (no matrix in that job): use 'branch: main' to download from the main branch - Fix download path in build-artifacts-page: download github-pages-staging to _site/ (after jekyll build) instead of artifacts/ (from PR #859) - Use if-no-files-found: ignore for get-docs-from-main upload to handle case where main branch has no capybara artifact yet - Update action versions to match current workflow (dawidd6 v15, upload-artifact v6, download-artifact v7, upload-pages-artifact v4) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
for more information, see https://pre-commit.ci
When no capybara artifact exists on main yet (e.g. first run), the get-docs-from-main job previously uploaded nothing (if-no-files-found: ignore), leaving zero github-pages-staging-* artifacts for the merge step in build-artifacts-page to find, causing it to fail with 'No artifacts found matching pattern'. Add a step to always create publishing_docs/.keep so the upload never has zero files, and change if-no-files-found to error so any future regression is caught immediately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- add continue-on-error: true to deploy-pages step so capybara PR
comments are still posted even when GitHub Pages environment
protection blocks deployment from PR branches
- guard 'find _site/pr/{n}/capybara/' against missing directory
(e.g. when npsim has not yet produced reports)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- jekyll-build-pages@v1 runs as root, making _site/ unwritable; add sudo chown step after Jekyll build to restore runner ownership - fix 'List content to publish' run: scalar (was parsed as YAML mapping due to indented value on next line) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
e8ec4c6 to
48b6a5e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Briefly, what does this PR introduce?
Reverts 6821c01 (re-applies a604499) with the following fixes:
matrix.head_shareference inget-docs-from-main(no matrix in that job), and use 'branch: main' to download from the main branchbuild-artifacts-page: copygithub-pages-staging-*artifacts from already-downloadedartifacts/into_site/after Jekyll build, avoiding unreliable parallel multi-artifact downloadsif-no-files-found: ignoreforget-docs-from-mainupload to handle case where main branch has no capybara artifact yetcontinue-on-error: trueto deploy-pages step so PR comments are still posted even if GitHub Pages environment protection blocks deployment from PR branchesfindagainst missing directory when npsim has not yet produced reportsWhat kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No.