Correct AGENTIC_REPO semantics in the dotnet recipe docs#109
Merged
Conversation
Discovered during the live end-to-end validation (issue #4 in .scratch/dotnet-afk-support/): AGENTIC_REPO only scopes gh API calls (issues/PRs) — it does not redirect git push, which always uses the orchestrator process's own cwd checkout (main.ts: repoRoot = process.cwd()). The original docs implied you could run from agentic-dev's own checkout while AGENTIC_REPO pointed at an unrelated external repo; following them literally would push branches to the wrong repo. Corrected to state the orchestrator must be launched with cwd inside the target project's own checkout, with a tested command for doing so directly via tsx.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
AGENTIC_REPOonly scopesghAPI calls (issues/PRs) — it does not redirectgit push, which always runs with the orchestrator process's own cwd checkout (main.ts:590,repoRoot = process.cwd();main.ts:1095,git push -u origin ...withcwd: repoRoot).examples/dotnet-project/docs I wrote in PR Package dotnet Dockerfile recipe as examples/dotnet-project/ #107 implied you could run the orchestrator fromagentic-dev's own checkout whileAGENTIC_REPOpointed at an unrelated external repo. Following that literally would push a branch to the wrong repo..scratch/dotnet-afk-support/) — I had to launchtsxdirectly with cwd inside the target repo's own checkout to make it work at all.README.mdandorchestrator.env's comments to state the real constraint, with the tested working command.Test plan