ci(ua-blocker): restrict PR creation to only upstream repository #1533
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
.github/workflows/ci-ua-blocker-sync.yml, thepeter-evans/create-pull-requestaction specifies reviewers. However, in forked repositories, reviewers are not collaborators, causing the action to fail.Since this workflow is triggered by a cron schedule, failure notifications are sent periodically. To address this, PR creation has been restricted to only the upstream repository.
Additional note: Even in the upstream repository, the specified reviewers are not collaborators, which appears to cause the same error1. Removing the
reviewersfield altogether could also be considered.It seems that in the initial PRs, reviewers were assigned correctly2, so perhaps there has been a change in the GitHub API specification?
Footnotes
https://github.com/honojs/middleware/actions/runs/18796556639/job/53637301727 ↩
https://github.com/honojs/middleware/pull/1229 ↩