Skip to content

docs: refresh Perform AGENTS workflow guidance #130

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
mehul0810 merged 2 commits into from
Jun 17, 2026
+9 −2
Merged

docs: refresh Perform AGENTS workflow guidance #130

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b5a5a8d
docs: refresh AGENTS branch guidance
mehul0810 Jun 15, 2026
c33669e
docs: add Perform release cadence guidance
mehul0810 Jun 16, 2026
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
11 changes: 9 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,20 @@ Guidance for AI coding agents working on the Perform WordPress plugin.

## Project Snapshot
- Plugin: `Perform`
- Current public line: `1.5.1`
- Active release branch in this workspace: `release/1.6.0`
- Stack:
- PHP (WordPress plugin, PSR-4 autoload `Perform\\` -> `src/`)
- JS/CSS via `@wordpress/scripts` + webpack output in `assets/dist`
- Freemius SDK via Composer

## Branch And Release Workflow
- `develop` is the default integration branch for workflow-policy and documentation changes unless current release evidence proves a different base.
- Release-scoped work uses `release/<milestone>` branches. Verify the live branch list each run instead of hardcoding a single active release branch here.
- If an issue or milestone maps to an existing `release/<milestone>` branch, create the work branch from that release branch and set the PR base explicitly.
- Verify the current public version and release line from live repo metadata such as `readme.txt`, GitHub releases, and WordPress.org signals rather than relying on a static value in this file.
- Release-readiness checks are project-specific: evaluate minor releases on a 30-day cadence and patch releases on a 7-day cadence within the same minor line.
- Treat `x.9.x` as the pre-major rollover boundary: if that line is exhausted, the next planned release target should become `(x+1).0.0`.
- At cadence checkpoints, verify the active milestone due date and latest public release live, then flag owner approval when a patch or minor candidate is justified by security, regression, compatibility, packaging, or high-impact stability/performance needs.

## Non-Negotiable Compatibility Rules
- Do not rename existing option/meta keys used by released versions.
- Preserve backward compatibility with legacy settings sections:
Expand Down
Loading