-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Description
It seems like the automerge flag on the deploy parameter doesn't work as expected on Azure Devops:
deploy --single-commit --create-pr --auto-merge --merge-method 'squash'
shows this in the logs:
INFO clone: Cloning repository: https://dev.azure.com/xxx/yyy/_git/zzz
INFO new_branch: Creating new branch: gitopscli-deploy-65db50ce
INFO __update_values: Updated yaml property application.image.tag to b83c978a23ec69d745bdcaf6bb95a89090840a17
INFO commit: Creating commit with message: changed 'application.image.tag' to 'b83c978a23ec69d745bdcaf6bb95a89090840a17' in values.yaml
INFO push: Pushing branch: gitopscli-deploy-65db50ce
INFO create_pull_request_to_default_branch: Creating pull request from 'gitopscli-deploy-65db50ce' to default branch with title: Updated value in values.yaml
INFO merge_pull_request: Merging pull request 31048
INFO delete_branch: Deleting branch 'gitopscli-deploy-65db50ce'
But the PR is still active and the source branch was deleted. Shouldn't the branch be deleted by the PR merge instead of separately deleting the branch? Any build validation pipeline will probably prevent this from working.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels