-
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
Pierogii.eateof 6932a 948598d3 7d04 418e bf82 d6b477fc9af5 #113163
Pierogii.eateof 6932a 948598d3 7d04 418e bf82 d6b477fc9af5 #113163
Conversation
/AzurePipelines run |
No commit pushedDate could be found for PR 113163 in repo microsoft/winget-pkgs |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @upintheairsheep, Please verify the manifest file is compliant with the package manager 1.0 manifest specification, 1.1 manifest specification, 1.2 manifest specification, or 1.4 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
|
manifests/p/pierogii/EATEOF/6932a/pierogii.EATEOF.installer.yaml
Outdated
Show resolved
Hide resolved
manifests/p/pierogii/EATEOF/6932a/pierogii.EATEOF.installer.yaml
Outdated
Show resolved
Hide resolved
manifests/p/pierogii/EATEOF/6932a/pierogii.EATEOF.locale.en-US.yaml
Outdated
Show resolved
Hide resolved
Hello @upintheairsheep, The package manager bot determined changes have been requested to your PR. Template: msftbot/changesRequested |
Co-authored-by: Stephen Gillie <[email protected]>
/AzurePipelines run |
No commit pushedDate could be found for PR 113163 in repo microsoft/winget-pkgs |
….yaml Co-authored-by: Kaleb Luedtke <[email protected]>
/AzurePipelines run |
/AzurePipelines run |
No commit pushedDate could be found for PR 113163 in repo microsoft/winget-pkgs |
1 similar comment
No commit pushedDate could be found for PR 113163 in repo microsoft/winget-pkgs |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @upintheairsheep, Please verify the manifest file is compliant with the package manager 1.0 manifest specification, 1.1 manifest specification, 1.2 manifest specification, or 1.4 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @upintheairsheep, Please verify the manifest file is compliant with the package manager 1.0 manifest specification, 1.1 manifest specification, 1.2 manifest specification, or 1.4 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
Hello @upintheairsheep, This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. Template: msftbot/noRecentActivity |
What cause the error? |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @upintheairsheep, Please verify the manifest file is compliant with the package manager 1.0 manifest specification, 1.1 manifest specification, 1.2 manifest specification, or 1.4 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
|
InstallerType: zip | ||
NestedInstallerType: portable | ||
NestedInstallerFiles: | ||
- RelativeFilePath: "Everywhere at the End of Funk Update\Funkin.exe" |
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.
- RelativeFilePath: "Everywhere at the End of Funk Update\Funkin.exe" | |
- RelativeFilePath: "Everywhere at the End of Funk Update\\Funkin.exe" |
Checking to see if double-escaping escapes the escape character.
Hello @upintheairsheep, This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 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: codeflow:open?pullrequest=#113163