Django Issue Capture
AI-powered GitHub issue creation and management system for Django with LLM enhancement.
Features
- AI-Powered Issue Generation: Use LiteLLM to generate comprehensive issues from basic descriptions
- Model Optionality: Support for OpenAI, Anthropic, Ollama, and any LiteLLM-compatible provider
- GitHub Integration: Direct promotion of issues to GitHub repositories
- Template System: Predefined templates for bugs, features, tasks, and enhancements
- HTMX Admin: Interactive admin interface with one-click GitHub promotion
- Markdown Support: Full markdown rendering with sanitization
Installation
pip install django-issue-capture
Quick Start
- Add to
INSTALLED_APPS:
INSTALLED_APPS = [
# ...
"solo", # Required dependency
"django_markdownify", # For markdown rendering
"django_issue_capture",
]
- Add context processor (optional, for floating button):
TEMPLATES = [{
'OPTIONS': {
'context_processors': [
# ...
'django_issue_capture.context_processors.issue_capture_settings',
],
},
}]
- Include URLs:
from django.urls import include, path
urlpatterns = [
# ...
path("issues/", include("django_issue_capture.urls")),
]
- Run migrations:
python manage.py migrate
- Configure in Django Admin:
Navigate to Issue Capture Settings and configure:
- GitHub: Repository (
owner/repo) and Personal Access Token - LLM: API key and model (e.g.,
gpt-4o-mini,anthropic/claude-3-5-sonnet-20241022)
- Set up issue templates:
python manage.py setup_issue_templates
Configuration
LLM Models
This package uses LiteLLM for model optionality. Use the format provider/model-name:
| Provider | Model Format | API Key Prefix |
|---|---|---|
| OpenAI | gpt-4o-mini, gpt-4o |
sk-... |
| Anthropic | anthropic/claude-3-5-sonnet-20241022 |
sk-ant-... |
| Ollama (local) | ollama_chat/llama3, ollama_chat/mistral |
(none) |
| Azure OpenAI | azure/deployment-name |
(Azure key) |
Note: OpenAI models work without a prefix. Most other providers require the
provider/prefix.
See LiteLLM providers for the full list.
GitHub Integration
To promote issues to GitHub, you need a Personal Access Token (PAT) with the appropriate permissions.
Creating a Personal Access Token
Option 1: Fine-grained token (Recommended)
Fine-grained tokens provide more granular control and are GitHub's recommended approach:
- Go to GitHub Settings
- Click Developer settings (bottom of left sidebar)
- Click Personal access tokens → Fine-grained tokens
- Click Generate new token
- Configure the token:
- Token name: e.g., "Django Issue Capture"
- Expiration: Choose based on your security requirements
- Repository access: Select "Only select repositories" and choose the target repo(s)
- Permissions: Under "Repository permissions", set:
- Issues: Read and write (required to create issues)
- Metadata: Read-only (automatically selected)
- Click Generate token
- Copy the token immediately (it won't be shown again)
Option 2: Classic token
Classic tokens are simpler but have broader access:
- Go to GitHub Settings
- Click Developer settings (bottom of left sidebar)
- Click Personal access tokens → Tokens (classic)
- Click Generate new token → Generate new token (classic)
- Configure the token:
- Note: e.g., "Django Issue Capture"
- Expiration: Choose based on your security requirements
- Scopes: Select
repo(grants full control of private repositories, including issues)
- Click Generate token
- Copy the token immediately (it won't be shown again)
Required Permissions
| Permission | Type | Purpose |
|---|---|---|
| Issues | Read and write | Create and manage issues in the repository |
| Metadata | Read-only | Access repository metadata (auto-included) |
Note: Classic tokens with
reposcope grant broader access than needed. For production use, fine-grained tokens with minimal permissions are recommended.
Adding the Token to Django
- Navigate to Django Admin → Issue Capture Settings
- Enter your GitHub repository in the format
owner/repo(e.g.,octocat/hello-world) - Paste your Personal Access Token in the GitHub API key field
- Save the settings
Environment Variables (Production)
For production, use environment variables:
# settings.py
from django.conf import settings
# Override singleton defaults with env vars
ISSUE_CAPTURE_LLM_API_KEY = os.getenv("ISSUE_CAPTURE_LLM_API_KEY")
ISSUE_CAPTURE_GITHUB_API_KEY = os.getenv("GITHUB_API_KEY")
Usage
Create Issue via UI
- Navigate to
/issues/create/ - Choose creation mode:
- Standard Form: Manual entry with all fields
- AI Quick Generate: One-shot AI enhancement from basic input
Promote to GitHub
- View issues at
/issues/list/ - Click issue to view details
- Click "Promote to GitHub" (or use admin interface)
Admin Interface
The Django admin provides:
- Issue management with status tracking
- One-click GitHub promotion (HTMX-powered)
- Template configuration
Development
# Clone and install
git clone https://github.com/directory-platform/django-issue-capture
cd django-issue-capture
uv sync --extra dev
# Run tests
PYTHONPATH=. uv run python tests/manage.py test
# Run quality checks
ruff check src/ tests/
ruff format src/ tests/
mypy src/
Dependencies
- Django ≥ 4.2
- django-solo ≥ 2.0
- shortuuid ≥ 1.0
- requests ≥ 2.32
- litellm ≥ 1.70
- django-markdownify ≥ 0.9
License
MIT License - see LICENSE file for details.
Contributing
Contributions welcome! Please:
- Fork the repository
- Create a feature branch
- Add tests for new functionality
- Ensure all tests pass
- Submit a pull request
Releasing
See RELEASING.md for instructions on publishing new versions to PyPI.
Support
- Issues: https://github.com/directory-platform/django-issue-capture/issues
- Docs: https://github.com/directory-platform/django-issue-capture
Credits
Part of the Directory Platform ecosystem. Extracted from directory-builder.
Metadata
Release files for django-issue-capture 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_issue_capture-0.2.2.tar.gz | 39.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_issue_capture-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 79.6 kB
Release files / django_issue_capture-0.2.2.tar.gz
| Download URL | django_issue_capture-0.2.2.tar.gz |
|---|---|
| Size | 39.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
893dedf12ed781ff6cf4cdecb275b9fc313b2844ebe78b976c42467c428cb9d6
|
|
BLAKE2b-256 checksum How to use checksums |
82c025e023734c54d02f7074ec6f6b752f514b367a5b3ab2315afb3f5fe88a8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 16, 2026.
Transparency logRelease files / django_issue_capture-0.2.2-py3-none-any.whl
| Download URL | django_issue_capture-0.2.2-py3-none-any.whl |
|---|---|
| Size | 40.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eeaa162314ecf1d7d3469ea74c3e8ca15c3914deac58f24c6805f52624e181e4
|
|
BLAKE2b-256 checksum How to use checksums |
4a6fe48ad180ec24eeca91e15488932bce3e85f14bec6ac7b18c5cdfe12edcf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 16, 2026.
Transparency log