Skip to content

COEP HTTP - works with CORS and CORP - but separately #59391

COEP HTTP - works with CORS and CORP - but separately

COEP HTTP - works with CORS and CORP - but separately #59391

name: Check Redirects
on:
pull_request:
branches:
- main
jobs:
check-redirects:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js environment
uses: actions/setup-node@v4
with:
node-version-file: ".nvmrc"
cache: yarn
# This is a "required" workflow so path filtering can not be used:
# https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks#handling-skipped-but-required-checks
# We have to rely on a custom filtering mechanism to run the checks only if required files are modified.
- uses: dorny/paths-filter@v3
name: See if any file needs checking
id: filter
with:
filters: |
required_files:
- ".nvmrc"
- "files/**"
- ".github/workflows/pr-check_redirects.yml"
- name: Install all yarn packages
if: steps.filter.outputs.required_files == 'true'
run: yarn --frozen-lockfile
env:
# https://github.com/microsoft/vscode-ripgrep#github-api-limit-note
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Check redirects file(s)
if: steps.filter.outputs.required_files == 'true'
run: yarn content validate-redirects en-us --strict