Related Issues/PRs

Relates to #issue_number

What changes are proposed in this pull request?

All i18n JSON files in mlflow/server/js/src/lang/ are auto-generated and create noise in PR diffs. Added linguist-generated=true attribute in .gitattributes with a wildcard pattern to collapse all of them by default in GitHub PR views.

# Collapse auto-generated Python stub files in pull request diffs on GitHub
mlflow/protos/**/*.pyi linguist-generated=true

+# Collapse auto-generated i18n files in pull request diffs on GitHub
+mlflow/server/js/src/lang/**/*.json linguist-generated=true

This covers en.json (generated by extract-i18n.js) as well as all other language translation files (de-DE.json, es-ES.json, fr-FR.json, it-IT.json, ja-JP.json, ko-KR.json, pt-BR.json, pt-PT.json, zh-CN.json, zh-HK.json, zh-TW.json).

How is this PR tested?

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

Configuration change only - no functional impact. Verified using git check-attr that the wildcard pattern correctly matches all JSON files in the lang directory.

Does this PR require documentation update?

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

Does this PR require updating the MLflow Skills repository?

• No. You can skip the rest of this section.
• Yes. Please link the corresponding PR or explain how you plan to update it.

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.

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)

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.