Repository navigation
docs(contributing): Known Issues Sweep references a known_issues/ directory this repo doesn't have #138
Description
CONTRIBUTING.md's 'Known Issues Sweep' section (copied from the monorepo during the split) requires a known_issues/_.md entry plus a GitHub issue, but this repo has no known_issues/ directory; deferred work is tracked in GitHub issues only (CLAUDE.md says so since #137). Either update CONTRIBUTING.md to say GitHub issues are the tracker here, or create known_issues/ and move to that model. The same check applies to LeanerCloud/cloud-commitments-mcp, which also has no known_issues/. Raised by CodeRabbit on #137.
Activity
cristim commentedon Oct 17, 2026
Decision needed (one line): is the tracker GitHub issues only, or
known_issues/plus issues?CONTRIBUTING.md(~:242-308) still mandatesknown_issues/, CLAUDE.md says the directory does not exist, and it now does (known_issues/01_gcp_compute_nonroot_term.md, edited by open PR #307). Either way the fix is a 30-60 line docs edit. Markingstatus/needs-info.cristim commentedon Oct 20, 2026
Question for @cristim (needed before #138 can move): CLAUDE.md on main says this repo has no
known_issues/directory and that GitHub issues are the tracker. Butknown_issues/01_gcp_compute_nonroot_term.mdwas added in abc5074 (#401), and CONTRIBUTING.md (~:242-308) still requires the directory model for the Known Issues Sweep.Options:
known_issues/01_gcp_compute_nonroot_term.mdinto its issue (gcp compute: non-root populateRecommendationResources path still guesses the term #304), remove the directory, and rewrite the CONTRIBUTING.md sweep to use issues.known_issues/and keep CONTRIBUTING.md as is.Without an answer, I'll take option 1, which matches CLAUDE.md. [claude-cc-libs]
docs(azure,gcp): drop dangling known_issues/ references in comments
docs: fix em-dash and cross-component note
docs(gcp): drop dangling 11_gcp_provider.md reference
docs(contributing): use GitHub issues instead of known_issues/ (#586)