Figure out how to run CI jobs only once on PRs
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 230
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
- Related PR: https://github.com/jraska/github-client/pull/706
- External PR where we required the
pull_request-target: https://github.com/jraska/github-client/pull/692 - Duplicated jobs problem, yet we still want to run CI on forks with approval.
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 reviewing related PRs #706 and #692 and the attached screenshot to understand the duplicated CI jobs and the pull_request_target requirement. Done means CI runs only once for a pull request while fork contributions can still run with approval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100