summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
13 daysRefs #35007 -- Added biome to lint and format CSS files.Tom Carrick
2026-04-16Added automated quality checks for PRs as a GitHub Actions workflow.Natalia
This work adds automated PR quality checks as a GitHub Actions workflow to enforce contribution requirements consistently and reduce the manual burden on reviewers for incoming PRs. Thanks to the many reviewers providing meaningful feedback. Co-authored-by: Frank Wiles <frank@revsys.com>
2026-04-13Removed unused code checkout step from labels.yml GitHub Action.Jacob Walls
2026-03-25Fixed #36993 -- Clarified N/A usage in pull request template for typo fixes.JaeHyuckSa
Signed-off-by: JaeHyuckSa <jaehyuck.sa.dev@gmail.com>
2026-03-19Refs #36620 -- Reduced permissions on coverage comment workflow.Jacob Walls
2026-03-19Refs #36620 -- Fixed coverage comment deletion.Jacob Walls
Follow-up to 92d4aea5ffacc38c5f7903b9410d0abec83f14de.
2026-03-16Skipped check_commit_messages action on forks.Jacob Walls
This was causing permission errors on private forks, e.g. the one maintained by the Security Team for staging security patches. Follow-up to f8665b1a7ff5e98d84f66ad0e958c3f175aa5d8b.
2026-03-12Discouraged automated AI reviews of pull requests.Natalia
Some contributors have been requesting Copilot reviews on pull requests submitted to the Django repository. These automated reviews add noise to the PR history, making it harder to follow the discussion, and Django does not incorporate them into its review process. This change discourages the practice by: - Adding a `copilot-instructions.md` file instructing Copilot to decline review requests in this repository. - Adding a checklist item to the PR template asking contributors not to request automated AI reviews for their PR. - Documenting the policy in the contributing guidelines.
2026-03-07Optimized check_commit_messages GitHub action.Jacob Walls
2026-03-06Extended checks and docs for proper commit message format and edition.Jacob Walls
Thanks to Tim Schilling for the review. Co-authored-by: Natalia <124304+nessita@users.noreply.github.com>
2026-03-02Aligned docs checks between GitHub Actions and local development.Natalia
2026-02-13Installed libmemcached-dev in screenshots workflow.Jacob Walls
2026-02-12Refs #36620 -- Removed stray + from coverage comment workflow step.Jacob Walls
2026-02-11Refs #36620 -- Shortened coverage diff comment.Jacob Walls
2026-02-11Refs #36620 -- Guarded coverage tests workflow behind a label.Jacob Walls
This also removes the skip on the primary tests workflow so that it runs more predictably.
2026-01-29Fixed spell checking in docs GitHub Actions workflow.Natalia
The spelling check job was passing even with spelling errors because the system spell checker (`aspell`) was not installed on the GitHub Actions runner. While `sphinxcontrib.spelling` and `PyEnchant` were installed via pip, they require a system-level spell checker backend to function.
2026-01-23Refs #36620 -- Ran coverage tests workflow on forks.Jacob Walls
We can continue to limit the coverage comment workflow to django/django, but now that this workflow is the main python test workflow, it should run on forks by default. The other tests workflow (currently running only JavaScript tests) may start running python tests again once we flesh out the matrix, but since it was duplicating the coverage tests configuration, we temporarily removed it. Follow-up to 26b0e2bb92caf2d16cabe455792350f20d6f42ca.
2026-01-20Fixed #36639 -- Added CI step to run makemigrations --check against test models.Skyiesac
2026-01-12Bumped linter dependencies.Ülgen Sarıkavak
* psf/black-pre-commit-mirror: 25.9.0 -> 25.12.0 * pre-commit/mirrors-eslint: v9.36.0 -> v9.39.1 * zizmorcore/zizmor-pre-commit: v1.16.3 -> v1.19.0 * zizmorcore/zizmor-action: 0.2.0 -> 0.3.0
2026-01-08Extended GitHub pull request template to require AI assistance disclosure.Natalia
2025-12-29Bumped checkout version in Github actions configuration.Pravin Kamble
2025-12-06Refs #36620 -- Fixed PR number extraction in coverage_comment workflow.saurabh
Passing the PR number as an artifact is more reliable in cross-fork workflows.
2025-12-05Refs #36620 -- Removed PR number null check from coverage_comment workflow.saurabh
2025-12-04Fixed #36620 -- Fixed workflow to summarize coverage in PRs.saurabh
Follow-up to a89183e63844a937aacd3ddb73c4952ef869d2cc, which was reverted in e4c4a178aa642f8493b7ae2c0ad58527af51f67e because a change to the workflow trigger resulted in the PR branch not being checked out. We used this opportunity to reimplement the coverage tracing and coverage commenting in a two-workflow pattern with more granular permissions. To reduce duplicative workflows, we removed the existing python test workflow on PRs, at least until we run more distinct configurations on GitHub actions. The run with coverage tracing enabled is sufficient for now. The existing workflow still runs on pushes to main. We can revisit when adding more test configurations.
2025-11-26Added timeout-minutes directive to all GitHub Actions workflows.Natalia
GitHub Actions defaults to a 360-minute (6-hour) timeout. We've had jobs hang due to issues in the parallel test runner, causing them to run for the full 6 hours. This wastes resources and negatively impacts CI availability, so explicit timeouts have been added to prevent long-running hangs.
2025-11-25Reverted "Fixed #36620 -- Added coverage workflow to summarize coverage in ↵Natalia
pull requests." This reverts commit a89183e63844a937aacd3ddb73c4952ef869d2cc.
2025-11-21Fixed #36620 -- Added coverage workflow to summarize coverage in pull requests.saurabh
Part of GSoC 2025. Thanks Lily for mentorship, and Sarah Boyce and Jacob Walls for reviews.
2025-11-21Configured dangerous-triggers zizmor rule.Jacob Walls
2025-11-21Addressed unpinned-uses zizmor finding.Jacob Walls
2025-11-21Simplified actions after applying zizmor auto-fixes.Jacob Walls
2025-11-21Applied auto-fixes from zizmor findings.Jacob Walls
2025-11-21Added GitHub Actions linter (zizmor).Jacob Walls
At the direction of the Security Team. Thanks Markus Holtermann, Jake Howard, and Natalia Bidart for reviews.
2025-11-11Refs #35844 -- Ran further selenium tests with --parallel=1.Jacob Walls
2025-11-11Refs #35844 -- Ran selenium tests with --parallel=1.Jacob Walls
2025-11-10Fixed unsafe variable interpolation in GitHub Action workflow.Markus Holtermann
Thank you Davide Netti for the report and initial patch. Co-authored-by: Davide Netti <davide.netti4@gmail.com>
2025-10-22Refs #36664 -- Added Python 3.15 to daily builds.Mariusz Felisiak
2025-10-17Refs #35844 -- Doc'd Python 3.14 compatibility.Mariusz Felisiak
2025-10-16Bumped minimum isort version to 7.0.0.Jacob Walls
Added ignores relating to https://github.com/PyCQA/isort/issues/2352.
2025-10-15Fixed parameter names in in "New contributor" GitHub action.Mariusz Felisiak
Follow up to 407ab793573ce82c93cfdc86e5a0a7fa804f60f5.
2025-10-14Removed setuptools from GitHub actions.Jacob Walls
Follow-up to 61c5c3173281b1e906a891aa6a6c6f9cdc9f2b8a.
2025-10-14Pinned "New contributor" GitHub action to v1.Jacob Walls
Later versions misidentify all contributors as new ones if the project does not enable issues. Follow-up to b7507bad7730e5f6558cfcce29976f65890083ca.
2025-10-08Refs #36595 -- Extended "postgis" GitHub Action to run against PostGIS 3.6.Chris Muthig
Changed image exercise these versions: * latest: POSTGIS="3.5.2 dea6d0a" PGSQL="170" GEOS="3.9.0-CAPI-1.16.2" PROJ="7.2.1" * 17-master: POSTGIS="3.7.0dev 3.6.0rc2-55-gfda22140e" PGSQL="170" GEOS="3.15.0dev-CAPI-1.21.0" PROJ="9.8.0" * 18-3.6-alpine: POSTGIS="3.6.0 0" PGSQL="180" GEOS="3.13.1-CAPI-1.19.2" PROJ="9.6.0"
2025-10-07Added required "issue_message" input to "New contributor" GitHub action.Tim Kamanin
2025-10-03Fixed #36623 -- Dropped support for PostgreSQL 14 and PostGIS 3.1.Mariusz Felisiak
2025-09-29Added PostgreSQL 18 to scheduled tests workflow.Mariusz Felisiak
2025-09-23Fixed warning in "New contributor" GitHub action.Mariusz Felisiak
2025-09-12Bumped versions in Github actions configuration.Mariusz Felisiak
2025-08-27Added matrix with newer image versions to the "postgis" GitHub Action.Natalia
This work allows to test three types of postgis Docker images to cover a wider spectrum of geo libraries versions: * `latest` (recommended upstream): uses latest stable Debian packages. These versions are generally conservative, so they may lag behind. * `alpine`: build PostGIS from source on Alpine, and ship newer geospatial libs. * `master`: provides development versions, therefore coverage for what's coming. Future compatibility issues can be caught in advance. This split is important because each image differs significantly in GEOS/PROJ/GDAL versions, so testing all increases confidence in compatibility. More info at https://hub.docker.com/r/postgis/postgis/. For example, at the time of this branch: * latest stable in debian: * POSTGIS="3.5.2 dea6d0a" * GEOS="3.9.0-CAPI-1.16.2" * PROJ="7.2.1" * latest stable in alpine: * POSTGIS="3.5.3 0" * GEOS="3.13.1-CAPI-1.19.2" * PROJ="9.6.0 * latest development branch: * POSTGIS="3.6.0dev 3.6.0beta1-29-g7c8cfe07d" * GEOS="3.14.0beta2-CAPI-1.20.1" * PROJ="9.7.0"
2025-08-27Ensured apt repo is updated before installing deps in "postgis" GitHub Action.Natalia
2025-08-25Fixed #36485 -- Added lint-docs check in Tox and GitHub Actions.David Smith
The `check` docs target now runs spelling, black, and lint, so all current documentation quality checks can be run with a single command. Also documented the lint-docs check's availability and usage.
generated by cgit v1.3 (git 2.53.0) at 2026-05-01 19:09:50 +0000