GitHub install fails when GitHub remote is not named 'origin'

[Waridley]

Bug Description

The GitHub install command only looks at the "origin" remote to find the repository. This fails when using a different remote name (e.g., "upstream", "github", etc.).

Expected Behavior

The command should parse all remotes and find the first valid GitHub remote URL.

Steps to Reproduce

1. Add a GitHub remote with a name other than "origin" (e.g., git remote add github https://github.com/user/repo.git)
2. Run the GitHub install command
3. It fails with "Could not find git repository"

Suggested Fix

Parse all remotes using git remote -v and find the first valid GitHub remote URL.

Labels: bug

[github-actions]

This issue might be a duplicate of an existing issue. Please check:

• [BUG] opencode github install - "Could not find git repository" in valid git repo #7787: Same command (opencode github install) fails with "Could not find git repository" in a valid git repository — your issue identifies the root cause (remote not named 'origin'), which may be the same underlying bug.

If your issue is indeed the same, please add any additional context there. If it's distinct, feel free to clarify the difference.