django-crispy-forms / django-crispy-forms/crispy-tailwind

Run Linters in Pipeline / Actions

Open
#158 8 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
423
Forks
64
PR merge metrics
No merged PRs in 30d

Description

Hi @smithdc1 and @carltongibson

am I wrong or don't we validate the linting rules in our CI pipeline?

![grafik](https://github.com/django-crispy-forms/crispy-tailwind/assets/3176075/d56dff74-c3e3-4821-95fa-89d540445dcb)

There is something in the per-pyhton-version setup but apparently, it's not being executed.

Futhermore, linting should / can be checked version-independly, right?

What's your take on this?

Best
Ronny

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the existing GitHub Actions pipeline, especially the per-Python-version setup mentioned in the issue, and identify whether the linting step is actually executed. Run the current workflow checks and confirm that linting is validated independently of the Python-version matrix. Done means the pipeline visibly runs the lint checks and reports failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
ci-cd, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.