Repository navigation
[Sync to prerelease] Run the weekly axe scan on prerelease too - #2274
Merged
Merged
Conversation
Move the scan into a reusable axe-scan.yml and call it from a two-leg matrix in axe-report.yml: main publishes to quarto.org, prerelease to prerelease.quarto.org with the prerelease-docs profile. (cherry picked from commit 81a83c7)
Member
|
/deploy-preview |
Contributor
Author
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-2274.quarto.org |
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
2 participants
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.
Description
Sync of #2265 to
prerelease.Original PR
Run the weekly axe scan on prerelease too
Follow-up to #2259. The weekly axe scan now also scans
prereleaseand publishes its report on prerelease.quarto.org. Themainscan does not change.axe-scan.yml(new) contains the old scan and publish jobs as a reusable workflow. It has the inputsbranch,site, andprerelease. Forprerelease, it renders with theprerelease-docsprofile, the same aspublish.yml.axe-report.ymlis now a two-leg matrix that callsaxe-scan.ymlonce formainand once forprerelease. Each leg has its own concurrency group and artifact, so the two legs run in parallel./release-mergeskill now has a note: a release merge conflicts on_axe-report.md. Keep themainversion, then run the workflow manually.Each leg commits
_axe-report.mddirectly to its branch. These bot pushes do not make backport PRs.Test run: https://github.com/quarto-dev/quarto-web/actions/runs/37054502660