semantic-release / semantic-release/github
Failure to get associated PRs for forked repo
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
When running semantic-release with this plugin in a forked repo, the success step will fail because the PR doesn't exist in the repositoryUrl.
For example, given a fork of originalOrg/some-repo: orgWithFork/some-repo, the plugin will get the associated PRs for the release, but then try to fetch them from orgWithFork repo instead of the upstream originalOrg
url: 'https://api.github.com/repos/orgWithFork/some-repo/pulls/55/commits',
status: 404,
Here's the failing workflow run: https://github.com/joe-p/algokit-core/actions/runs/14618441013/job/41012357613
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the linked workflow failure in the plugin's success step and inspect the GitHub API request for associated PR commits, especially the /repos/orgWithFork/some-repo/pulls/55/commits endpoint. Done means releases from forked repositories retrieve their associated PR commits from the upstream repository without a 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- api, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100