Merge branch 'microsoft:master' into master

.github/ISSUE_TEMPLATE/package_request.yml

@@ -43,4 +43,4 @@ body:
         Package Name:
         Description:
         Package Version:
-        Installer URL:
+        Installer Url:

.github/actions/spelling/allow.txt

@@ -1,4 +1,5 @@
 appinstaller
+admins
 appname
 apps
 appsandfeaturesentries
@@ -14,6 +15,7 @@ distro
 ESRP
 Estmob
 EULA
+ftp
 github
 https
 Inno
@@ -41,11 +43,14 @@ screenshots
 Smartscreen
 ssh
 standalone
+subkey
 submitters
 tada
 Testplan
 toolset
+unassign
 ubuntu
+uninstall
 uninstaller
 uninstalls
 upvote
@@ -54,4 +59,5 @@ website
 winget
 wingetbot
 wingetcreate
+workflows
 yml

.github/actions/spelling/expect.txt

@@ -1,30 +1,8 @@
-admins
 automerge
-craigloewen
 cspell
-Daa
 denelon
-Esco
-fabricbot
-Filezilla
 Icm
-jedieaston
-Joakim
-Kad
-Karan
-Levvie
 LOCALAPPDATA
-mdanish
-Megamix
 misclicks
-msft
-quhxl
-redistribution
 Repology
-russellbanks
 stephengillie
-Tbot
-timezone
-Trenly
-Unassign
-workflows

.github/policies/labelAdded.manifestSingletonDeprecated.yml

