[Django] #30968: Use github actions for linting

9 views
Skip to first unread message

Django

unread,
Nov 9, 2019, 7:12:02 AM11/9/19
to django-...@googlegroups.com
#30968: Use github actions for linting
---------------------------------------------+------------------------
Reporter: Tom Forbes | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
Lets implement our linting checks as Github Actions to see how they
perform and if they are stable enough. This can guide the discussion about
adding more tests to Actions in the future.

Mailing list discussion:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic
/django-developers/xDCmZPLTOQQ

Side note: It's possible we need an additional Component in Trac for CI,
that's separate from the Testing Framework one?

--
Ticket URL: <https://code.djangoproject.com/ticket/30968>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Nov 11, 2019, 2:00:42 AM11/11/19
to django-...@googlegroups.com
#30968: Use github actions for linting.
-----------------------------------+--------------------------------------

Reporter: Tom Forbes | Owner: nobody
Type: New feature | Status: closed

Component: Testing framework | Version: master
Severity: Normal | Resolution: duplicate

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by felixxm):

* status: new => closed
* resolution: => duplicate


Comment:

I think that a single ticket to trace GitHub actions is enough. I'm going
to play with them in the near future (maybe in this week).

Duplicate of #30962.

--
Ticket URL: <https://code.djangoproject.com/ticket/30968#comment:1>

Reply all
Reply to author
Forward
0 new messages