# `.wordpress-org/` — WordPress.org plugin assets

Drop image files in this directory and the `.github/workflows/wporg-assets.yml`
workflow will push them to the SVN `assets/` directory on WordPress.org the
next time `main` is updated. None of these files are bundled inside the
plugin zip itself — they only exist in the WP.org SVN `assets/` tree, which
controls what shows up on the plugin's directory listing page.

## Required / recommended filenames

The 10up/action-wordpress-plugin-asset-update action picks files up by exact
name. Add any of these as needed:

### Plugin icon (shown on the directory listing + the plugin row in wp-admin)

- `icon-128x128.png` (or `.jpg`)
- `icon-256x256.png` (or `.jpg`) — retina; recommended
- `icon.svg` — optional vector icon (preferred if you have one)

### Plugin banner (shown on the directory page header)

- `banner-772x250.png` (or `.jpg`) — standard
- `banner-1544x500.png` (or `.jpg`) — retina; recommended

### Screenshots (matched against the `== Screenshots ==` section of `readme.txt`)

- `screenshot-1.png` (or `.jpg`)
- `screenshot-2.png`
- … numbered sequentially, matching captions in `readme.txt`

A `screenshot-N` file with no matching caption in `readme.txt` won't render
on the listing page. Likewise, a caption without a matching file shows a
broken-image placeholder.

## Updating

1. Replace any of the files above
2. Commit + push to `main`
3. The `wporg-assets.yml` workflow pushes the change to WP.org SVN

The action is idempotent: a no-op when the existing SVN copy matches the
repo state.

## Notes

- The directory itself is excluded from the plugin zip via `.distignore` at
  the repo root, so the icons / banners never ship inside the install.
- The asset workflow uses the same `WPORG_SVN_USERNAME` / `WPORG_SVN_PASSWORD`
  secrets as `wporg-deploy.yml`.