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
Two critical bugs combine to silently lose the agent's work without any error surfacing, plus one enhancement gap that limits the agent's ability to resolve issues.
Bug 1 — No git identity configured (critical)
The workflow never configures git config user.email / user.name. When commit_and_push in scripts/dev-lead-fix-reviews.sh calls git commit, git rejects it:
fatal: empty ident name (for <runner@...>) not allowed
commit_and_push is called as the condition of an if statement:
if commit_and_push "human";then
post_reviews_terminal "human""applied""Changes committed and pushed."
In bash with set -euo pipefail, set -e is suspended for the entire function body when the function is the condition of an if. So git commit fails, execution continues to git push (exits 0 with "Everything up-to-date"), the function returns 0, and the PR gets a false "Changes committed and pushed" comment. The agent's fixes are silently lost.
Bug 3 — WebFetch not in run_writer allowed tools (enhancement)
engine.sh's run_writer uses --allowed-tools "Bash,Read,Write,Edit,Grep,Glob" — no WebFetch. When the agent needed to verify a SHA256 hash from GitHub releases, it could not and noted: "This could not be safely fixed without internet access to verify the correct hash." Adding WebFetch allows the agent to look up release hashes, SonarCloud rule docs, etc.
Root cause timeline (run 26071797185)
Agent ran for ~6 minutes, made file edits (NOSONAR suppressions, trailing newlines)
commit_and_push "human" was called
git commit failed — no git identity on runner
set -e suspended (function called from if) → git push ran → "Everything up-to-date"
post_reviews_terminal "human" "applied" "Changes committed and pushed." fired falsely
The symptom this issue fixed has recurred behind a different root cause — filed as #1567.
#281's Bug 2 was post_reviews_terminal "human" "applied" "Changes committed and pushed." firing falsely, traced to a missing git identity plus set -e being suspended when commit_and_push ran as an if condition. That mechanism is fixed and explicitly guarded in current main.
On 2026-08-21 (PR .github#995) the same false claim appeared three times, most starkly for a commit that changed one cross-reference (§4 → §3, +1/−1) while reporting "Changes committed and pushed" against a review requesting eight substantive changes. #1567 argues the guard should move from "did the commit succeed" to "did the requested change land".
Activity
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
7 remaining items
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
fix(dev-lead): configure git identity, surface commit/push failures, …
don-petry commentedon Aug 21, 2026
The symptom this issue fixed has recurred behind a different root cause — filed as #1567.
#281's Bug 2 was
post_reviews_terminal "human" "applied" "Changes committed and pushed."firing falsely, traced to a missing git identity plusset -ebeing suspended whencommit_and_pushran as anifcondition. That mechanism is fixed and explicitly guarded in currentmain.On 2026-08-21 (PR .github#995) the same false claim appeared three times, most starkly for a commit that changed one cross-reference (
§4→§3, +1/−1) while reporting "Changes committed and pushed" against a review requesting eight substantive changes. #1567 argues the guard should move from "did the commit succeed" to "did the requested change land".