For this CI/CD process to work, we don't want the developers to be able to commit changes in the DEV workspace to GIT directly. Rather, we rely on them creating a new branch out of "main" and attaching it to their isolated workspaces, and merge the changes ONLY via PR.
This task is to update the README.md to include instructions about locking the branch which is linked to DEV workspace using branch policies.
This is related to #712.
For this CI/CD process to work, we don't want the developers to be able to commit changes in the DEV workspace to GIT directly. Rather, we rely on them creating a new branch out of "main" and attaching it to their isolated workspaces, and merge the changes ONLY via PR.
This task is to update the README.md to include instructions about locking the branch which is linked to DEV workspace using branch policies.
https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops&tabs=browser#can-i-push-changes-directly-to-branches-that-have-branch-policies
@FYI @ydaponte