A team has finished a feature on a branch in a Databricks Git Folder and has committed and pushed it. Governance requires that the code reaching main is approved by two reviewers and that the approval record lives with the repository, alongside the branch protection rules the team already maintains. An engineer asks how the merge itself should be carried out. Which statement is correct?
- AThe Git dialog merges the feature branch into main inside the workspace once the required reviewers have added their approval in the dialog, and it then pushes the merge commit to the provider.
- BThe engineer checks out main in the Git Folder, copies the notebooks across from the feature branch checkout, and commits the result to main so that the reviewers can read the diff afterwards.
- CThe Git dialog links out to the Git provider to open a pull request, and the review and merge take place there, after which the folder is brought up to date by checking out main and pulling. Correct
- DThe team should schedule a Lakeflow Job that runs a notebook calling the provider's merge endpoint, because the workspace UI offers no route from a pushed branch to a pull request.
Why A is wrong: It sounds reasonable because the dialog does handle branches, commits and pushes, but Databricks does not host code review, and approvals are recorded by the provider.
Why B is wrong: Copying files does produce the same content on main, which makes it look equivalent, but it bypasses the pull request and so leaves no approval record and defeats branch protection.
Why C is correct: Databricks Git Folders integrate with the provider rather than replacing it, so approvals and the merge happen in the provider and the workspace copy is refreshed with a pull.
Why D is wrong: Automating a provider call is technically possible, so it reads as thorough, but it is unnecessary bespoke work and its premise about the UI having no route is wrong.