A filter path segment ending in [] resolves to the list of every element's
value, so a task can run only when, say, an issue carries a given label:
{path: 'body.issue.labels[].name', op: 'equals', value: 'needs more info'}.
equals, in and startsWith match when any element does, notEquals only when
none equals the value, exists when the list is not empty. Placeholders
accept the same syntax and render the list.
Before this, filters could only compare scalars and arrays satisfied
exists alone, so a GitHub issue_comment hook had to wake the bound thread
on every comment in the repository and let the agent discard the rest.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>Julius Marminge committed on 10/22/2026, 1:40:54 AMparent49e97d4
Checks
- SuccessfulCodeRabbitGitHub
Review skipped
- Skipped
- Skipped
- Skipped
- SuccessfulRemove preview downloadGitHub
- FailedCheckGitHub
- Skipped
- SkippedRustGitHub
- FailedTestGitHub
- SuccessfulTest WebGitHub
- SuccessfulRelease SmokeGitHub
- FailedBuild and TypecheckGitHub
- Skipped
- SuccessfulLabel PR sizeGitHub
- SuccessfulLabel PR 23282GitHub
- Skipped
- Successful
- Skipped
- SuccessfulTest Server 8GitHub
- SuccessfulChangesGitHub
- SuccessfulTest Server 1GitHub
- SuccessfulTest Server 6GitHub
- FailedTest Server 3GitHub
- SuccessfulTest Server 4GitHub
- SuccessfulTest Server 5GitHub
- FailedTest Server 2GitHub
- FailedTest Server 7GitHub
- FailedLintGitHub
- SkippedEAS PreviewGitHub
- SuccessfulCollect PR targetsGitHub
- SuccessfulPrepare PR size configGitHub
- SuccessfulNative fingerprint diffGitHub
6 files changedLine totals unavailable