[Task]: No public CI workflows, and the Makefile references a ci/pipeline.yml that is not in the repository
@Noah-Tervalon-Nvidia já está trabalhando nisso.
Desde 11/9/2026.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
Task type
Other
Current state
The repository has no CI configuration. At commit 13b6811 there is no
.github/workflows/ directory and no ci/ directory; .github/ contains only
ISSUE_TEMPLATE/ and PULL_REQUEST_TEMPLATE.md.
The Makefile refers to a pipeline file that is not in the tree. Makefile:41-44:
# Mirrors the repository-wide header gate plus the desktop half of the CI
# validate and monorepo-gate stages (ci/pipeline.yml). CI additionally rebuilds
# the binaries and runs the Go suites; use make build-binaries and
# make test-services for those.
ci/pipeline.yml does not exist here, so a contributor reading the Makefile is
pointed at something they cannot open, and cannot tell which gates a maintainer
will actually run against their pull request.
The consequence for an outside contributor: CONTRIBUTING.md asks them to run the
gates by hand, nothing verifies a pull request automatically, and a missing SPDX
header or a failing Go suite surfaces only in human review - which CONTRIBUTING.md
says will send the change back.
Desired result
Concrete completion condition - either of the following.
(a) A GitHub Actions workflow that runs on pull_request and on push to main and
executes the documented gates, so a contributor sees the same verdict a
maintainer would:
- node scripts/spdx-headers.mjs (dependency-free; runs in a fresh clone
before any install)
- the desktop gates: npm ci, npm run verify:build-scripts, npm run lint,
npm run typecheck, npm run service-contracts:check, npm run test:unit,
npm run dead-code:check
- go test ./... in every services module, plus services/tests
"make check" (Makefile:45) and "make test" (Makefile:47) already wrap most of
this on Linux and macOS; note that "make check" deliberately omits
dead-code:check, per AGENTS.md.
A matrix over ubuntu-latest / macos-latest / windows-latest would match the
stated support surface. A Linux-only job would still be a large improvement
over none.
(b) If CI is intentionally internal-only and not mirrored to this repository,
then correct Makefile:42 so it does not reference a path that is absent here,
and say in CONTRIBUTING.md that pull requests are validated by an internal
pipeline that contributors cannot see or run.
Either one resolves the mismatch. (a) additionally gives contributors a
pre-review signal.
Relevant paths or references
- Makefile:42 - the ci/pipeline.yml reference
- Makefile:45 - the "check" target (headers, verify, lint, typecheck, contracts,
test-desktop) - Makefile:47, 118, 123 - "test", "test-desktop", "test-services"
- CONTRIBUTING.md, "Development Setup" - the by-hand command list
- AGENTS.md, "Checks" - notes that "make check" omits dead-code:check, and that
Windows runs the npm and go commands directly - scripts/spdx-headers.mjs - the header gate
- services/readme.md, "Testing" - per-component and cross-process suites, and
which tests skip themselves - .github/ - currently ISSUE_TEMPLATE/ and PULL_REQUEST_TEMPLATE.md only
Validation
- Open a pull request that deliberately omits the SPDX header on a new file and
confirm the workflow fails on it, then passes once the header is added. - Confirm the workflow's gate list matches what CONTRIBUTING.md and AGENTS.md tell
contributors to run, so the two cannot drift apart. - Note for whoever implements this: services/readme.md documents that some Go
tests skip themselves when a well-known port (11434, 14319, 14321) is in use or
no mDNS responder is available, and that live-engine tests run only under
NVPAIR_LIVE_OLLAMA / NVPAIR_LIVE_LMSTUDIO. A skip is not a pass, so the workflow
should make skips visible rather than let them read as green. - For (b): confirm that no path referenced by the Makefile is absent from the
repository.
Confirmations
- I searched existing issues for duplicates.
- I agree to follow the Code of Conduct.
- Linguagem predominante
- Go
- Estrelas
- 1.4k
- Forks
- 250
- Merge médio
- 23h 27min
- PRs com merge (30d)
- 1
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de NVIDIA/Personal-AI-Router
-
bug
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 55/100
NVIDIA/Personal-AI-Router#94 · 1 comentário ·
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 74/100
NVIDIA/Personal-AI-Router#92 · 1 comentário ·
-
NVIDIA/Personal-AI-Router#91 · 1 responsável ·
-
[Feature]: Support for Tailscale mesh network endpoints (CGNAT IPs and MagicDNS domain names) Abertaenhancement
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 45/100
NVIDIA/Personal-AI-Router#85 · 1 comentário ·
-
NVIDIA/Personal-AI-Router#84 · 2 comentários · 1 responsável ·
Todas as issues de NVIDIA/Personal-AI-Router
Issues semelhantes
-
optimization optimization:agents-md-curator
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
githubnext/gh-aw-cao#13143 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
blinklabs-io/bursa#904 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comentários ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Abertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 90/100