-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
CI: only run pylint in CI #49526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Could I attempt resolving this issue? I'm mostly a beginner as of now. |
sure, PRs welcome, here's the contributing guide https://pandas.pydata.org/docs/development/contributing.html |
By the way is it |
no |
Oh sorry. I just realised that looking at https://pre-commit.com/ |
Please provide feedback on the PR #49527 . I need to learn more about the processes I guess. |
pylint is helping unearth some issues, but it's quite slow, especially for local development
as brought up on Slack by @jorisvandenbossche , let's just run it in CI instead
Task would be:
pandas/.pre-commit-config.yaml
Lines 62 to 65 in 57d8d3a
add
pandas/.github/workflows/code-checks.yml
Lines 89 to 93 in e02133c
The text was updated successfully, but these errors were encountered: