[bug] app config issue

[l0lawrence]

#39274 the way the pipeline is set up for app config, analyze runs twice, once for provider and once for app-config, but analyze runs both packages so it duplicates the errors. Could also update its test.yml in addition since that seems excessive imo

[l0lawrence]

/azp run python - appconfiguration - tests-weekly

[azure-pipelines]

Command 'python' is not supported by Azure Pipelines.

Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
• Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull Request Overview

This pull request addresses a bug where duplicate error messages are posted due to the pipeline analyzing both the provider and app-config packages simultaneously. Key changes include:

• Updating the condition to append Pylint errors only if the issue body does not already include a "Pylint Errors:" section.
• Adding an inline comment clarifying the intention behind the conditional block in the issue edit logic.

Comments suppressed due to low confidence (1)

tools/azure-sdk-tools/gh_tools/update_issue.py:72

• Consider verifying that issue.body contains the delimiter 'How to fix:' before taking the second element of the split, to prevent a potential IndexError.

new_body = first_section + template + "\n" + issue.body.split("**How to fix:**")[1]

[mccoyp]

Agreed that App Config might want to simplify their pipeline, but this solves the problem and doesn't hurt