* Fix test migrations for django-taggit 3.0.0 (forthcoming)
The next release of django-taggit [will change slugs to allow_unicode=True](https://github.com/jazzband/django-taggit/pull/797), which breaks our check for missing migrations.
This change is not released yet, but the fix is needed now so that we can run against django-taggit git master for our tests against Django main. It's also dependent on the version bump happening at the django-taggit end: https://github.com/jazzband/django-taggit/pull/800
* Allow django-taggit 3.x as a dependency and drop special case when testing against Django main
let's revisit this optimization in a different PR, since there is no
explicit requirements.txt in the project as such. We will need a slighly
different approach with this.
Authored-by: Vinit Kumar <vinit.kumar@kidskonnect.nl>
Signed-off-by: Vinit Kumar <vinit.kumar@kidskonnect.nl>
Github actions have a new release and pip cache was not enabled.
Both of these will make the CI run faster.
Authored-by: Vinit Kumar <vinit.kumar@kidskonnect.nl>
Signed-off-by: Vinit Kumar <vinit.kumar@kidskonnect.nl>
This improves the CI experience as it will run the github checks in a
group and at the same time cancel in progress jobs if a new commit is
pushed for the pull request.
No only does it makes the contributing experience nice, but it also
saves tonnes of energy.
- Github Issue: #8276
Authored-by: Vinit Kumar <vinit.kumar@kidskonnect.nl>
Signed-off-by: Vinit Kumar <vinit.kumar@kidskonnect.nl>
* update github bug template to have status:Unconfirmed
- by default, ensure that all new bugs are raised with the label status:Unconfirmed
- for the bug template where 'hints' exist - use HTML comments to hide these
* docs - update issue tracking
- convert from RST to markdown
- add details about when to use Github discussions instead of an issue
- add details about bugs will be raised with the status:Unconfirmed
- add link to PR triage guide
- add links to release schedule & roadmap
- put less emphasis on milestones for new issue creation
* Upgrade mysql to 8.0.23 for github actions
* Fix thumbnail_url migration to work on Django 3 / MySQL 8.0.13+
Work around https://code.djangoproject.com/ticket/32503 by applying the not-null constraint before converting to TextField.
This should result in the docs workflow only running if files in the
`docs/` folder have changed, and only run the test workflow if files NOT
in the `docs/` folder have changed.
This commit itself should therefore, I think, only trigger the test
workflow. I will follow up with test commits for the other scenarios
(docs-only and both).
Matt Westcott