Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

feat(evals): back review fixtures with a repo so the horizontal pass can run

未關閉
  • 哪裡不對？
#11 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
54/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
javascript, nodejs, react
領域
developer-experience, testing

研究方向

Start by inspecting the review fixtures, the fix-node fixture, and the runner that applies pr.diff; the issue does not name their paths. Give each fixture base code under repo/, apply its diff on a branch, update expected.md where sibling code changes the finding, and add two dotnet variants with sibling endpoints that differ in ownership checks. Done when the horizontal pass can review repository context and those acceptance criteria are met.

由索引模型根據 Issue 內容生成。

描述

enhancement eval

What

The review fixtures are bare .diff files, so the review sees only the hunks and cannot read sibling endpoints, guards or tests.

Why

The horizontal pass and several expected answers depend on code outside the diff. The remaining false positive (an ownership check graded must) comes from this: the expected answer is a question because siblings are out of view, and a fixture with visible siblings would test the real rule.

Acceptance criteria

  • Each review fixture gets a repo/ with the base code, as fix-node has, and the runner applies pr.diff on a branch.
  • expected.md is updated where a finding depends on sibling code.
  • The dotnet fixture includes sibling endpoints, with and without ownership checks, in two variants.
主要語言
JavaScript
星號
0
分支
0
30 天內沒有已合併 PR

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

devmaxxx/stackwise 的其他 Issue

查看 devmaxxx/stackwise 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。