Is your feature request related to a problem? Please describe.
Currently when the pipeline task adds a PR comment, it defaults the state to "Active".
However some users have pipelines that only pass once the PR comment is set to "Resolved."
Describe the solution you'd like
So offering an option that can be set for the task extension to specify the default behavior is desired.
Optimally, the choices would allow for "Active", "Pending", "Resolved", "Closed" which match the allowed options in ADO (skipping "Won't Fix")
And the default should be "Resolved" to minimize the impact on processes and pipelines related to the automatically added comments.
Describe alternatives you've considered
None.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. Currently when the pipeline task adds a PR comment, it defaults the state to "Active". However some users have pipelines that only pass once the PR comment is set to "Resolved."
Describe the solution you'd like So offering an option that can be set for the task extension to specify the default behavior is desired. Optimally, the choices would allow for "Active", "Pending", "Resolved", "Closed" which match the allowed options in ADO (skipping "Won't Fix") And the default should be "Resolved" to minimize the impact on processes and pipelines related to the automatically added comments.
Describe alternatives you've considered None.
Additional context Add any other context or screenshots about the feature request here.