beyondcode / beyondcode/polyscope-community
[Bug]: Pushing commit to a fork's PR goes to the wrong remote
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Platform
macOS
### Operating system version
macOS Tahoe 26.3.1 (a)
### System architecture
ARM64 (M1, M2, etc)
### PolyScope Version
0.15.0
### Bug description
If I create a workspace from a PR, and that PR belongs to an outside contributor (i.e. its from a fork), when I push a commit Polyscope/Claude will push it to my own repo's origin (with the same branch name used in the PR) rather than back to the fork's branch.
### Steps to reproduce
- Create workspace from pull request. The PR must be from a fork.
- Make a change
- Click the commit button
### Relevant log output
```shell
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the flow from workspace creation through the commit button using a pull request from a fork. Trace how the PR branch and remote are selected during the push, then verify that a commit is sent back to the fork's branch rather than the user's origin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100