Repository navigation
[Bug]: Pushing commit to a fork's PR goes to the wrong remote #116
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
Activity
Merdin commentedon Jun 26, 2026
I have a similar issue.
Platform
macOS
Operating system version
macOS Tahoe 26.5.1 (25F80)
System architecture
ARM64 (M1, M2, etc)
PolyScope Version
0.22.2 (0.22.2)
Bug description
When I create a new workspace from a specified branch, it does not push to the remote branch that I selected.
Steps to reproduce
Relevant log output
Merdin commentedon Jun 26, 2026
Maybe we should be able to add protected branches in the
polyscope.jsonor polyscope settings, so it never accidentally pushes to them. In that case we can always manually decide if we want to push to a specific branch.I put some rules in the project settings about not pushing to mentioned branches without permission in the app but it ignores them.