In Azure Repositories, maintain owner when changing PR to gs-pipelines
When dealing with Azure Repository, the owner of the gs-pipeline PR is always the user used for authentication. Any way to include the original owner would be helpful since the messaging is lost this way
Kajetan
shared this idea
-
Jason Flammang
commented
This would be really great! As an alternative, even the ability to configure a pipeline with a custom Git credential or separate Azure connection so that we could leverage a service account in Azure for performing all of the pipeline automation (promotion branch creation, promotion branch syncing with feature branch, etc.). Currently I have to use my own Azure connection for configuring the pipeline. I like to use my own credentials when tagging work items in a deployment, but for automated actions it would be great to perform that with credentials for a separate service account in Azure so that everyone can distinguish between Git actions taken by a user and automated actions taken by Pipelines.