Feature Request: Work across forks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
A standard open-source project workflow on Github is to fork the project, push refs to origin, then create a PR across repos from origin to upstream. At present, stack-pr seems to only support one remote for both refs and PRs. It would be very nice if stack-pr supported this workflow, albeit I don't know how it would work since the branches would not exist in upstream. I hope whatever logic Github uses to track refs between repos would support the ability to use stack PRs across forks but I am not sure it is possible.
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
No files or tests are named. Start by tracing how stack-pr selects the remote for refs and pull requests, then check GitHub's cross-fork pull request behavior and the project's current assumptions about branch locations. Done means the documented fork workflow can create and manage stacked PRs from origin to upstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100