[FR] Add support for automatically tracking git metadata without requiring MLflow Projects or MLflow Recipe

Willingness to contribute

No. I cannot contribute this feature at this time.

Proposal Summary

Add support for automatically tracking mlflow.source.git.branch or mlflow.source.git.repoURL without requiring MLflow Projects and MLflow Recipe. I believe this feature would greatly enhance the usability of MLflow.

Motivation

What is the use case for this feature?

The use case for this feature is to enable automatic tracking of Git metadata (branch and repository URL) for MLflow experiments, even when not using MLflow Projects and MLflow Recipe.

Why is this use case valuable to support for MLflow users in general?

This is valuable for MLflow users in general because it allows for more comprehensive tracking of experiment provenance and reproducibility.

Why is this use case valuable to support for your project(s) or organization?

For our project(s)/organization, this feature is crucial because we rely heavily on Git for version control and collaboration, and manual tracking of Git metadata is error-prone and time-consuming.

Why is it currently difficult to achieve this use case?

Currently, it is difficult to achieve this use case because MLflow only tracks Git metadata when using MLflow Projects or MLflow Recipe, which is not always feasible or desirable.

Reference https://mlflow.org/docs/latest/tracking/tracking-api.html#system-tags

Details

No response

What component(s) does this bug affect?

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

What interface(s) does this bug affect?

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

What language(s) does this bug affect?

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

What integration(s) does this bug affect?

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations