Django Forge Issues
Create github/gitlab issues directly from a Django application.
Installation
pip install django-forge-issues[gitlab] or pip install django-forge-issues[github]
Then add DJANGO_FORGE_ISSUES to your INSTALLED_APPS and to your urls.py:
urlpatterns += [path("", include("django_forge_issues.urls"))]
This give you the urls django_forge_issues/create/<str:contenttype>/<int:pk>
and django_forge_issues/list/<str:contenttype>/<int:pk> for creating resp.
listing the urls.
Configuration
DJANGO_FORGE_ISSUES_PROJECT = "https://the.url.of/your/project"
DJANGO_FORGE_ISSUES_TOKEN = "secret-token"
For Gitlab projects, the DJANGO_FORGE_ISSUES_PROJECT must not be the web URL to
the project but the hostname of the instance and the ID of the project. You can
find the project ID in Settings -> General of your project. So the variable coul
look like https://gitlab.example.org/134 where gitlab.example.org is the instance
hostname and 134 is the project ID.
For Gitlab projects, create the token in Project Settings -> Access tokens. Add a
token that has the role Reporter and the api scope.
For Github projects, create the token in Settings -> Developer Settings -> Personal Access tokens.
1 maintainer
Metadata
1 maintainer
Release files for django-forge-issues 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_forge_issues-0.2.0.tar.gz | 3.5 kB | With provenance | Details for django_forge_issues-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_forge_issues-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for django_forge_issues-0.2.0-py3-none-any.whl |
Total release size: 8.1 kB
Release files / django_forge_issues-0.2.0.tar.gz
| Download URL | django_forge_issues-0.2.0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45c168a8f2227875750b0dacce1cff44fff9efb15a9e524ac247e5eecd934897
|
|
BLAKE2b-256 checksum How to use checksums |
0e6d3970c5dafcd8f00f0debd97984e8a5f126ae9459b52a42429562cefbba79
|
| 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 21, 2026.
Transparency logRelease files / django_forge_issues-0.2.0-py3-none-any.whl
| Download URL | django_forge_issues-0.2.0-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af282b098c39d75560d1c7dda258ddc0d28fde7b1119aff6f2c0f3cf1107d2ab
|
|
BLAKE2b-256 checksum How to use checksums |
34b38432acaf36b27f1a11406cf2d87f7693cc0177ea95389e11c2b6531ae367
|
| 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 21, 2026.
Transparency logSecurity for django-forge-issues 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_forge_issues-0.2.0.tar.gz
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 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
