Support no-op for PR pipeline

[raych1]

Mirrors Azure/azure-sdk-for-java#49558 for the .NET PR pipeline.

• Adds a SkipPrValidation parameter to eng/pipelines/pullrequest.yml.
• Passes it through to archetype-sdk-client.yml.
• Adds a manual-run no-op stage and skips build/release validation when the flag is enabled.
• Excludes .github/skills/azsdk-common-*/** from the PR validation trigger so changes limited to common Azure SDK skill folders do not run this pipeline.

Validation:

• git diff --check
• Parsed changed YAML files with PyYAML

[Copilot]

Pull request overview

This PR adds an opt-in SkipPrValidation boolean parameter to the PR pipeline so that manual runs can complete as a no-op, mirroring the behavior introduced in the Java repo. The flag is threaded from eng/pipelines/pullrequest.yml into the shared stage template, where it conditionally injects a simple “No-op” stage and suppresses build/release validation for manual executions.

Changes:

• Added SkipPrValidation parameter to the PR pipeline entrypoint (eng/pipelines/pullrequest.yml) and passed it into the archetype stage template.
• Updated archetype-sdk-client.yml to add a manual-run “NoOp” stage when SkipPrValidation=true, and to skip Build plus prerelease/release stages in that mode.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
eng/pipelines/templates/stages/archetype-sdk-client.yml	Adds SkipPrValidation parameter, introduces a manual “No-op” stage, and conditions Build/release stages to be skipped when enabled.
eng/pipelines/pullrequest.yml	Adds SkipPrValidation pipeline parameter and forwards it to the archetype stage template.

[jsquire]

@raych1 : Can you please explain the purpose of this feature? I get that this version brings parity with Java, but I'd like to understand the end-to-end scenario and motivation.

[raych1]

@raych1 : Can you please explain the purpose of this feature? I get that this version brings parity with Java, but I'd like to understand the end-to-end scenario and motivation.

@jsquire : The main motivation is to reduce CI friction for non-SDK changes, especially the common process of syncing skills under the .github\skills\ folder. In language repos, the PR validation pipeline is currently the only required CI check for pull requests since check enforcer was removed. So, every PR will need to pass the PR pipeline before it can be merged.

That works well for SDK code changes. However, there are some cases for PRs which might only touch repo automation or other non-SDK related changes - for example, updates under \.github\ folder. In those cases, running the full PR validation pipeline doesn't add value but increasing additional efforts to pass all jobs.

This new feature allows us to trigger the PR validation pipeline with no-op mode in automations-driven scenarios, so those PRs can satisfy the required check without consuming the full validation workflow.