Try DiffCI on your repository: design partners wanted
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 1/5
- 預估耗時
- 1 小時以內
- 新手友好度
- 15/100
研究方向
This is an outreach call for design partners, not a code task. Read docs/release-boundary.md for the supported stacks and examples/github-actions-check-plan.yml for the scheduled comparison setup. Optionally run the local npx @diffci.com/diffci check command on a real change. Done means commenting with your repository or stack, or emailing the maintainer, and saying whether a public repository may be replayed.
由索引模型根據 Issue 內容生成。
描述
DiffCI works out what a change needs from CI, so you and your AI coding agents can run the right things before pushing. Required CI is never skipped. Today that means the tests and checks a change affects; build and deploy decisions (rebuild the image or not, deploy or promote) come next, and design partners shape them. We'd like a few more teams to try it on real repositories and tell us where it gets things wrong.
Supported today (details in the release boundary)
- JavaScript/TypeScript: Vitest, pnpm workspaces, Vue components
- Go: a root module
- Java: conventional Maven reactors
- Python: pytest (see #75)
When DiffCI isn't sure about a change, it runs the full suite and says why.
Try it locally (about 5 minutes, sends nothing anywhere):
npx --yes @diffci.com/[email protected] check --base origin/main --head HEAD
To compare it with your full suite over time, use the scheduled check-plan example. It reports any failure the selection would have missed. There's also the observer GitHub Action, which comments on PRs without changing what runs.
What you get
- direct help setting it up
- fixes for the cases that matter to your repository, first
What we ask
- run it on real changes and share the reports, or only the fallback reasons if your code is private
- tell us whenever it selected too little, or fell back to the full suite when it shouldn't have
Comment below with your repository (or just its stack) or email [email protected]. If your repository is public, say whether we may replay it. We'll only replay repositories whose maintainers say yes.
- 主要語言
- TypeScript
- 星號
- 0
- 分支
- 4
- 平均合併
- 18 小時 41 分鐘
- 30 天內合併 PR
- 48
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
DiffCI/core 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at random可能已有人在做 @FredApps 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆
-
Agent tools: changed_files lists only the new path of a renamed file可能已有人在做 @FredApps 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
adapter good first issue
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
相似的 Issue
-
agent-ready area: ui-server priority: p3 type: test
難度 2/5 1-3 小時 新手友好度 78/100
schlessera/brain-kit#4249 ·
維護者通常 1 天內回覆
-
documentation tool triaged
難度 2/5 1-3 小時 新手友好度 73/100
can1357/oh-my-pi#19608 · 2 則留言 ·
維護者通常 1 天內回覆
-
dependencies tech-debt
難度 2/5 1-3 小時 新手友好度 65/100
bcgov/nr-waste-plus#1549 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 78/100
blixvip/solana-tx-parse#18 ·