swiftlang / swiftlang/github-workflows
Please skip CI jobs that run on self-hosted runners on forked repositories
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 115
- Forks
- 57
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
The following jobs run on self-hosted runners.
- https://github.com/swiftlang/github-workflows/blob/497d9ab8410e69981b3b2f28da24cf7bf4b8733d/.github/workflows/swift_package_test.yml#L289
- https://github.com/swiftlang/github-workflows/blob/497d9ab8410e69981b3b2f28da24cf7bf4b8733d/.github/workflows/swift_package_test.yml#L331
- https://github.com/swiftlang/github-workflows/blob/497d9ab8410e69981b3b2f28da24cf7bf4b8733d/.github/workflows/swift_package_test.yml#L378
However, the self-hosted runner is not available for forked repositories. This causes CI to hang and fail after a long period of time on forked repositories. This is frustrating for contributors.
Example:
Similar cases from the past:
Contributor guide
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 .github/workflows/swift_package_test.yml at the three linked job locations, then trace the invocation from .github/workflows/pull_request.yml. Check how the jobs behave for pull requests from forked repositories. Done means those self-hosted jobs are skipped for forks instead of hanging and failing after a long wait.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100