Skip to content

Fix e2e tests for WordPress 6.7 #7350

Fix e2e tests for WordPress 6.7

Fix e2e tests for WordPress 6.7 #7350

# This workflow removes any assets created for manual QA testing
# from the GCP bucket once a pull request is closed.
name: Clean up PR assets
on:
pull_request:
types: [closed]
permissions:
contents: read
jobs:
remove-pr:
name: Cleanup storage
runs-on: ubuntu-latest
timeout-minutes: 5
if: >
github.event.pull_request.draft == false &&
github.event.pull_request.head.repo.fork == false &&
github.event.pull_request.user.login != 'dependabot[bot]'
steps:
- name: Harden Runner
uses: step-security/harden-runner@91182cccc01eb5e619899d80e4e971d6181294a7
with:
disable-file-monitoring: true
disable-sudo: true
egress-policy: block
allowed-endpoints: >
cloudresourcemanager.googleapis.com:443
dl.google.com:443
oauth2.googleapis.com:443
storage.googleapis.com:443
raw.githubusercontent.com:443
- name: Authenticate
uses: google-github-actions/auth@6fc4af4b145ae7821d527454aa9bd537d1f2dc5f
with:
credentials_json: ${{ secrets.GCP_SA_KEY }}
- name: Setup Cloud SDK
uses: google-github-actions/setup-gcloud@6189d56e4096ee891640bb02ac264be376592d6a
with:
project_id: ${{ secrets.GCP_PROJECT_ID }}
- name: Prune PR files
run: gsutil rm -rf gs://web-stories-wp-github-artifacts/refs/pull/${{ github.event.pull_request.number }}