fix: configure push remote for fork PRs in claude-rebase workflow (#2583)
## Summary
- `claude-code-action` overwrites origin's fetch URL to point to the
base repo (`dyad-sh/dyad`), causing the rebase workflow to push to
upstream instead of the fork
- Added a `Configure push remote for fork PRs` step (matching
`pr-review-responder.yml`) that sets `pushurl` on origin to point to the
fork repo
- Added a learning to `rules/git-workflow.md` documenting this
`claude-code-action` behavior
## Test plan
- Apply `cc:rebase` label to a fork PR and verify the rebase pushes to
the fork, not the base repo
#skip-bugbot
🤖 Generated with [Claude Code](https://claude.com/claude-code)
<!-- devin-review-badge-begin -->
---
<a href="https://app.devin.ai/review/dyad-sh/dyad/pull/2583"
target="_blank">
<picture>
<source media="(prefers-color-scheme: dark)"
srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1">
<img
src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1"
alt="Open with Devin">
</picture>
</a>
<!-- devin-review-badge-end -->
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Ensure claude-rebase pushes to the contributor’s fork instead of the
base repo by setting a push-only remote for fork PRs. Also documents
this claude-code-action behavior in git workflow rules.
- **Bug Fixes**
- Add a “Configure push remote for fork PRs” step to claude-rebase.yml
that sets origin’s pushurl to the PR head repo using GITHUB_TOKEN, so
pushes go to the fork even if claude-code-action rewrites origin’s fetch
URL; matches pr-review-responder.yml.
<sup>Written for commit dbd6a1082657c8a162b137682e1f3c30df697e94.
Summary will update on new commits.</sup>
<!-- End of auto-generated description by cubic. -->
Co-authored-by:
Claude Opus 4.6 <noreply@anthropic.com>
正在显示
请
注册
或者
登录
后发表评论