You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implementation of a pylint linter workflow will help to ensure proper and uniform linting of the codebase.
Pitch
As a project with multiple users contributing to it, it is essential to maintain a proper linting style to ensure better code readability by users. An excellent way to do this is by automatic linting checks using GitHub actions. So, I would propose adding the pylint linter workflow to ensure proper and uniform linting of the codebase.
I would like to work on this feature as a part of GSSoC 23.
Restart triage: P2 — useful developer tooling, after test CI. The inspected repository has no pylint workflow; existing GitHub workflows cover scanning and greetings rather than a dedicated lint/test pipeline.
Next step: coordinate with #190 and choose one small lint policy shared by local checks and CI. Start with a manageable baseline rather than a repository-wide formatting rewrite; get the offline test gate in #50 working first.
Source/configuration review only; no linter was run. Keeping the issue open.
Activity
[-]Add the black linter workflow [/-][+]Add the pylint linter workflow [/+]GouravSardana commentedon Oct 21, 2026
Restart triage: P2 — useful developer tooling, after test CI. The inspected repository has no pylint workflow; existing GitHub workflows cover scanning and greetings rather than a dedicated lint/test pipeline.
Next step: coordinate with #190 and choose one small lint policy shared by local checks and CI. Start with a manageable baseline rather than a repository-wide formatting rewrite; get the offline test gate in #50 working first.
Source/configuration review only; no linter was run. Keeping the issue open.