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
{{ message }}
Repository navigation
-F flag passes string args that could be type-coerced by gh api #43
-F owner="$OWNER" -F name="$NAME" uses -F (typed) for string GraphQL variables. gh api auto-detects types, so a repo name like "123456" would be coerced to an integer and fail the String! schema. Current repos are safe, but -f (explicit string) for owner/name and -F only for number is the safer form.
Context
This issue was automatically created from a non-blocking concern identified
during pre-push whole-codebase review. It was flagged for tracking.
Resolved. The owner/name portion was fixed in PR #47 (commit 8584ec1, switched -F → -f for String-typed GraphQL variables). The ID! variable on the minimizeComment mutation was fixed in PR #53 (commit d42d068). Both gh api graphql sites in the workflow now use -f for non-Int variables.
Activity
fix: minimize prior reviews — use last:100 and explicit-string vars
feat: doc-only fast-skip + SHA marker + prior-comment collapse (#47)
twistedmelonman commentedon Apr 18, 2026
Resolved. The owner/name portion was fixed in PR #47 (commit 8584ec1, switched
-F→-ffor String-typed GraphQL variables). TheID!variable on theminimizeCommentmutation was fixed in PR #53 (commit d42d068). Bothgh api graphqlsites in the workflow now use-ffor non-Int variables.