Azure DevOps pipeline shows error messages below while validating yml:

Here is the yml content which relates to Pull Request Utils:

      - task: PullRequestDescription@0
        name: RetrievePullRequestDescription
        inputs:
          action: 'view'
          outputVariable: 'PullRequest.DescriptionContent'
          isOutput: true
          stripIdentifiers: false

Extension has confirmed to be installed and has needed permission for build service

Is there any possible that I miss something?

This extension could use a rewrite to make maintaining it easier. Skipping V1 of tasks due to extension version 1 being used when open sourcing.

• Rewrite and introduce V2 of the tasks
• Add deprecation warnings to V0 tasks
  • Add option to disable warnings
• Add migration guide between versions

Since July, the task PullRequestComments creates a new PR comment with an invalid status Unknown in Azure DevOps.

With this invalid status, it's not possible to block a PR.

Task:

  - task: PullRequestComments@0
    displayName: 'Post a pull request comment reminder for checking the documentation'
    inputs:
      action: 'createOrUpdate'
      content: 'Please check if the changes on this PR needs some documentation update.'
      status: 'Active'
      commentId: 'pr-comment-documentation'
      useDefined: true
      pullRequestId: '${{ parameters.pullRequestId }}'
      type: 'System'

Task Log:

Starting: Post a pull request comment reminder for checking the documentation
==============================================================================
Task         : Pull Request Comments
Description  : Add comments to a pull request
Version      : 0.4.0
Author       : Joachim Dalen
Help         : https://docs.devops-extensions.dev/docs/extensions/pull-request-utils/tasks/pull-request-comments
==============================================================================
Finishing: Post a pull request comment reminder for checking the documentation

Hi, as the title implies, in an Azure classic release, when using the Pull Request Status task, trying to choose Update causes the screen to go blank. I've repro'd this across three different browsers on three different machines

.

• Refactor code to use more shared implementation
• Update documentation to use AzExt
• Update changelog
• Refactor webpack setup
• Add new pipelines
• Update README with correct environments

Hi All,

I am using Azure DevOps https://dev.azure.com/ Classic Pipeline. We have created a branch policy which must run a build when a PR is created.

In that Build Definition, I have added below Task (exported YAML below)
steps:

• task: joachimdalen.pull-request-utils.b5a17f8e-3729-4f73-9cae-e8c9ee69137d.PullRequestTags@0
  displayName: 'Pull Request Tags'
  inputs:
  action: check
  tag: deploy
  isOutput: true

Then in the pipeline, in the next Task I try to access variable value in Condition like
and(succeeded(), eq(variables['PullRequest.TagCheckResult'], 'true'))

When I create a PR and add a tag as deploy to that PR, when the pipeline runs, I see value of variables['PullRequest.TagCheckResult'] as Null.

What is it that I am missing here?

The log from the task is:
2022-05-23T08:36:43.0863839Z ##[section]Starting: Pull Request Tags
2022-05-23T08:36:43.0995998Z ==============================================================================
2022-05-23T08:36:43.0996479Z Task : Pull Request Tags
2022-05-23T08:36:43.0997046Z Description : Manage labels for a pull request. Gives the ability to manage pull request tags, or check if a tag is assigned.
2022-05-23T08:36:43.0997478Z Version : 0.4.0
2022-05-23T08:36:43.0997683Z Author : Joachim Dalen
2022-05-23T08:36:43.0998255Z Help : https://docs.devops-extensions.dev/docs/extensions/pull-request-utils/tasks/pull-request-tags
2022-05-23T08:36:43.0998710Z ==============================================================================
2022-05-23T08:36:47.2594109Z ##[section]Finishing: Pull Request Tags

The Condition Log is -
Evaluating: and(succeeded(), eq(variables['PullRequest.TagCheckResult'], 'true'))
Expanded: and(True, eq(Null, 'true'))
Result: False

First of all, let me thank those of you who have used this extension.

As you might notice, it has been a long time since this extension was updated. When this extension was under active development I was using it myself. Over the past year that has changed, and I no longer have the time it requires to properly maintain it. For that reason I will be marking this extension as deprecated and it will no longer be getting any updates. It might change in the future, but right now I can not see any time opening up in the foreseeable future.

It would be really greate if it would be possible to use an something.md file as source for the comment content instead of providing the content inline.

The tests for PullRequestTags seems to be very flaky and keeps failing during test runs, a rerun normally fixes them. Tests should probably be re-written.

hi, i just found out each on every submit new commits on the existing PR its just delete the last appended text, should be the last line of text retain and append the new words instead?

I want to update an PR as part of a build triggered by a Pull request.
The definition for the pipeline is a different repository then the PR which triggered the build.
This throws an error:

Task         : Pull Request Comments
Description  : Add comments to a pull request
Version      : 0.4.1
Author       : Joachim Dalen
Help         : https://devops-extensions.dev/docs/extensions/pull-request-utils/tasks/pull-request-comments
==============================================================================
##[debug]Using node path: /home/vsts/agents/2.217.2/externals/node10/bin/node
##[debug]agent.TempDirectory=/home/vsts/work/_temp
##[debug]loading inputs and endpoints
##[debug]loading INPUT_ACTION
##[debug]loading INPUT_SKIPIFCOMMENTEXISTS
##[debug]loading INPUT_COMMENTID
##[debug]loading INPUT_STATUS
##[debug]loading INPUT_CONTENT
##[debug]loading INPUT_USEDEFINED
##[debug]loading INPUT_PULLREQUESTID
##[debug]loading INPUT_TYPE
##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
##[debug]loaded 12
##[debug]Agent.ProxyUrl=undefined
##[debug]Agent.CAInfo=undefined
##[debug]Agent.ClientCert=undefined
##[debug]Agent.SkipCertValidation=undefined
##[debug]System.AccessToken=***
##[debug]System.TeamFoundationCollectionUri=https://dev.azure.com/xxx/
##[debug]Build.Repository.ID=70d68496-6a91-4137-a7a2-b64d01e5694e
##[debug]useDefined=false
##[debug]System.PullRequest.PullRequestId=362800
##[debug]content=This is a comment posted from pipeline CI_Ansible-lint
##[debug]skipIfCommentExists=true
##[debug]action=createOrUpdate
##[debug]type=Text
##[debug]task result: Failed
##[error]e is not iterable
##[debug]Processed: ##vso[task.issue type=error;]e is not iterable
##[debug]Processed: ##vso[task.complete result=Failed;]e is not iterable
Finishing: Post markdown comment

This is caused by following code line I think:

Either it should be possible to specify a different repo as a parameter, or the extension should use the pull request source repository if the build is triggered by a PR.

We have an update PullRequestStatus task, which sets the integration tests status to the PR. In the pipeline the integration tests run in parallel.
Now we have the problem that the PullRequestStatus of the tests overwrite each other status.
We would now like to have a way to define when the update is effectively applied, in our case only when e.g. the current PullRequestStatus is set to 'pending or succeeded'.

If this is not possible, an alternative would be that the PullRequestStatus task also supports get as an action, so that we can read the status and implement our own decision logic based on it.