Skip to content

fix(#191): remove stale REPO_DIR from harness configs#192

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/191-remove-harness-repo-dir
Open

fix(#191): remove stale REPO_DIR from harness configs#192
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/191-remove-harness-repo-dir

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Remove REPO_DIR from forge.github.runner_env in harness/code.yaml and from forge.github.env.runner in harness/fix.yaml. Since fullsend#2774 changed sandbox output extraction to a temp directory, this value pointed to a stale location. The runner (run.go) already injects the correct REPO_DIR via last-value-wins, making the harness entries redundant and confusing.

Post-scripts (post-code.sh, post-fix.sh) are unaffected: they default REPO_DIR with ${REPO_DIR:-repo} and receive the correct value from the runner injection.


Closes #191

Post-script verification

  • Branch is not main/master (agent/191-remove-harness-repo-dir)
  • Secret scan passed (gitleaks — ab29a63c40f2e235c8b1bdd8152d6083a0dddcc3..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Remove REPO_DIR from forge.github.runner_env in harness/code.yaml
and from forge.github.env.runner in harness/fix.yaml. Since
fullsend#2774 changed sandbox output extraction to a temp
directory, this value pointed to a stale location. The runner
(run.go) already injects the correct REPO_DIR via last-value-wins,
making the harness entries redundant and confusing.

Post-scripts (post-code.sh, post-fix.sh) are unaffected: they
default REPO_DIR with ${REPO_DIR:-repo} and receive the correct
value from the runner injection.

Closes #191
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner July 16, 2026 07:50

@rh-hemartin rh-hemartin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocked until fullsend-ai/fullsend#2774 gets merged.

@rh-hemartin rh-hemartin self-assigned this Jul 20, 2026
@rh-hemartin

Copy link
Copy Markdown
Member

/fs-review

@rh-hemartin
rh-hemartin dismissed their stale review July 20, 2026 11:34

Dep PR merged.

@fullsend-ai-review

fullsend-ai-review Bot commented Jul 20, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 11:35 AM UTC · Completed 11:43 AM UTC
Commit: 7d0bfa9 · View workflow run →

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium

  • [protected-path] harness/code.yaml, harness/fix.yaml — Both changed files are under the harness/ protected path. The PR is properly authorized by issue Remove REPO_DIR from harness RunnerEnv #191 and the rationale is well-explained, but human approval is always required for protected-path changes regardless of context.

@fullsend-ai-review fullsend-ai-review Bot added the requires-manual-review Review requires human judgment label Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

requires-manual-review Review requires human judgment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove REPO_DIR from harness RunnerEnv

1 participant