You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI cannot go green on a pull request from a fork #2142
I'm about to open a pull request from my fork (marordyan/nemar-cli) into dev: a local Zarr reader (a read core shared by the MCP server and the CLI, a local engine, and nemar zarr read). .rules/git.md says an epic -> dev PR waits for the full green CI run, and .rules/code_review.md requires green CI on the final head. A PR from a fork cannot reach that on its own, and I need a maintainer's help with it. cc @nemarOrg/admins (per AGENTS.md: escalate when blocked).
Why it can't go green
GitHub gives a workflow running on a fork's pull request no repository secrets (TEST_ADMIN_API_KEY, TEST_USER_API_KEY, TEST_BYPASS_TOKEN, GH_TOKEN, DOCS_READ_TOKEN, ...).
test.yml skips the private docs checkout for fork PRs on purpose (github.event.pull_request.head.repo.full_name == github.repository).
So api-test and integration-dev fail at authentication before they reach what they check.
The same happens on my fork's own CI. Across six runs there, including one at the commit the work branched from (785c172d, a plain copy of dev), the results were identical test by test:
Job
pass
fail
api-test
31
28
integration-dev
1,920
46
Every failure is a 401 or the CLI reporting "invalid api key format". None is caused by the change.
What would unblock it
Any one of these:
A maintainer pushes the branch into nemarOrg/nemar-cli (or opens the PR from an upstream branch), so CI runs with secrets.
A maintainer runs the secret-dependent jobs on the PR's head another way and posts the result.
One limit applies whichever option is used: the PR also changes backend code (the MCP read path moves into shared/zarr/, and a schema route is added), and api-test / integration-dev run against the deployed dev Worker, which won't have those changes. The backend side is covered by the unit tier, the MCP golden test and mcp-smoke.sh.
Activity
marordyan commentedon Nov 13, 2026
The pull request is open as a draft: #2144.