Answer: Clone

## Explanation In Databricks Repos, you can perform most Git operations directly within the platform, including: - **Commit**: You can commit changes to your local repository - **Pull**: You can pull changes from the remote repository - **Push**: You can push changes to the remote repository - **Merge**: You can merge branches However, the **Clone** operation must be performed outside of Databricks Repos because: 1. **Initial Setup**: To create a Databricks Repo, you need to first clone a Git repository from an external Git provider (GitHub, GitLab, Bitbucket, etc.) using external Git tools or the Databricks CLI. 2. **Repo Creation Process**: When creating a new Repo in Databricks, you specify the Git URL, but the actual cloning happens during the repo creation process, not as a separate Git operation within the Repo interface. 3. **Workflow**: The typical workflow is: - Clone repository externally or use Databricks CLI - Connect it to Databricks Repos - Then perform all other Git operations within Databricks This is because Databricks Repos is designed to work with existing Git repositories that have already been cloned, rather than providing a full Git client for initial repository cloning operations.

Author: Keng Suppaseth