summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2025-10-17[6.0.x] Refs #35844 -- Doc'd Python 3.14 compatibility.Mariusz Felisiak
Backport of 56977b466c33ca3da14a1ed2609172425a76a34e from main.
2025-10-16[6.0.x] Bumped minimum isort version to 7.0.0.Jacob Walls
Added ignores relating to https://github.com/PyCQA/isort/issues/2352. Backport of d980d68609448a4c85763fa34e471ff80540888b from main.
2025-09-23[6.0.x] Fixed warning in "New contributor" GitHub action.Mariusz Felisiak
Backport of 30e9b6f6adfed9ee4c1fa911956881a2361c8946 from main
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.
2025-08-08Improved docs.yml GitHub Action covering docs quality checks.David Smith
This change renames the `docs` job to `spelling` to better reflect its purpose. It also removes the unused `--keep-going` flag, since starting with Sphinx 8.1, `--keep-going` is enabled by default. See: https://www.sphinx-doc.org/en/master/man/sphinx-build.html#cmdoption-sphinx-build-keep-going
2025-07-16Fixed GitHub Action that checks commit prefixes to fetch PR head correctly.nessita
2025-07-16Added GitHub Action to enforce stable branch commit message prefix.nessita
2025-06-17Refs #36009 -- Added GitHub action workflow to run tests with latest stable ↵nessita
postgis version.
2025-04-23Skipped "Labels" Github action when not targeting the main django/django repo.Sarah Boyce
2025-01-28Pinned isort version to "<6.0.0" to avoid undesired reformat.nessita
2025-01-22Switched to pull_request_target event trigger in the Labels Github action.Sarah Boyce
The `pull_request` trigger runs in the context of the PR, and has limited access to information stored in the base repo django/django. As access is needed to the label "no ticket" in django/django, use the `pull_request_target` trigger.
2025-01-21Moved permissions setup to toplevel for the Labels Github action.nessita
2025-01-21Added GitHub action to label PRs without a ticket linked in title.Sarah Boyce
2025-01-20Fixed #36005 -- Dropped support for Python 3.10 and 3.11.Mariusz Felisiak
2024-11-27Upgraded to Python 3.12, Ubuntu 24.04, and enabled fail_on_warning for docs ↵David Smith
builds.
2024-10-25Made GitHub actions display all warnings in Python tests.Mariusz Felisiak
2024-10-16Refs #35844 -- Added Python 3.14 to daily builds.Mariusz Felisiak
2024-10-09Added GitHub Action workflow to test all Python versions listed in the ↵nessita
project config file.
2024-10-09Refs #34900 -- Added Python 3.12 to classifiers and tox.ini, and used it in ↵Mariusz Felisiak
GitHub actions.
2024-10-03Bumped latest PostgreSQL to 17 in scheduled tests workflow.nessita
2024-09-19Refs #35734 -- Added entry to scheduled tests workflow to test newer ↵nessita
PostgreSQL versions.
2024-09-13Pinned Miniforge in benchmark workflow.Sarah Boyce
2024-08-20Updated GitHub PR template headings to level 4.Marijke Luttekes
GitHub pull request descriptions are rendered as a comment. Comment titles, which include the PR author, render in a h3. Hence, titles within the comment body should be header level 4. This makes pull request descriptions more accessible to screen readers.
2024-07-31Removed GitHub Actions for creating and checking reminders.nessita
2024-05-27Fixed #35479 -- Dropped support for PostgreSQL 13 and PostGIS 3.0.Mariusz Felisiak
2024-05-10Organized images in the screenshots workflow.Nick Pope
Added a top-level directory in the zip archive that is the commit hash which makes it easier when downloading multiple artifacts for comparison. Updated the filenames of screenshots for easier comparison between different cases. Added that an error is raised if no screenshots uploaded in workflow.
2024-05-10Optimized images in the screenshots workflow.Nick Pope
Running `oxipng` over a set of screenshots from a previous run that were 1.9M in size resulted in a total size of 1.3M, a 31.5% reduction. This can be useful to reduce the artifact size stored in GitHub and locally if downloading screenshots from multiple runs. See https://til.simonwillison.net/github-actions/oxipng
2024-05-10Removed obsolete logic from screenshots workflow.Nick Pope
The id was used when we attempted to update comments in an early version of the feature. Also removed the job summary as it doesn't have the value that it did in the original version of the feature.
2024-04-24Pinned GitHub Actions for reminders to commit hashes for latest release.nessita
2024-04-24Improved phrasing and removed bold text in the GitHub pull request template.nessita
2024-03-18Stopped using byte-compiled 3rd-party packages in daily builds for ↵Mariusz Felisiak
byte-compiled Django.
2024-03-04Added a GitHub pull request template.erosselli
Co-authored-by: Natalia <124304+nessita@users.noreply.github.com> Co-authored-by: Paolo Melchiorre <paolo@melchiorre.org> Co-authored-by: Adam Johnson <me@adamj.eu>
2024-02-22Added GitHub Actions to create and check for reminders in pull requests.nessita
2024-02-21Refs #30950, Refs #35187 -- Added tests for byte-compiled Django to daily ↵Jon Janzen
builds.
2024-01-26Bumped versions in Github actions configuration.Mariusz Felisiak
2023-12-15Fixed database connection for other alias in PostgreSQL tests on GitHub Actions.Nick Pope
2023-12-13Removed unnecessary write permission from screenshots Github workflow.Tom Carrick
2023-12-12Changed the screenshots Github workflow to run in the PR's branch by using ↵Tom Carrick
pull_request as event trigger. The original event trigger pull_request_target runs against the target branch (main), not the branch associated with the PR. Consequently, any new screenshots added in a PR are not captured, and the available screenshots reflect the state of the main branch code, not the code from the PR's branch. This update addresses the issue by changing the event trigger to pull_request. However, it's important to note that this adjustment breaks the comments functionality since the action no longer has write permissions.
2023-12-07Refs #34986 -- Added PyPy 3.10 with PostgreSQL to daily builds.Nick Pope
2023-11-22Refs #34986 -- Installed libmemcached-dev in PyPy 3.10 daily builds.Mariusz Felisiak
2023-11-21Added PyPy 3.10 to daily builds.Mariusz Felisiak
2023-11-20Refs #34900 -- Added Python 3.13 to daily builds.Mariusz Felisiak
2023-11-18Refs #34118 -- Used Python 3.12 for GitHub actions.Mariusz Felisiak
2023-10-19Fixed permissions for GitHub action with screenshots.Mariusz Felisiak
Follow up to 97b7970c6479ef414175f22a009240ed0df8ce46.
2023-10-18Refs #34043 -- Added GitHub action to capture screenshots in Selenium tests.Sarah Boyce
2023-10-03Used Node.js 20 for GitHub actions.Mariusz Felisiak
2023-09-21Refs #34851 -- Used PostgreSQL 13 for selenium tests.Mariusz Felisiak
Follow up to 2c6ebb65c9eb6b11347d907127b82d31e04569e5.