@@ -0,0 +1,40 @@
+id: labelAdded.manifestSingletonDeprecated
+name: GitOps.PullRequestIssueManagement
+description: Handlers when "Manifest-Singleton-Deprecated" label is added
+owner:
+resource: repository
+disabled: false
+where:
+configuration:
+  resourceManagementConfiguration:
+    eventResponderTasks:
+      - description: >-
+          When the label "Manifest-Singleton-Deprecated" is added to a pull request
+          * Add the PR specific reply notifying the issue author
+          * Assign to the Author
+          * Label with Needs-Author-Feedback
+          * Remove the Needs-Attention Label
+        if:
+          - payloadType: Pull_Request
+          - labelAdded:
+              label: Manifest-Singleton-Deprecated
+        then:
+          - addReply:
+              reply: >-
+                Hello @${issueAuthor},
+
+
+                The package manager bot determined that your submission uses a `Singleton` Manifest, which been deprecated in this repository. Please update your submission to use the newer multi-manifest format. If you built your manifest by hand, a tool like [WingetCreate](https://github.com/microsoft/winget-create) or [YamlCreate](https://github.com/microsoft/winget-pkgs/blob/master/doc/tools/YamlCreate.md) can help you build the multi-manifest.
+
+
+                Template: msftbot/validationError/manifest/singleton/deprecated
+          - assignTo:
+              author: True
+          - addLabel:
+              label: Needs-Author-Feedback
+          - removeLabel:
+              label: Needs-Attention
+        # The policy service should trigger even when the label was added by the policy service
+        triggerOnOwnActions: true
+onFailure:
+onSuccess:

.github/policies/labelAdded.manifestVersionDeprecated.yml

@@ -9,7 +9,7 @@ configuration:
   resourceManagementConfiguration:
     eventResponderTasks:
       - description: >-
-          When the label "Manifest-Version-Error" is added to a pull request
+          When the label "Manifest-Version-Deprecated" is added to a pull request
           * Add the PR specific reply notifying the issue author
           * Assign to the Author
           * Label with Needs-Author-Feedback

.github/policies/labelManagement.issueOpened.yml

@@ -8,6 +8,31 @@ where:
 configuration:
   resourceManagementConfiguration:
     eventResponderTasks:
+      - description: >-
+          When a PR is opened/updated, if no files are modified
+          * Close the issue
+          * Add a comment
+        if:
+          - payloadType: Pull_Request
+          - isOpen
+          - or:
+              - isAction:
+                  action: Opened
+              - isAction:
+                  action: Synchronize
+          - filesMatchPattern:
+                pattern: ^$
+        then:
+          - addReply:
+              reply: >-
+                Hello @${issueAuthor},
+
+
+                This pull request does not update any files. Please review your commit history and resubmit.
+
+
+                Template: msftbot/validationError/pullRequest/noContent
+          - closePullRequest
       - description: Add CodeFlow link to new PRs
         if:
           - payloadType: Pull_Request
@@ -39,6 +64,9 @@ configuration:
           - payloadType: Pull_Request
           - filesMatchPattern:
               pattern: DevOpsPipelineDefinitions/*
+          - not:
+              filesMatchPattern:
+                pattern: ^$
           - or:
               - activitySenderHasPermission:
                   permission: Read
@@ -66,6 +94,9 @@ configuration:
           * Add the "Manifest-Path-Error" label
         if:
           - payloadType: Pull_Request
+          - not:
+              filesMatchPattern:
+                pattern: ^$
           - not:
               filesMatchPattern:
                 pattern: ^manifests/*
@@ -136,6 +167,9 @@ configuration:
         if:
           - payloadType: Pull_Request
           - isOpen
+          - not:
+              filesMatchPattern:
+                pattern: ^$
           - or:
             - filesMatchPattern:
                 pattern: ^.github\\.*
@@ -161,6 +195,9 @@ configuration:
         if:
           - payloadType: Pull_Request
           - isOpen
+          - not:
+              filesMatchPattern:
+                pattern: ^$
           - filesMatchPattern:
                 pattern: ^.*\.validation
           - not:

.github/policies/scheduledSearch.cleanupInPRLabels.yml

@@ -0,0 +1,42 @@
+# Due to limitations in the policy service, it isn't possible to check on the state of the linked PRs because of this
+# the assumption is made that if a linked PR is merged, the issue will be closed automatically. If the issue doesn't
+# close, then the PR must not have been merged and is either stale or was closed. Since there is no way to check for
+# that state specifically, the policy checks to see if there has been any activity on the issue. Any comments, labels
+# or other actions on the issue will reset the 15 day period.
+
+id: scheduledSearch.cleanupInPRLabels
+name: GitOps.PullRequestIssueManagement
+description: Remove the In-PR label from issues where the PR has become stale
+owner:
+resource: repository
+disabled: false
+where:
+configuration:
+  resourceManagementConfiguration:
+    scheduledSearches:
+      - description: >-
+          Search for issues where -
+          * Issue is Open
+          * Issue has the label In-PR
+          * Has not had activity in the last 15 days
+
+          Then -
+          * Remove In-PR label
+          * Add Help-Wanted label
+        frequencies:
+          - hourly:
+              hour: 12
+        filters:
+          - isIssue
+          - isOpen
+          - hasLabel:
+              label: In-PR
+          - noActivitySince:
+              days: 15
+        actions:
+          - removeLabel:
+              label: In-PR
+          - addLabel:
+              label: Help-Wanted
+onFailure:
+onSuccess:

.github/policies/wingetbotTriggers.yml

@@ -28,6 +28,9 @@ configuration:
               issueAuthor: False
           - filesMatchPattern:
               pattern: DevOpsPipelineDefinitions/*
+          - not: # This checks to ensure the PR is not empty. If it is empty, it would be treated as a match for the above condition
+              filesMatchPattern:
+                pattern: ^$
           - isOpen
         then:
           - approvePullRequest:

README.md

@@ -1,8 +1,8 @@
 # Windows Package Manager Community Repository
 
 [![Gitter](https://img.shields.io/gitter/room/Microsoft/winget-pkgs)](https://gitter.im/Microsoft/winget-pkgs)
-[![Validation Pipeline Badge](https://img.shields.io/endpoint?url=https://winget-pme.azurefd.net/api/GetServiceComponentStatusBadge?component=ValidationPipeline 'Validation Pipeline Badge')](https://dev.azure.com/ms/winget-pkgs/_build?definitionId=337)
-[![Publish Pipeline Badge](https://img.shields.io/endpoint?url=https://winget-pme.azurefd.net/api/GetServiceComponentStatusBadge?component=PublishPipeline 'Publish Pipeline Badge')](https://dev.azure.com/ms/winget-pkgs/_build?definitionId=338)
+[![Validation Pipeline Badge](https://img.shields.io/endpoint?url=https://winget-pme.azurefd.net/api/GetServiceComponentStatusBadge?component=ValidationPipeline 'Validation Pipeline Badge')](https://dev.azure.com/shine-oss/winget-pkgs/_build?definitionId=14)
+[![Publish Pipeline Badge](https://img.shields.io/endpoint?url=https://winget-pme.azurefd.net/api/GetServiceComponentStatusBadge?component=PublishPipeline 'Publish Pipeline Badge')](https://dev.azure.com/shine-oss/winget-pkgs/_build?definitionId=12)
 [![GitHub Status](https://img.shields.io/endpoint?url=https://api.bittu.eu.org/github-status-badge-endpoint)](https://www.githubstatus.com)
 
 This repository contains the manifest files for the **Windows Package Manager** default source. You are highly encouraged to submit manifests for your favorite application.
@@ -21,11 +21,6 @@ Please check the [overview](doc/README.md) for detailed topics. Common topics fo
 * [Requesting a new package](doc/Issues.md#Request-a-New-Package)
 * [Requesting a new package version](doc/Issues.md#Request-a-New-Package-Version)
 
-## Repology
-[Repology](https://repology.org/), the packaging hub monitors package repositories comparing package versions and other information.
-
-[![Repository status](https://repology.org/badge/repository-big/winget.svg)](https://repology.org/repository/winget)
-
 # Contributing
 
 This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.