You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/integrations/SKILL.md
+87-64Lines changed: 87 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,32 @@ All integrations live in the `integration/` directory.
14
14
15
15
**File naming:**`class-{plugin-name}.php` (following PHP conventions in AGENTS.md)
16
16
17
-
### Available Integrations
18
-
- BuddyPress
19
-
- bbPress
20
-
- WooCommerce
21
-
- Jetpack
22
-
- The Events Calendar
23
-
- WP User Avatars
24
-
- And 13+ more
17
+
**Namespace:**`Activitypub\Integration`
18
+
19
+
### How Integrations Load
20
+
Integrations are wired up in `integration/load.php` inside `plugin_init()`. Each one is guarded by a detection check and then calls its class's static `init()`:
21
+
22
+
```php
23
+
// integration/load.php
24
+
if ( \defined( 'JETPACK__VERSION' ) ) {
25
+
Jetpack::init();
26
+
}
27
+
```
28
+
29
+
### Existing Integrations
30
+
The real integrations shipped today (see `integration/`):
The enabled post types are stored in the `activitypub_support_post_types` option (read with `\get_option( 'activitypub_support_post_types', array( 'post' ) )`).
104
+
67
105
### Custom Transformers
68
106
107
+
The `activitypub_transformer` filter takes **three** arguments — `( $transformer, $data, $object_class )` — and is registered with priority `10, 3`:
108
+
69
109
```php
70
-
public static function transformer( $transformer, $object ) {
71
-
if ( 'custom_type' === get_post_type( $object ) ) {
Copy file name to clipboardExpand all lines: .claude/agents/bug-bounty.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,26 +10,23 @@ You are a bug-fix agent for the WordPress ActivityPub plugin. Your job is to pic
10
10
11
11
## Step 1 — Find an Issue to Fix
12
12
13
-
Fetch open bug issues from the repository. **Only consider issues labeled "Bug" or "[Type] Bug"** — skip everything else:
13
+
Fetch open bug issues from the repository. **Only consider issues labeled "Bug"** — skip everything else:
14
14
15
15
```bash
16
16
gh issue list --label "Bug" --state open --json number,title,body,labels --limit 20
17
-
gh issue list --label "[Type] Bug" --state open --json number,title,body,labels --limit 20
18
17
```
19
18
20
-
Merge and deduplicate the results.
21
-
22
19
From the results, **skip issues that also have the "Needs triage" label** — these are unverified and waiting for manual review.
23
20
24
21
Review the remaining issues and pick the one that is most straightforward to fix — look for clear reproduction steps, well-described expected behavior, and a scope that can be addressed with minimal changes.
25
22
26
-
**Skip issues that already have a linked PR.** For each candidate issue, check:
23
+
**Skip issues that already have a linked PR.** For each candidate issue, check for referencing PRs:
27
24
28
25
```bash
29
-
gh pr list --state open --search "#<number>" --json number,title
26
+
gh search prs --repo Automattic/wordpress-activitypub --state open "Fixes #<number> OR Closes #<number> OR #<number>"
30
27
```
31
28
32
-
If any open PR already references the issue, move on to the next candidate.
29
+
You can also see linked PRs directly in `gh issue view <number>` (the development/timeline section). If any open PR already references the issue, move on to the next candidate.
Copy file name to clipboardExpand all lines: .claude/agents/patch-release.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,9 +95,9 @@ git log --oneline -3
95
95
96
96
Follow the **release** skill's patch release process:
97
97
98
-
1. Run `composer changelog:write` — usethe patch version when prompted.
98
+
1. Run `composer changelog:write -- --use-version=<patch-version> --no-interaction` to force the patch version non-interactively (it otherwise derives the version from change-file significance and may prompt).
99
99
2. Copy new entries from `CHANGELOG.md` into the `== Changelog ==` section of `readme.txt`.
100
-
3. Update version numbers in all version file locations (per the release skill).
100
+
3. Update version numbers in all version file locations (per the release skill). In `activitypub.php` this means **both** the `Version:` header **and** the `ACTIVITYPUB_PLUGIN_VERSION` constant, plus `includes/class-migration.php`.
101
101
4. Replace any `unreleased` annotations in cherry-picked files with the patch version.
0 commit comments