-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
New package: Icedrive.Icedrive version 2.29.9 #39191
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @wingetbot! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
The check-in policies require a moderator to approve PRs from the community. Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission. |
Hello @Trenly, |
Hello @Trenly, |
Apologies, I am afraid I am encountering technical difficulties that might have hampered my ability to assist with merging this pull request. I will continue to try to assist if there are further changes to this pull request. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@denelon - I realize it's holidays for you guys, but is there someone available who can merge this? |
Hello @Trenly, 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 |
Apologies, I am afraid I am encountering technical difficulties that might have hampered my ability to assist with merging this pull request. I will continue to try to assist if there are further changes to this pull request. |
1 similar comment
Apologies, I am afraid I am encountering technical difficulties that might have hampered my ability to assist with merging this pull request. I will continue to try to assist if there are further changes to this pull request. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @Trenly, 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 |
@arjun-msft you seem to be alive at this hour, i think we broke stuff 👀 |
I think that the commits merged in, just that the sheer number of issues to be closed caused the bot to not actually close anything. I think all the issues mentioned above can be closed, and then this PR can be marked as closed |
Adding a dummy commit then force-pushing the branch should fix the issue, I guess. |
It shouldnt because it should still recognize that the previous commits were already merged in, and return the same PR validation error. I don’t want to break anything further, so I’ll let MSFT fix it first |
Ran into the same issue; looks like @msftbot merges in the commit instead of merging the PR for trying to close 10+ issues/PRs. So I'm just going to delete everything from my PR message.
Since the commit was merged the PR will get |
@OfficialEsco did this make it in? I see it closed but I don't think it got merged but I see it in the repo. Let me know if something needs to be done! |
winget validate --manifest <path>
?winget install --manifest <path>
?Closing these issues in favor of #39190
Microsoft Reviewers: Open in CodeFlow