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
Update Fullsend and the pinned agent harnesses to v0.55.0. Add custom code and fix harnesses that enable GitHub-signed commits, and migrate the issue-target allowlist to the current configuration schema.
Update Fullsend workflow refs and pinned agent harnesses to v0.55.0. Enable GitHub-signed commits for the code and fix agents, and migrate the issue-target allowlist to the current configuration schema.
Co-authored-by: Codex <noreply@openai.com>
No actionable comments were generated in the recent review.
Walkthrough
The change adds code and fix harnesses, updates harness base references and repository target settings, and changes the reusable workflow commit used by the dispatch and prioritize jobs.
Changes: Harness configuration
Layer / File(s)
Summary
Add harnesses and update base references .fullsend/customized/harness/code.yaml, .fullsend/customized/harness/fix.yaml, .fullsend/customized/harness/review.yaml, .fullsend/customized/harness/retro.yaml
Adds code and fix harness configurations with GitHub signed-commit overlays. Updates the base references for review and retro.
Register harnesses and update repository targets .fullsend/config.yaml
Adds code and fix to the agents list. Moves the repository allowlist to tracker.github.allowed_targets.repos without changing its entries.
This PR updates Fullsend pins, enables GitHub-signed commits for the code and fix agents, and migrates the target allowlist to the current schema. The caller and callee contracts checked in earlier inspections are compatible, and no concrete merge-blocking risk remains.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly identifies the Fullsend version update, which is the main change in the pull request.
Description check
The description explains the update, signed-commit harness changes, configuration migration, and linked ticket. It omits the template headings but includes the required information.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (7 skipped: 7 unsupported.)
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: b59f9594-f11f-462e-8133-c1bd7280c9c5
Commits
Reviewing files that changed from the base of the PR and between 3bc55d6 and f332719.
Files selected for processing: 7
.fullsend/config.yaml
.fullsend/customized/harness/code.yaml
.fullsend/customized/harness/fix.yaml
.fullsend/customized/harness/retro.yaml
.fullsend/customized/harness/review.yaml
.github/workflows/fullsend.yaml
.github/workflows/prioritize.yml
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
A routine Fullsend version bump to v0.55.0 touching only configuration YAML files; protected-path count (2) and CI workflow modification each push individual signals high, but very low recent churn (1 commit/30d) and no security-sensitive changes keep the weighted composite moderate.
[protected-path].github/workflows/fullsend.yaml, .github/workflows/prioritize.yml — PR modifies files under protected paths (.github/). These are governance/infrastructure files that require human approval. The PR provides sufficient justification (linked to EC-2390, description explains version upgrade to v0.55.0), but human approval is always required for protected-path changes regardless of context.
Labels: PR modifies GitHub Actions workflow files and CI/agent configuration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fullsend-ai-review
Bot
added
requires-manual-review
Update Fullsend and the pinned agent harnesses to v0.55.0. Add custom code and fix harnesses that enable GitHub-signed commits, and migrate the issue-target allowlist to the current configuration schema.
Resolves: EC-2390