Improve the app's workflow for forked repositories
Open
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Forked projects need support for choosing the upstream base, creating worktrees from the latest upstream commit, pushing branches to the fork, and opening pull requests against the upstream repository instead of assuming origin is always the source and target
Contributor guide
Research direction
Start by mapping the app's repository and pull-request workflow for forked repositories; the issue does not name files, tests, or entry points. Done means users can choose an upstream base, create worktrees from the latest upstream commit, push branches to the fork, and open pull requests against the upstream repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- desktop, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100