Please skip CI jobs that run on self-hosted runners on forked repositories

Open Beginner friendly
#305 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd, devops

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.

Description

The following jobs run on self-hosted runners.

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:

Dominant language
Swift
Stars
115
Forks
57
Avg merge
1d 8h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from swiftlang/github-workflows

All issues in swiftlang/github-workflows

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.