A developer has successfully configured their credentials for Databricks Repos and cloned a remote Git repository. They do not have privileges to make changes to the main branch, which is the only branch currently visible in their workspace.
Which approach allows this user to share their code updates without the risk of overwriting the work of their teammates?
To share code updates without the risk of overwriting teammates' work, the developer should use Repos to create a new branch, commit all changes, and push changes to the remote Git repository. This approach allows the developer to keep the main branch untouched while working on their updates. After pushing the changes to the new branch, they can then create a pull request, enabling their teammates to review the changes before they are merged into the main branch. This method ensures the main branch remains stable and prevents any accidental overwrites.
This is a common workflow in collaborative development environments. The developer can create a new branch in their local repository, make changes, and then push the branch to the remote repository. This way, they can share their updates without modifying the main branch directly. After pushing the changes, they can create a pull request on the remote repository, allowing their teammates to review the changes before merging them into the main branch. This process ensures that the main branch remains stable and that all changes are reviewed and approved before they’re incorporated. It also prevents any accidental overwrites of teammates’ work.
E is the regular collaboration approach. B makes a fork so breaks away from the collaborating teamates. There's no way they can make a pull request on the source repository after making change to a fork.
Sorry, my mistake, just tested B is a do-able way. Fork from github can create pull request against the original repository and contribute back. B seems to be a better answer.
Databricks Repos itself does not currently support creating forks directly within the platform. However, you can achieve a similar workflow using the following steps: Use the git clone command in a terminal or IDE to create a local copy of the remote repository. This effectively creates a local fork. Make your changes in the local copy. Use git push to push your changes to a new remote repository you create on a Git hosting service like GitHub. Create a pull request from your new remote repository to the original repository on Databricks Repos. This approach allows you to make changes to your own copy of the code, collaborate with others through code reviews, and propose your changes for integration into the main branch without directly modifying it
Databricks Repos cannot be used to fork a repository
E is correct
B is correct
B is correct
E is correct if you create a fork you create another repository so not B
Isn't this B?