Django support: design partners and contributors wanted

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
django, python
Domain
ci-cd, testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
0
Forks
4
Avg merge
18h 41m
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DiffCI/core

All issues in DiffCI/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.