microsoft / microsoft/winget-pkgs

[New Feature]: Validate against similar top-level and overall identifiers

Open
#271,007 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Validation-Pipeline Issue-Feature
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Description of the new feature/enhancement

When the pipelines run Manifest Validation, they should provide a recommendation if there is another package identifier which is similar but not the same for the first part of the package identifier and the overall package identifier

Proposed technical implementation details (optional)
  • PR for TestPublisherInc.ExamplePackageA

Your manifest appears to be under TestPublisherInc. There are similar folders which already exist. Please check if any of these may be duplicate top-level identifiers and update your PR accordingly.

  • TestPublisher
  • PR for TestPublisherInc.ExamplePackageA
  • Your submission appears to be for TestPublisherInc.ExamplePackageA. There are similar packages which already exist. Please check if any of these may be duplicates and update your PR accordingly.

  • TestPublisher.ExamplePackage
  • TestPublisher.Example.PackageA
  • TestPublisher.ExampleOtherPackage

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the Manifest Validation pipeline and its existing identifier checks, then compare the proposed top-level and overall identifier examples with current recommendations. Done means validation recommends similar existing identifiers at both levels with the expected package examples.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.