Not a valid question anymore since, Databricks Repos can now perform:
• Clone, push to, and pull from a remote Git repository.
• Create and manage branches for development work, including merging, rebasing, and resolving conflicts.
• Create notebooks (including IPYNB notebooks) and edit them and other files.
• Visually compare differences upon commit and resolve merge conflicts.
Option D - Clone.
The Clone operation must be performed outside of Databricks Repos. Cloning a repository involves creating a copy of an existing remote repository to a local machine. In the context of Databricks, you would typically clone the repository to your local development environment first and then connect it to the Databricks repos
The reason D. Clone is the correct answer is because cloning a repository involves creating a copy of the entire repository, including all of its history, branches, and files, on your local machine. This operation is typically performed outside of Databricks Repos, using Git commands in a terminal or a Git client.
On the other hand, operations like Commit, Pull, Push, and Merge can be performed within Databricks Repos, as they involve interacting with the repository's content and history that is already cloned and available in the Databricks environment.
D. Clone
Cloning a repository creates a local copy of the repository on your machine and must be done using a local Git client or command line. Once the repository is cloned, you can work with it in Databricks Repos, but the initial clone operation itself is outside the Databricks interface. Other operations like commit, pull, push, and merge can be managed within Databricks Repos or through other Git tools.
D: Cloning a repository is typically done outside of Databricks Repos, often using a Git client or command line interface before the repository is linked to Databricks Repos.
Why not option B Pull
The following tasks are not supported by Databricks Repos, and must be performed in your Git provider:
Create a pull request
Delete branches
Merge and rebase branches *
Pull is not the same as pull request. Pulls are updating local version of the repo to the one present on remote. And it's surely feasible in Databricks repos.
i think it supports merge now
https://docs.databricks.com/en/repos/git-operations-with-repos.html
"If an operation such as pull, rebase, or merge causes a merge conflict, the Repos UI shows a list of files with conflicts and options for resolving the conflicts.
You have two primary options:
Use the Repos UI to resolve the conflict."
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ZSun
Highly Voted 1 year, 10 months agoTedet
3 months, 2 weeks agoNickWerbung
Highly Voted 1 year, 7 months agoSoumyaHK
Most Recent 23 hours, 40 minutes agodevbila
4 weeks agochinhuy
1 month, 2 weeks agosakis213
3 months, 1 week agodanishanis
3 months, 3 weeks agoMultiCloudIronMan
4 months, 1 week agopeadar_pa
5 months, 4 weeks ago9d4d68a
8 months ago80370eb
8 months, 2 weeks agoIsio05
12 months agoItmma
1 year, 1 month agoBob123456
1 year, 2 months agoIsio05
12 months agovvg130
1 year, 3 months agoSerGrey
1 year, 4 months agonedlo
1 year, 4 months ago