test issue

[host6]

test issue

[augmentcode]

🤖 Augment PR Summary

Summary: This PR refactors how qs dev gathers repository metadata and adds a small git-status edge case handling.

Changes:

• Introduces gitcmds.RepoContext and a new LoadRepoContext() helper intended to gather key repo state up front (branch info, upstream presence, uncommitted changes, parent repo).
• Refactors parent-repo detection by extracting the GitHub API call into getParentRepoByOrgRepo() and reusing it from GetParentRepoName().
• Updates qs dev to use the preloaded context values instead of issuing repeated git/gh queries inline.
• Extends git status parsing to handle the AD status by skipping those entries.
• Bumps Go toolchain version and updates several module dependencies.
• Adds a benchmark that measures git ls-remote performance in the current repo.

Technical Notes: The intent appears to be fewer round-trips and better responsiveness by parallelizing independent git calls and deferring the single GitHub API call until org/repo are known.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 3 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

In non-fork repositories, gh api ... --jq .parent.full_name may yield null, which would be returned as a non-empty string and could incorrectly trigger fork/upstream behavior (e.g., treating parent repo as "null"). Consider normalizing a missing parent (null) to an empty value before returning.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

Porcelain status AD typically means “added to index, deleted in working tree”; the file can still be staged and included in the next commit. Skipping it here may cause staged additions (including large files) to bypass whatever checks rely on getListOfChangedFiles().

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

return string(out[:len(out)-1]) assumes the output ends with exactly one \n; on Windows (\r\n) this can leave a trailing \r in the path and break cmd.Dir. A whitespace-based trim would be more robust.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}