docs-version-sync: cannot resolve the repo root on the public mirror
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
Research direction
Read tools/docs-version-sync/main.go and compare its findRepoRoot logic with tools/collect-dependencies/main.go, then run the documented command from docs/AGENTS.md on the public mirror. Update the root detection and the relevant AGENTS guidance so the command works without imports.yaml; done means the command runs successfully from the mirror.
Written by the indexing model from the issue text.
Description
Describe the bug
The regeneration command documented in docs/AGENTS.md cannot run in this
repository:
$ go run -C tools/docs-version-sync . --target main
docs-version-sync: imports.yaml not found (started from .../tools/docs-version-sync)
exit status 1
findRepoRoot in tools/docs-version-sync/main.go walks up looking only for
imports.yaml, which is intentionally absent on the public mirror. The repo
states this in three places: license-compliance.md:232,
tools/collect-dependencies/scan.go:31, and
tools/collect-dependencies/README.md:38.
The sibling tool tools/collect-dependencies/main.go already handles it by
falling back to the .git marker.
Root AGENTS.md also points agents at imports.yaml without noting that it is
internal, unlike tools/ci/subproject-validations.yaml, which is marked as not
present in this public snapshot.
Steps or code to reproduce bug
go run -C tools/docs-version-sync . --target main
Expected behavior
The documented command runs. Mirror the .git fallback that
collect-dependencies already uses.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 415
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/nvcf
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100