文件操作 - CONTRIBUTING.md

文件: /storage/v12552/creatormedianetwork/public_html/wp-content/plugins/embedpress-pro/CONTRIBUTING.md

编辑文件内容

# Contributing to EmbedPress Pro

Read [CLAUDE.md](CLAUDE.md) first — it captures the architecture and the cardinal rule (**Pro never forks free-plugin code**). This file covers the workflow.

## Branching

- Default branch is **`master`** (NOT `main`).
- Branch from `master`: `fix/fbs-<cardId>-<slug>` for a FluentBoards card, or `feat/<slug>` / `fix/<slug>` otherwise.
- Create the FluentBoards card **before** branching so the branch name references it.
- Never commit or push to `master` directly; open a PR.

## Making changes

1. Implement on your branch. If the change needs a new free-plugin hook, land that hook in the free repo first — do not fork free code into Pro.
2. If you touched Gutenberg block sources, rebuild: `cd Gutenberg && npm run build`. Commit the `Gutenberg/dist/` output (it ships in the distributed zip).
3. If you changed a block's `save()` output, add a `deprecated[]` entry or use conditional emission so old posts keep rendering (see CLAUDE.md).
4. If you added/changed user-facing strings, run `npm run pot`.
5. Verify locally against a WordPress install with the free plugin active (Sandbox or `embedpress-docker`).

## Pull requests

- Keep PRs scoped to one card/feature.
- CI must pass: PHP syntax matrix (7.4–8.5), version-consistency check, WP×PHP compatibility, and Plugin Check.
- Describe what changed and link the FluentBoards card.

## Releasing

Semantic Versioning (`MAJOR.MINOR.PATCH`). Prefer the `/embedpress-pro-release` skill, which automates the version bumps and changelog. Manual steps:

1. Bump the version in **all three** places (the CI version-consistency job enforces they match):
   - `embedpress-pro.php` header `Version:`
   - `package.json` `version`
   - `readme.txt` `Stable tag`
2. Update `readme.txt` changelog.
3. Regenerate `languages/embedpress-pro.pot` (`npm run pot`) if strings changed.
4. Commit, then push a `vX.Y.Z` tag.
5. `.github/workflows/deploy.yml` builds the dist zip and attaches it to a GitHub Release.
6. EDD/store pickup of the release asset is a manual downstream step (until automated).

Do not tag or push a release without explicit sign-off.

## Code standards

- PHP: WordPress Coding Standards; keep files syntax-clean on PHP 7.4 through 8.5 (CI enforces the whole matrix).
- Prefix everything (functions, options, transients, hooks) to avoid collisions.
- Never edit `vendor/` or bundled `includes/Dependencies/` — patch from plugin code or send an upstream PR.

文件操作 - CONTRIBUTING.md

文件: /storage/v12552/creatormedianetwork/public_html/wp-content/plugins/embedpress-pro/CONTRIBUTING.md

编辑文件内容

修改文件时间

删除文件