Explanation:
In Databricks Repos, the branch selection dropdown only displays branches that are known to the local workspace. If a branch like dev-2.3.9 was recently created or updated on the remote repository (e.g., GitHub, GitLab, or Azure DevOps), it will not appear in the dropdown until the local repository fetches the latest metadata from the remote.
Why B is correct:
Performing a Fetch (often triggered by the 'Pull' or refresh actions in the Git dialog) updates the local environment's view of all available remote branches. Once the fetch is complete, the dev-2.3.9 branch will become visible in the menu, allowing the developer to switch to it and review the code.
Why other options are incorrect:
Ultimate access to all questions.
A junior data engineer is working within a Databricks Repos notebook on a personal branch containing outdated logic. They need to review the latest code in the dev-2.3.9 branch; however, this branch is not appearing in the branch selection dropdown.
What is the correct approach to allow the developer to review the current logic in the dev-2.3.9 branch?
A
Merge the personal branch with dev-2.3.9 and create a pull request to synchronize with the remote repository.
B
Fetch the latest changes from the remote Git repository and then switch to the dev-2.3.9 branch once it appears.
C
Use the Databricks REST API to create a pull request and force the Repos environment to update to dev-2.3.9.
D
Check out the dev-2.3.9 branch using the Git CLI to automatically resolve any merge conflicts with the current branch.
No comments yet.