Skip to content

Fix ManualValidation@1 approvers field documentation to clarify multiLine format #21196

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

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Copilot
Copy link

@Copilot Copilot AI commented Aug 6, 2025

The approvers field in ManualValidation@1 task had misleading documentation that caused only the first user in a list to be able to approve manual validations.

Problem

The approvers field was defined as type multiLine but the help text said "separated by commas", creating confusion about the expected format. Users following the documentation would write YAML like:

- task: ManualValidation@1
  inputs:
    approvers: |
      [email protected],
      [email protected],
      [email protected]

This mixed multiline YAML syntax with comma separation, causing the Azure DevOps service to only recognize the first email address. Other users would see only a loading screen instead of approval options, even when they had proper permissions.

Solution

Updated the help text to clarify that each user/group should be on a separate line without commas, consistent with other multiLine field patterns in Azure Pipelines tasks.

Before:

"Specify users/groups/project teams separated by commas to act on a manual validation..."

After:

"Specify users/groups/project teams who can act on a manual validation. Enter each user/group on a separate line..."

Correct Usage

- task: ManualValidation@1
  inputs:
    approvers: |
      [email protected]
      [email protected]
      [email protected]

This change ensures all specified approvers can act on manual validations as intended, resolving the issue where only the first user could approve.

Fixes #21179.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 03nvsblobprodwcus014.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 055vsblobprodwcus02.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 1g1vsblobprodwcus01.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 3eavsblobprodwcus03.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 3zgvsblobprodwcus024.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 40qvsblobprodwcus022.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
  • 4fdvsblobprodwcus012.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
  • 5tbvsblobprodwcus06.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 61cvsblobprodwcus010.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 73dvsblobprodwcus07.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 8usvsblobprodwcus011.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • 9owvsblobprodwcus020.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • arpvsblobprodwcus017.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • crcvsblobprodwcus021.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
  • fslvsblobprodwcus015.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • grnvsblobprodwcus04.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • k92vsblobprodwcus08.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • mnzvsblobprodwcus05.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • pl8vsblobprodwcus09.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • uubvsblobprodwcus018.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • vwmvsblobprodwcus016.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • x4wvsblobprodwcus013.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • xg1vsblobprodwcus019.vsblob.vsassets.io
    • Triggering command: npm install (dns block)
  • xlkvsblobprodwcus023.vsblob.vsassets.io
    • Triggering command: npm install (dns block)

If you need me to access, download, or install something from one of these locations, you can either:


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@Copilot Copilot AI changed the title [WIP] [BUG]: ManualValidation@1 approvers attribute does not behave as documented Fix ManualValidation@1 approvers field documentation to clarify multiLine format Aug 6, 2025
@Copilot Copilot AI requested a review from v-schhabra August 6, 2025 11:25
Copilot finished work on behalf of v-schhabra August 6, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG]: ManualValidation@1 approvers attribute does not behave as documented
2 participants