Why can't this do cross fork PR's anymore, any open source workflow ...
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Why can't this do cross fork PR's anymore, any open source workflow uses that where you create a branch in your fork (linked in the copilot app) and then you create a PR against upstream/main, often you do not even have access to create branches in the main repo so this is the only way to work, and currently I'm being gaslit that the agents are not capable of doing that, even explicitly telling it to the the gh cli! Please fix!
| Field | Value |
|---|---|
| App version | 1.1.19 |
| OS | macOS 26.6.2 |
| Theme | GitHub |
| Path | /mywork |
| Tenure | Week 4 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the workflow in the Copilot app at /mywork using app version 1.1.19 on macOS, with a branch in a fork and a target of upstream/main. Use the gh CLI as requested and compare the agent's behavior with the expected cross-fork pull request flow; done means the app can complete that workflow without requiring branch access in the upstream repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, macos
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100