Repository navigation
я почему-то поулчаю такую ошибку и не отрабатывается план #417
Description
[8:05:52] ~/~/app (pr-5)> git push
Everything up-to-date
[post-push-pr] Open PR: https://github.com/ProverCoderAI/effect-ts-skills/pull/7
import: scanned 5 file(s), matched 5 current repo/branch file(s), found 1 plan(s), added 0, skipped 1 duplicate(s), skipped 0 rendered stack(s), parse errors 0
import: scanned 197 file(s), matched 0 current repo/branch file(s), found 0 plan(s), added 0, skipped 0 duplicate(s), skipped 0 rendered stack(s), parse errors 0
[plan-to-git] Syncing queued agent plans to PR #7
plan-to-git error: gh api PR comment failed: gh: Not Found (HTTP 404)
[8:17:40] ~/~/app (pr-5)>
Activity
skulidropek commentedon Jun 17, 2026
Root cause looks like a repo/PR context mismatch in the post-push plan sync path.
In my workspace
post-pushfirst found the open PR correctly:Then
/opt/docker-git/hooks/plan-to-git-syncpassed only the PR number to the binary:plan-to-git sync --pr "$pr_number"plan-to-gitresolves the target repo fromgit remote get-url origin. In this checkoutoriginwas the fork:but PR
#7exists in the base repo:So the comment API call effectively went to the fork repo issue endpoint for
#7, where that PR/issue does not exist, which explains the GitHub404 Not Found.Local fix that removed the error: wrap the
plan-to-git import-*and sync calls inpost-pushwith a scoped Git URL rewrite so only that subprocess seesoriginas the base repo (upstreamwhen present), without changing.git/configor the realoriginremote.Shape of the fix:
I applied this around the whole
plan-to-gitblock in/opt/docker-git/hooks/post-push:plan-to-git import-codex --no-syncplan-to-git import-claude --no-sync/opt/docker-git/hooks/plan-to-git-syncplan-to-git syncAfter that,
git pushcompleted with exit code 0 and no longer printedgh api PR comment failed: gh: Not Found (HTTP 404). The actual remote config stayed unchanged:Caveat: this fixes the post-push path. If
plan-to-git-syncis also invoked directly from live agent hooks, the same scoped rewrite may need to live inplan-to-git-syncitself orplan-to-gitshould accept an explicit--repo <owner/repo>together with--pr.konard commentedon Jun 17, 2026
🚨 Solution Draft Failed
The automated solution draft encountered an error:
What you can do
--allow-fork-divergence-resolution-using-force-push-with-leaseto allow a guarded force-with-lease sync.Administrator-only CLI details, if any, are printed in the solver terminal log rather than in this GitHub comment.
🤖 Models used:
opusclaude-opus-4-8)Click to expand failure log (43KB)
Now working session is ended, feel free to review and add any feedback on the solution draft.