Support comma-separated rules in # clint: disable= comments#20651
Merged
Support comma-separated rules in # clint: disable= comments#20651
# clint: disable= comments#20651Conversation
- Updated DISABLE_COMMENT_REGEX to match comma-separated rule names - Modified ignore_map() to split and process multiple rules - Added comprehensive tests for single/multi-rule and spacing variants - Updated README with multi-rule syntax examples - Fixed lint issues (added return type annotations, removed single-line docstrings) Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Renamed test_ignore_map_mixed_spacing to test_ignore_map_handles_various_spacing_around_commas for better descriptiveness Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update clint regex to support multiple rules in disable comment
Support comma-separated rules in Feb 8, 2026
# clint: disable= comments
harupy
approved these changes
Feb 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues/PRs
N/A
What changes are proposed in this pull request?
The
# clint: disable=comment only disabled the first rule when multiple comma-separated rules were specified (e.g.,# clint: disable=rule1,rule2only disabledrule1). The regex pattern captured a single rule name and ignored everything after the first comma.Changes:
DISABLE_COMMENT_REGEXto match comma-separated rule names:([a-z0-9-]+(?:\s*,\s*[a-z0-9-]+)*)ignore_map()to split captured group on commas and strip whitespaceNOQA_REGEXimplementationExample:
How is this PR tested?
Added 6 unit tests for
ignore_map()covering single-rule, multi-rule, spacing variations, and 1 integration test verifying end-to-end linting behavior.Does this PR require documentation update?
Updated
dev/clint/README.mdwith comma-separated syntax example.Does this PR require updating the MLflow Skills repository?
Release Notes
Is this a user-facing change?
The
# clint: disable=comment now supports comma-separated rule names to disable multiple linter rules on a single line (e.g.,# clint: disable=rule-a,rule-b).What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.