az repos pr create --delete-source-branch

[erikrok]

Describe the bug

In a CI/CD workflow in Azure Releases, I automatically create a PR after a stage.
When this PR is approved and completed, I want it to be automatically be deleted, and set the flag --delete-source-branch true.
Documentation explains:
Delete the source branch after the pull request has been completed and merged into the target branch.

The PR get created successfully, but the branch is not deleted when I complete the PR.

Note that this PR is created as the user Project Collection Build Service ({OrgName}), using the:
environment token in Azure Releases:
AZURE_DEVOPS_EXT_PAT and $(System.AccessToken)

Related command

az repos pr create \
   --project ProjectName \
   --organization https://dev.azure.com/Project/ \
   --repository RepositoryName \
   --delete-source-branch true \
   --source-branch $BRANCH_NAME \
   --target-branch main \
   --title "Title $BUILDID, release $RELEASENAME, $(date +%Y%m%d%H%M)" \
   --reviewers "areviewer@foo.com"
   --description "Deployed $(date -I)" "ref: $BUILD_COMMIT"

Errors

no errors

Issue script & Debug output

cli.knack.cli: Command arguments: ['repos', 'pr', 'create', '--project', 'Project', '--organization', 'https://dev.azure.com/Organization/', '--repository', 'ProjectBackend', '--delete-source-branch', 'true', '--source-branch', 'testing_pr_loc', '--target-branch', 'testing_pr', '--title', 'TESTING', '--reviewers', 'foo@bar.com', '--description', '- Deployed Synapse to prod 2023-09-29', 'testing', '--debug']

Expected behavior

I expect that the branch will be deleted after the PR has been completed, as documentation says.

Environment Summary

bash script, running in a Bash@3 - Bash v3 task

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[sb1975]

We are also impacted by this.

[ThisIsLNo]

+1 impacted :(

[FFraterBizeta]

Hi all, I also notice the same issue with Azure DevOps UI (I think that the UI use APIs too).
The source branch is never deleted.

[darrenswart]

Not sure if your situation is similar or not but in my case, the issue was the user Project Collection Build Service ({OrgName}) did not have the permission to delete branches. To resolve this, I had to grant the user Project Collection Build Service ({OrgName}) the Allowed permission to Force push (rewrite history, delete branches and tags) in the security settings for the impacted repo. Once this was done the source branch would get automatically deleted once the PR was approved and merged.

[in-fke]

For the love of god, what is this with these long pending bugs?