-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting Browser Tamer from winget #115266
Conversation
@wingetbot run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Each manifest will need to be removed as a separate PR |
Haha |
Hello @aloneguid, The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case. Example: For details on the error, see the details link below in the build pipeline. You may also try the Windows Package Manager Manifest Creator Template: msftbot/validationError/pullRequest |
I hope you understand that raising tens of PRs is ridiculous and I'm not going to do that. |
Unfortunately, the pipelines can only process changes to individual manifests at a time. I'll see what I can do to raise those PR's |
Individual PRs have been opened; |
Curious though... why? edit: nvm aloneguid/bt@4fc78e7 |
yes, spot on, nothign against WinGet, I personally use it every day :) |
I'm an author of "Browser Tamer" utility and I would like it to be permanently removed from the winget package manager please.
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: codeflow:open?pullrequest=#115266