Try DiffCI on your repository: design partners wanted

未关闭
#86 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
15/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, go, java, python, typescript
领域
ci-cd, testing

调研方向

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 内容生成。

描述

enhancement help wanted

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

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DiffCI/core 的其他 Issue

查看 DiffCI/core 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。