-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow approver to complete manual merge activities #82
Conversation
Closes #81. |
@ewingjm Thanks for reviewing. I think you need to manually trigger the checks? |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@tdashworth would you mind adding this into the power-apps-bindings.yml? browserOptions:
driversPath: ChromeWebDriver Should fix the error you're getting on the pipeline. I was going to just bypass the policy and merge this as I know it doesn't impact the few tests that are there but I realised we'll just get the same error on the CI run and we won't get a release published. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tdashworth.
Purpose
On our project, the user approving the Solution Merge will often also carry out the manual steps (documented in a Note). The problem is that only the creator of the Solution Merge Request can confirm these have been done via an Approval.
#81
Approach
Allows both creator and approver to complete the manual merge activities.
TODOs