-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
ViGEm.BthPS3 version 2.1.153.0 #65544
ViGEm.BthPS3 version 2.1.153.0 #65544
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @sitiom, |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @sitiom, Please verify the manifest file is compliant with the package manager 1.0 manifest specification. You could also try our Windows Package Manager Manifest Creator Preview. For details on the specific error, see the details link below in the build pipeline. |
6301394
to
52c6ba6
Compare
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @sitiom, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can set this PR to DRAFT until Bluetooth stack is available in validation pipelines (probably requires custom hardware)
Hello @sitiom, Template: msftbot/changesRequested |
@msftbot Blocking-Issue |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @sitiom, This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any recent activity. It will be closed if no further activity occurs within 3 days of this comment. Template: msftbot/noRecentActivity |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow