Skip to content

Fix the Lint job, which is failing on main - #218

Open
vahid-ahmadi wants to merge 1 commit into
mainfrom
fix/lint-on-main
Open

vahid-ahmadi wants to merge 1 commit into
mainfrom
fix/lint-on-main

Conversation

@vahid-ahmadi

Copy link
Copy Markdown

The Lint job is red on an untouched checkout of main, and therefore on every open pull request:

$ git checkout main && ruff format --check .
5 files would be reformatted, 83 files already formatted

pr_code_changes.yaml:19 installs ruff>=0.9.0 with no upper bound, which currently resolves to 0.16.7. That version formats Python inside markdown code blocks, which earlier versions left alone, so five files under docs/ became unformatted without anyone editing them.

The changes are cosmetic — single to double quotes, trailing commas — in fenced examples:

-common_variables = ['age', 'income', 'education', 'marital_status', 'region']
+common_variables = ["age", "income", "education", "marital_status", "region"]

This PR reformats the five files and bounds the constraint to >=0.9.0,<0.17.0, so a future ruff release changes the lint result only when someone chooses to move the pin.

No package code is touched. Worth merging before #214, #215, #216 and #217, whose Lint failures are all this and not their own contents.

The Lint job installs ruff>=0.9.0 with no upper bound. ruff 0.16.7
formats Python inside markdown code blocks, which earlier versions left
alone, so five documentation files under docs/ became unformatted
without anyone changing them. make check-format fails on an untouched
checkout of main, and therefore on every open pull request.

Reformats the five files and gives the constraint an upper bound, so a
future ruff release changes the lint result only when someone chooses to
move the pin.
@vercel

vercel Bot commented Sep 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
microimpute-dashboard Ready Ready Preview Sep 16, 2026 12:14pm UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant