Skip to content

CI cannot go green on a pull request from a fork #2142

Open

Description

@marordyan

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:

  1. A maintainer pushes the branch into nemarOrg/nemar-cli (or opens the PR from an upstream branch), so CI runs with secrets.
  2. A maintainer runs the secret-dependent jobs on the PR's head another way and posts the result.
  3. I get read access to the dev-plane test keys, so I can run api-test and integration-dev locally against api-test.nemar.org with an isolated NEMAR_CONFIG_DIR (as AGENTS.md describes). The planned /ci-nemar-cli secrets folder in nemarOrg/nemar-infisical (epic Epic: Centralize secret management in self-hosted Infisical (single source of truth for Cloudflare, GitHub, AWS, local) #885) may make this easier later.

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.

I'll link the PR here once it's open.

Activity

  1. marordyan commented on Nov 13, 2026

    @marordyan
    Author

    The pull request is open as a draft: #2144.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions