Django support: design partners and contributors wanted

未關閉
#87 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
42/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
django, python
領域
ci-cd, testing

研究方向

Read docs/adding-an-adapter.md, then the Python adapter in src/repo/adapters/python.ts, which this work extends. Pick one unblocked step, such as detecting a Django project from manage.py or DJANGO_SETTINGS_MODULE, and confirm the design with the thread first. Done means the adapter recognises the project and a fixture repo gets Django-aware selection or a blockers fallback instead of an empty graph.

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

描述

adapter enhancement help wanted

DiffCI works out what a change needs from CI, starting with the tests it affects, so AI coding agents (and people) can run them before pushing. Python projects tested with pytest are supported today (#61, #75). Django is next, and this is open for contributors and design partners.

Why Django needs its own work: much of a Django project is wired by strings, not imports, so a plain import graph misses it:

  • INSTALLED_APPS, MIDDLEWARE, ROOT_URLCONF, AUTH_USER_MODEL and include("app.urls") name modules as dotted strings
  • templates, static files and fixtures are found by app directory, not imported
  • a settings.py change can affect everything, or nothing
  • many projects run manage.py test (unittest discovery), not pytest

Today these show up as missed edges or a full-suite fallback.

Steps (each is one PR; take any that are unblocked):

  • Detect a Django project (manage.py, DJANGO_SETTINGS_MODULE, pytest-django settings)
  • Treat dotted-string settings and include() targets as imports
  • Map templates, static files and fixtures to the app that owns them
  • Narrow settings.py changes where the changed setting is known, else fall back with a reason
  • Generate manage.py test <labels> commands when the project doesn't use pytest
  • Replay on one public Django repository and publish the report

Ground rules

  • When the adapter is unsure, it records a blockers entry and DiffCI runs the full suite. An empty graph must never look like "nothing affected".
  • Read the adapter guide first; the Python adapter (src/repo/adapters/python.ts) is where this builds.
  • Discuss design questions here, so every step stays consistent.

Run a Django codebase? Try npx --yes @diffci.com/diffci@latest check --base origin/main --head HEAD and post what it selected or the fallback reason below. That tells us which step to do first. 👍 this issue if you'd use it.

主要語言
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 摘要。