Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Report bugs at https://github.com/omenapps/django-model-info/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for features. Anything tagged with "feature" is open to whoever wants to implement it.
django-model-info could always use more documentation, whether as part of the official django-model-info docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://github.com/omenapps/django-model-info/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome.
Ready to contribute? Here's how to set up django-model-info for local development.
-
Fork the django-model-info repo on GitHub.
-
Clone your fork locally:
$ git clone git@github.com:your_name_here/django-model-info.git -
Install uv and set up your local development environment:
$ cd django-model-info/ $ uv sync --group dev -
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-featureNow you can make your changes locally.
-
When you're done making changes, check that your changes pass linting and the tests:
$ uv run nox -s pre-commit $ uv run pytest -vvTo run the full test matrix across Python and Django versions:
$ uv run nox -s tests -
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature -
Submit a pull request through the GitHub website.
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
- The pull request should work for Python 3.11-3.14. CI will verify this automatically.