OpenAPITools / OpenAPITools/openapi-generator-pip
Configure CI for PR from forked repo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 8
- Avg merge
- 5h 51m
- Merged PRs (30d)
- 3
Description
Ref: #55
This PR is from a fork. GitHub restricts the GITHUB_TOKEN to read-only
for fork PRs triggered by thepull_requestevent.To fix this, use the
pull_request_targetevent instead:on: pull_request_target: types: [opened, synchronize, reopened] permissions: contents: read pull-requests: writeNote:
pull_request_targetruns in the context of the base branch.
Be cautious when checking out fork code — never run untrusted code
from the fork with elevated permissions.For more information, see:
https://github.com/MishaKav/pytest-coverage-comment#fork-prs
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 with the failed GitHub Actions run linked in the issue and inspect the workflow used by PR #55. Check the fork-PR event and permission settings against the documented pull_request_target approach, then verify that the workflow can comment on fork PRs without executing untrusted fork code with elevated permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100