VectorCI Docs

VectorCI guide

Keep product repositories isolated

Run one pinned CLI inside each product repository without granting cross-repository access.

Use one process per repository

Start the product agent and pinned CLI from the exact product Git root. The CLI refuses parent directories, sibling repositories, and the VectorCI provider source repository.

Run independently inside each product 
cd /absolute/product-one
npx vectorci setup .
npx vectorci doctor .

cd /absolute/product-two
npx vectorci setup .
npx vectorci doctor .

Use a product-scoped identity

  • The product credential may access only its selected product repositories.
  • The product credential must receive Not Found when it probes davidgrijalva-orin/VectorCI.
  • The VectorCI GitHub App may post the provider-owned VectorCI check without giving the product agent provider-source permission.
  • A separate owner profile is required for VectorCI source, releases, workers, and provider administration.

Allowed product surfaces

  • The exact pinned @orintech/vectorci CLI release.
  • Product-owned .vectorci.yml and public documentation.
  • Provider-owned VectorCI status and Check Run output.