Cannot find fork in "Code with agent mode" from upstream
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
I know this is not the right repo for this, but talking with @davidfowl I was recommended to open it anyways and let it be moved wherever is appropriate
-----
Working on Microsoft OSS such as [winget-cli](https://github.com/microsoft/winget-cli) requires users to fork the repo, make updates in branches on their fork, then PR them back to the upstream.
When reviewing issues in the upstream / base repository, I'd like to be assign an agent to work on the issue in my fork. It seems like this should be possible using the "Code with agent mode" button and selecting which repository I want it to work in. But. . . I cannot find my fork in the list of repositories to work in. In fact, I can’t see any of my forks, only my private repos, despite being able to run agents in my fork if I navigate to the fork directly.
Contributor guide
Research direction
Start by reproducing the issue from an upstream repository with the “Code with agent mode” button, then compare the repository picker with opening the fork directly. Trace how fork repositories are discovered and selected; done means a user can choose an accessible fork from the upstream issue flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100