Expose a read-only repository planning API with an injected command backend
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 22/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- github, javascript
研究方向
Read merged command transport PR #47 and minimal CLI fixture extraction PR #48, then inspect the native planning entry point and the CLI-2 characterization tests described in the issue. The issue says CLI-2 still needs an explicitly authorized bounded design and measurement attempt before implementation; verify the proposed unit fits the 400-line cap. Done means the full API contract, tests, and documentation pass the listed CLI-4 checks while preserving native behavior.
由索引模型根據 Issue 內容生成。
描述
Expose a read-only repository planning API with an injected command backend
Goal and scope
Introduce executeRepositoryPlan(argv, { execute } = {}) for repository planning of labels, milestones, templates and files. This is a separate feature candidate, not an additional acceptance requirement for #15.
The native CLI remains the product entry for Projects and apply. Exclude mutations through the API, new schema/default/flag/version fields, workflow activation, branch-protection features, live credentials, sandbox guarantees and release changes. A supplied backend is trusted code, not a security sandbox.
Dependencies and coordination
Build on merged command transport PR #47 and merged minimal-CLI fixture extraction PR #48. These are delivered foundations, not outstanding issues; enabled-family/guard characterization is still CLI-2 work. Milestone and scheduling are deliberately unassigned; the approved B01→B06 order is unchanged. This issue is proposed, not a reservation or implementation grant. Recheck dependencies, assignees, claims and related PR before any explicit start.
Acceptance criteria
- Plan all four supported resource families with the same target/config/observed/plan and canonical authorization kernel as the native CLI.
- Reject apply, including authorized apply, before command-runner construction, config discovery or backend execution; an earlier rejection by the existing parser remains valid.
- Validate/normalize actual config, reject an active Project before target/backend discovery, and prevent caller extras from bypassing this private policy.
- Preserve legacy native Projects/apply behavior and
ghJson(args, options)/ghTry(args, options)calling contracts. - Return a fresh
{ report, exitCode }per supported call, with 0/1 outcomes, no process exit or console transport, and no cross-call mutable backend state. - Cover import safety, native/default/injected backends, apply refusal, config/project policy, backend validation, command errors and malformed JSON, output freshness and sequential/concurrent isolation. Document argument/type boundaries rather than promising universal error capture.
- Keep callback identity/private policy out of serialized config, plan and authorization hashes.
- Verify the API selects only read/discovery requests and performs no product apply/file-write path. Disabled families issue no family-specific requests; global discovery may remain.
ODD phases
| Phase | Result | Prerequisite | Validation and exit |
|---|---|---|---|
| CLI-2 | Characterize current native planning: enabled families, ensure/replace/noop, guards and disabled families | Merged fixtures #48 | Real CLI assertions cover existing behavior; all essential tests/docs fit a complete measured unit |
| CLI-3 | Extract live private planning used immediately by native main | CLI-2 | Characterization remains green; no unused public factory or Project-policy branch |
| CLI-4 | Deliver the complete public API and all new entry contracts/docs | CLI-3 | Functional contract matrix, regression checks and independent verification pass |
Forecasts for CLI-2/3/4 are respectively 360–439, 100–150 and 320–370 changed lines. They are not measured fits, minimums or permission to write. CLI-2's forecast crosses the 400-line cap; actual fit is unproven. Its next gate is an explicitly authorized bounded design/measurement attempt, not source implementation. No cap exception or scope split is inferred from a forecast. Form and measure the whole proposed unit in RAM before writing anywhere; if it exceeds 400 additions+deletions, stop without compressing code, dropping assertions or deferring essential tests/docs. Moves count twice.
Delivery
Use meaningful test-first evidence where applicable, proportionate checks otherwise, and independent verification according to risk. Separate authorization remains necessary for implementation and each delivery operation. No hidden helpers, live API validation or release claim is implied.
- 主要語言
- JavaScript
- 星號
- 22
- 分支
- 3
- 平均合併
- 27 分鐘
- 30 天內合併 PR
- 27
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
egdev6/github-repository-bootstrap 的其他 Issue
-
status:approved type:chore
難度 5/5 一週以上 新手友好度 25/100
egdev6/github-repository-bootstrap#57 ·
維護者通常 1 天內回覆
-
type:docs
難度 1/5 1 小時以內 新手友好度 20/100
egdev6/github-repository-bootstrap#50 ·
維護者通常 1 天內回覆
-
status:approved type:chore
難度 5/5 一週以上 新手友好度 25/100
egdev6/github-repository-bootstrap#30 ·
維護者通常 1 天內回覆
-
status:approved type:chore
難度 5/5 一週以上 新手友好度 42/100
egdev6/github-repository-bootstrap#29 ·
維護者通常 1 天內回覆
-
enhancement status:approved
難度 5/5 一週以上 新手友好度 35/100
egdev6/github-repository-bootstrap#28 ·
維護者通常 1 天內回覆
查看 egdev6/github-repository-bootstrap 的全部 Issue
相似的 Issue
-
[BUG]: Prompt compressor crashes with TypeError when a past chat has a non-string response.text可能已有人在做 @ManojDevarajulu 今天認領。 未關閉possible bug
難度 2/5 1-3 小時 新手友好度 82/100
Mintplex-Labs/anything-llm#6737 ·
維護者通常 1 天內回覆
-
check:passed feeds:add
難度 2/5 1 小時以內 新手友好度 62/100
-
bug
難度 2/5 1-3 小時 新手友好度 70/100
codex-team/editor.js#3037 ·
-
No Code Attached Yet
難度 2/5 1-3 小時 新手友好度 72/100
joomla/joomla-cms#48626 ·
維護者通常 1 天內回覆
-
complexity: trivial good first issue impact: low
難度 1/5 1 小時以內 新手友好度 78/100
ueberdosis/tiptap#8522 ·
維護者通常 1 天內回覆