Related Issues/PRs

#xxx

What changes are proposed in this pull request?

The clint linter appended "See dev/clint/README.md for instructions on ignoring this rule (<rule_name>)." after each error, creating excessive verbosity with multiple violations.

Changes:

• Removed README reference from individual Violation.__str__() output in linter.py
• Added single README message after error count in __init__.py with proper singular/plural grammar
• Combined the error count and README instruction into a single print() statement for cleaner code

Before:

file.py:2:1: MLF0003: Unordered parameters See dev/clint/README.md for instructions on ignoring this rule (docstring-param-order).
file.py:12:1: MLF0003: Unordered parameters See dev/clint/README.md for instructions on ignoring this rule (docstring-param-order).
Found 2 errors

After:

file.py:2:1: MLF0003: Unordered parameters
file.py:12:1: MLF0003: Unordered parameters
Found 2 errors
See dev/clint/README.md for instructions on ignoring these rules.

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

All 189 clint tests pass. Manually verified output for single error, multiple errors, and no errors cases.

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

Clint linter now shows README instructions once after the error summary instead of repeating them on each error line, reducing output verbosity.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How 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" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.