Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Deleting Browser Tamer from winget #115266

wants to merge 1 commit into from

Conversation

aloneguid
Copy link

@aloneguid aloneguid commented Aug 4, 2023

I'm an author of "Browser Tamer" utility and I would like it to be permanently removed from the winget package manager please.

  • Have you signed the Contributor License Agreement?
  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • This PR only modifies one (1) manifest
  • Have you validated your manifest locally with winget validate --manifest <path>?
  • Have you tested your manifest locally with winget install --manifest <path>?
  • Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.


Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115266&drop=dogfoodAlpha

@Trenly
Copy link
Contributor

Trenly commented Aug 4, 2023

@wingetbot run

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Trenly
Copy link
Contributor

Trenly commented Aug 4, 2023

Each manifest will need to be removed as a separate PR

@aloneguid
Copy link
Author

Haha

@microsoft-github-policy-service
Copy link
Contributor

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:
Path: manifests / m / Microsoft / WindowsTerminal / 1.6.10571.0 / WindowsTerminal.yaml

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

@aloneguid
Copy link
Author

I hope you understand that raising tens of PRs is ridiculous and I'm not going to do that.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels Aug 4, 2023
Trenly added a commit to Trenly/winget-pkgs that referenced this pull request Aug 4, 2023
@Trenly
Copy link
Contributor

Trenly commented Aug 4, 2023

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

@Trenly
Copy link
Contributor

Trenly commented Aug 4, 2023

Individual PRs have been opened;

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Attention This work item needs to be reviewed by a member of the core team. label Aug 4, 2023
@sharunkumar
Copy link
Contributor

sharunkumar commented Aug 4, 2023

Curious though... why?

edit: nvm aloneguid/bt@4fc78e7

@aloneguid
Copy link
Author

yes, spot on, nothign against WinGet, I personally use it every day :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PullRequest-Error PR is Invalid
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants