Django support: design partners and contributors wanted

Offen
#87 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
django, python
Bereich
ci-cd, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
0
Forks
4
Ø Merge
18 Std. 41 Min.
Gemergte PRs (30 T.)
48

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus DiffCI/core

Alle Issues in DiffCI/core

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.