microsoft / microsoft/winget-pkgs

[New Feature]: Manifest Validation Responses

Open
#328,386 0 comments 7 reactions 0 assignees View on GitHub
Area-Validation-Pipeline Issue-Feature
Dominant language
No language data
Stars
11.1k
Forks
9.7k
PR merge metrics
PR metrics pending

Description

### Description of the new feature/enhancement

When a manifest is invalid (YAML syntax, WinGet Manifest Syntax, etc.) a comment on the PR should provide a more helpful message so the author can easily fix it.

We should consider printing the specific error we see during manifest validation when there is a failure, rather than just saying "Invalid manifest." This will make it easier to identify and resolve it quickly.

### Proposed technical implementation details (optional)

_No response_

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the pull-request manifest validation logic that emits "Invalid manifest" and inspect how YAML and WinGet manifest errors are currently handled. Done means validation comments expose the specific failure details needed to correct an invalid manifest.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.