Skip to content

docs(#1196): add jq to sandbox image tool list in images/README.md - #1234

Merged
rh-hemartin merged 1 commit into
mainfrom
fullsend/code/issue-1196
May 21, 2026
Merged

docs(#1196): add jq to sandbox image tool list in images/README.md#1234
rh-hemartin merged 1 commit into
mainfrom
fullsend/code/issue-1196

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

PR #1151 added jq to the sandbox base image but did not update the tool list in images/README.md. Add jq alongside the existing entries so the documentation matches the installed packages.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com


Closes #1196

Post-script verification

  • Branch is not main/master (fullsend/code/issue-1196)
  • Secret scan passed (gitleaks — 7813c92add42ca3ba723cf83de489fd6a67d442a..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

PR #1151 added jq to the sandbox base image but did not update the
tool list in images/README.md. Add jq alongside the existing entries
so the documentation matches the installed packages.

Closes #1196
Closes #1153

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rh-hemartin rh-hemartin self-assigned this May 20, 2026
@github-actions

Copy link
Copy Markdown

Site preview

Preview: https://6fa4d095-site.fullsend-ai.workers.dev

Commit: 7a6a645713336d05de58d243f74d67de1ce8bbe6

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

No findings.

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label May 20, 2026
@rh-hemartin
rh-hemartin added this pull request to the merge queue May 21, 2026
Merged via the queue into main with commit f36cd93 May 21, 2026
10 checks passed
@rh-hemartin
rh-hemartin deleted the fullsend/code/issue-1196 branch May 21, 2026 14:36
ifireball pushed a commit to ifireball/fullsend that referenced this pull request May 25, 2026
When a human closes a code agent PR and re-triggers /fs-code, the
old remote branch persists. The post-code script's plain git push
fails with non-fast-forward because the new local branch diverges
from the stale remote. This caused silent failures requiring
manual intervention (e.g., PR fullsend-ai#1234 needed 3 attempts).

Changes to post-code.sh:
- Section 7a: before pushing, check if the remote branch exists
  via git ls-remote. If it does and no open PR references it,
  delete the stale remote branch so the fresh push succeeds.
- Section 7b: capture push exit code and output. On
  non-fast-forward errors, retry with --force-with-lease as a
  fallback safety net.
- Error reporting: add an ERR trap that posts a comment on the
  originating issue when the post-code script fails, including
  the exit code and a link to the workflow run. This ensures
  humans get feedback without checking workflow logs.
- Move GH_TOKEN export earlier (before section 7a) since both
  the stale branch check and error reporting need it.

Changes to post-code-test.sh:
- Add stale branch decision tests (no remote, stale with no PR,
  branch with open PR).
- Add push retry decision tests (success, non-fast-forward,
  rejected, unexpected error).
- Add error comment content tests (exit code, workflow link,
  retry hint, warning emoji).

Note: make lint could not run due to a Go toolchain permission
error in the sandbox (unrelated to these shell script changes).
The post-code-test.sh suite passes all 38 tests.

Closes fullsend-ai#1301

Signed-off-by: fullsend-code <fullsend-code@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge All reviewers approved — ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Review agent hits jq unavailability in sandbox on every run

1 participant