hermes-agent/.github/workflows
ethernet 3ee1bb323e fix(ci): resolve fork PRs in the E2E evidence publisher
The publisher read the PR number from the CI run's pull_requests
payload. GitHub keeps that payload empty for fork runs, so the job
printed 'No pull request is associated' and stopped on every fork PR.

Resolve the PR from the run's head owner, branch, and SHA instead.
The SHA match skips runs that a newer push superseded.

A fork PR also has no CI review comment, because the live poller
skips forks. The publisher now logs this and exits clean instead of
raising; the evidence stays in the workflow artifact.
2026-08-11 03:53:52 -04:00
..
ci-review-comment.yml fix(ci): review comment poller deadlocked on its own run 2026-08-10 13:48:21 -04:00
ci.yml
contributor-check.yml
deploy-site.yml
docker-lint.yml
docker.yml
docs-site-checks.yml
e2e-desktop.yml
history-check.yml
infographic-check.yml
install-e2e-run.yml
install-e2e.yml
installer-tests.yml
js-autofix.yml fix(ci): keep review-gated files out of the js-autofix patch 2026-08-10 02:36:55 -04:00
js-tests.yml
label-rerun.yml
lint.yml
lockfile-diff.yml
osv-scanner.yml
publish-e2e-evidence.yml fix(ci): resolve fork PRs in the E2E evidence publisher 2026-08-11 03:53:52 -04:00
review-labels.yml
skills-index-freshness.yml
skills-index.yml
supply-chain-audit.yml
tests-os.yml ci: print the zero-selection diagnostic instead of dying first 2026-08-09 22:09:49 -04:00
tests.yml fix(ci): merge all duration slices, not one 2026-08-10 14:33:36 -04:00
uv-lockfile-check.yml