[Bug]: Pushing commit to a fork's PR goes to the wrong remote

Open
#116 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
git, github
Domain
developer-experience, tooling

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.

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
Dominant language
No language data
Stars
20
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beyondcode/polyscope-community

All issues in beyondcode/polyscope-community

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.