Skip to content

chore: fixing CI for PRs from forks#237

Merged
skylenet merged 1 commit into
masterfrom
fixup-ci
May 12, 2026
Merged

chore: fixing CI for PRs from forks#237
skylenet merged 1 commit into
masterfrom
fixup-ci

Conversation

@skylenet
Copy link
Copy Markdown
Member

Summary

Cherry-picked from the second commit of #182 (4439298, by @fselmo). Adds a git-repo input to the composite action so CI workflows triggered by PRs from forks clone the fork's HEAD instead of always cloning ethpandaops/benchmarkoor. The workflow wires github.event.pull_request.head.repo.clone_url into that input and uses head.repo.full_name in the run-config-urls so the runtime config files are also fetched from the fork.

Test plan

  • Open a PR from a fork against this branch and confirm the CI action clones the fork (the workflow log should show Cloning https://github.com/<fork-owner>/benchmarkoor.git at ref <sha>).
  • Verify the run-config-urls resolve to raw.githubusercontent.com/<fork-owner>/benchmarkoor/<sha>/... rather than the canonical repo path.
  • PRs from branches inside ethpandaops/benchmarkoor should continue to clone the canonical repo unchanged.

@skylenet skylenet changed the title chore: attempt at fixing CI for PRs from forks chore: fixing CI for PRs from forks May 12, 2026
@skylenet skylenet merged commit cb09ce3 into master May 12, 2026
6 checks passed
@skylenet skylenet deleted the fixup-ci branch May 12, 2026 09:21
skylenet added a commit to CPerezz/benchmarkoor that referenced this pull request May 12, 2026
Brings in ethpandaops#237 (fix CI for PRs from forks) so this PR's checks run
against the updated workflow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants