Shallow git fetch before mlflow run

[marijncv]

Signed-off-by: Marijn Valk marijncv@hotmail.com

What changes are proposed in this pull request?

This PR updates the project run utils such that it fetches the user code repository with depth=1. This is a small optimization to reduce the size of the .git folder in the repository that is cloned (and subsequently sent to dbfs when running on Databricks backend). The revisions are not needed when running a project.

How is this patch tested?

Used the mlflow run command with a git repository uri. Tested with and without version specified.

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/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• 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/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

Interface

• 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

Language

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

Integrations

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

How should the PR be classified in the release notes? Choose one:

• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• 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/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

[harupy]

@marijncv I locally tested this PR using our example repo and it worked!

[harupy]

LGTM

[harupy]

@marijncv Can you fix the lint error?
https://github.com/mlflow/mlflow/pull/4838/checks?check_run_id=3745168686#step:4:21

tests/projects/test_utils.py (7,0): [W0611 unused-import] Unused ExitStack imported from contextlib as does_not_raise

[marijncv]

@harupy, I removed the unused import. Thanks for the review!

[adeandrade]

@harupy @marijncv This PR is causing issues. We cannot run anything but the latest commit. Can we revert or increase GIT_FETCH_DEPTH to something reasonable?

See: #5301