Error on branch creation

[MaggyLarsen]

2020-08-05T15:23:04.3535930Z ##[error]You must grant the build account access to permission: Create Branch
2020-08-05T15:23:04.3548889Z ##[error]If you need to change permissions see: _admin/_versioncontrol?_a=security&repositoryId= ....
2020-08-05T15:23:04.3551387Z ##[error]Unable to create ref: heads/Release-18 UpdateStatus: 8 RepositoryId: ....

All Permissions seem to be fine in devops.

[MaggyLarsen]

Can be be because of the path? It's missing the refs in it.. when i echo a source path is returns : refs/heads/release
wouldn't it be better if we specify the full path to the repo ?

[MaggyLarsen]

After a day of struggles.. Seems more like an authorization issue on the running build agent. had same issues with other tasks. This can be ignored. Thanks.

[TASlavens]

All Permissions seem to be fine in devops.

One thing people commonly forget about is the Git repo object permissions for the "Project Collection Build Service":

https://docs.microsoft.com/en-us/azure/devops/organizations/security/permissions?view=azure-devops-2019&tabs=preview-page#git-repository-object-level

https://docs.microsoft.com/en-us/azure/devops/organizations/security/set-git-tfvc-repository-permissions?view=azure-devops-2019#set-git-repository-permissions

If you're not using on-prem AzDOS 2019, switch the MS doc view to your version with the version selector at the upper left (people forget about this, too). The relevant permissions for this extension should be "Create tag" and "Create branch", and for your error log, the latter. These permissions are scoped to the AzDOS/TFS team project, so you have to set these permissions to "Allow" for the Git repo container in each project. If a project doesn't have a Git repo yet, you cannot set the top-level permissions until one is created (might be fixed in cloudy AzDOS or AzDOS 2020 RC1). Also, disabling permission inheritance can really mess with your head when diagnosing permission problems - I recommend leaving it on in all cases unless there's a compelling reason to turn it off for a specific repo.