Skip to content

fix: fall back to SWIFTLM_PR_TOKEN for PR creation, matching the sibling sync - #60

Merged
solderzzc merged 1 commit into
mainfrom
fix/upstream-sync-pr-creation-token
Aug 16, 2026
Merged

fix: fall back to SWIFTLM_PR_TOKEN for PR creation, matching the sibling sync#60
solderzzc merged 1 commit into
mainfrom
fix/upstream-sync-pr-creation-token

Conversation

@solderzzc

Copy link
Copy Markdown
Member

Summary

The push-rejection bug (#59) is fixed and verified end-to-end via a real `workflow_dispatch` run — it pushed `sync/upstream-latest` successfully. But the very next step in that same run still failed:

```
pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest)
```

Fix

Bare `GITHUB_TOKEN` can't create the PR here, even with `pull-requests: write` declared. The sibling `mlx-swift/upstream-sync.yml` already falls back to `secrets.SWIFTLM_PR_TOKEN` for its equivalent step and has created PRs successfully on every run — that secret is configured on both repos, this workflow just never used it. Applies the identical fallback.

Test plan

  • After merge, trigger `workflow_dispatch` and confirm a PR actually opens (not just "PR already exists or no changes" from the fallback echo).

…ing sync

The push-rejection bug is fixed and verified (workflow_dispatch run
31958854896 pushed the sync branch successfully), but the PR-creation
step still failed on that same run:

  pull request create failed: GraphQL: Resource not accessible by
  integration (createPullRequest)

Bare GITHUB_TOKEN can't create the PR here even with pull-requests:
write declared. mlx-swift/upstream-sync.yml already falls back to
secrets.SWIFTLM_PR_TOKEN for its equivalent step — that secret is
configured on both repos — and has created PRs successfully on every
run. This applies the identical fallback.
@solderzzc
solderzzc merged commit 8995a7b into main Aug 16, 2026
6 checks passed
@solderzzc
solderzzc deleted the fix/upstream-sync-pr-creation-token branch August 16, 2026 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant