Skip to content

Run WordPress Plugin Check in CI #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
josephfusco merged 1 commit into from
Jun 10, 2026
Merged

Run WordPress Plugin Check in CI #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 3 additions & 13 deletions .github/workflows/plugin-check.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,20 +40,10 @@ jobs:

- run: npm install -g @wordpress/env@11.7.0

# Authenticate composer's GitHub API calls. Without this, wp-env's
# Docker build hits the 60/hour unauthenticated rate limit on
# `api.github.com/repos/.../zipball/...` and 504s while pulling
# the Sebastian Bergmann package tree. Writing the auth file at
# `~/.composer/auth.json` raises the limit to 5000/hour using the
# workflow's GITHUB_TOKEN.
# Avoids the intermittent 504s on api.github.com during wp-env's
# Docker build (PR #22). Authenticated requests dodge the issue.
- name: Authenticate composer to GitHub
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
mkdir -p ~/.composer
cat > ~/.composer/auth.json <<JSON
{ "github-oauth": { "github.com": "${GH_TOKEN}" } }
JSON
run: composer config --global --auth github-oauth.github.com '${{ secrets.GITHUB_TOKEN }}'

# Build the plugin tree the same way `release.yml` does so
# plugin-check sees only what would actually ship — `.distignore`
Expand Down
Loading