Deploys to test without waiting for Lighthouse
Test exists to try things out, so it now deploys as soon as the check job passes; Lighthouse runs alongside and its reports are information. Production still waits for both check and Lighthouse, so accessibility, best-practices and SEO problems never go live. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -157,8 +157,10 @@ jobs:
|
||||
path: web/lighthouse-reports/
|
||||
retention-days: 14
|
||||
|
||||
# Test wacht niet op Lighthouse: test is om te testen, de rapporten zie je
|
||||
# achteraf. Lighthouse draait ernaast.
|
||||
deploy-test:
|
||||
needs: [check, lighthouse]
|
||||
needs: check
|
||||
if: (github.event_name == 'workflow_dispatch' && github.event.inputs.deploy_test == 'true') || (github.event_name == 'push' && github.ref == 'refs/heads/master')
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
@@ -206,6 +208,8 @@ jobs:
|
||||
curl -fsSI "$HEALTH_URL" | grep -qi '^content-security-policy:'
|
||||
echo "Test bereikbaar met security headers"
|
||||
|
||||
# Productie wacht wel op Lighthouse: toegankelijkheid, Best Practices en SEO
|
||||
# moeten slagen voordat er iets live gaat.
|
||||
deploy-production:
|
||||
needs: [check, lighthouse]
|
||||
# Alleen handmatig, en alleen vanaf een release-branch
|
||||
|
||||
Reference in New Issue
Block a user