You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always To analyze at the time of the pull request what was being planned in the plan I would go to the pipeline task. to be able to approve
Describe the solution you'd like
Something easier to analyze and approve the pull request
Describe alternatives you've considered
I would like a comment on Azure Devops, at the time of the pull request
Additional context
I have already created it for my use, and I would like you to check if it can be part of the package.
The comments.yaml file is inside the templates directory, and after the plan we call comments.yaml and it will only be triggered if it is a pull request, as it will comment on the result of the Plan.
This is LOVELY @EdersonSC
We actually just created a new extended reporting feature in the hydration kit , and this is a good amount of the json conversion work that I was anticipating. I'll get this into the next release, I think. It shouldn't be a big lift.
@EdersonSC Also, you may want to check out the Build-HydrationDeploymentPlans -ExtendedReporting Feature. If you do, please let us know what you think?
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always To analyze at the time of the pull request what was being planned in the plan I would go to the pipeline task. to be able to approve
Describe the solution you'd like
Something easier to analyze and approve the pull request
Describe alternatives you've considered
I would like a comment on Azure Devops, at the time of the pull request
Additional context

I have already created it for my use, and I would like you to check if it can be part of the package.
The comments.yaml file is inside the templates directory, and after the plan we call comments.yaml and it will only be triggered if it is a pull request, as it will comment on the result of the Plan.
Please change the extension from Json to Yaml
comments.json
The text was updated successfully, but these errors were encountered: