Forum Discussion
Azure Dev Ops integration - pull only
Hi, ells69
May I ask if you have gotten this issue resolved? If it is solved, please share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.
If not, please provide more details about the problem you are experiencing and we will do our best to solve the problem you are experiencing.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I dont think it has been answered. This is quite project critical. The same code will be pushed \pulled to multiple workspaces.
What I am trying to guard against is someone who is using one worksapce pusheing changes back to source control. This will then get pulled into the other workspaces and could have really bad effects and we would be left with a mess.
I cant believe that if you grant read access only in Dev Ops Source control this can be over written by Fabric.
This makes no sense whatsoever.
Nobody so far has said that if you use an account with read only access in Dev Ops then it will neve get updated. That surprises me. Just means it is a free for all now to mess up the code in source control.
