Hi,
Starting scenario:
You have a branch called Development and a workspace linked to this branch. The workspace has many notebooks.
On Azure DevOps, you create a new branch called MyNewFeature, based on the Development branch.
On the workspace, you make some changes on the notebooks. Basically, you drop some code you don't want in the Development branch yet. You are confident you have this code in the MyNewFeature branch, to continue the work there.
You commit the changes to the Development Branch.
On Power BI portal, you go on Workspace Settings -> Git Integration and change the branch from Development to MyNewFeature in order to continue your work.
The notebook you changed will not be updated from the branch. It will be considered modified and requiring a commit. There is no option to make a pull (not that I have identified). In this way, you don't have "access" in the workspace to the code you need.
If you commit the notebook to the server, the only option provided, you "lose" the code you built. You will need to dig the devOps history to retrieve the code again.
The portal should:
A) Make the checkout of the new branch silently, without comparing a previous branch with the new one. OR
B) At least ask if we would like to override the content of the workspace or the content of the branch. I discovered the portal makes this question if we link a workspace which had no source control before and is not empty with a branch in source control which is not empty. This question would be useful.
on:
URGENT!! Paginated Report not loading on Mozilla F...
mattlee
on:
“Add Value” in Textbox Not Visible in Dark Theme
on:
Bi Crashes on launch with (AS Process PID=XXXXXX H...
on:
Fix the Date function in DAX