-
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
Update manifest: Git.Git version 2.46.0 #173749
Update manifest: Git.Git version 2.46.0 #173749
Conversation
- Fix incorrect installer switches Signed-off-by: Dragon1573 <[email protected]>
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wingetbot run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wingetbot run |
/AzurePipelines run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
This error seems to be occurring frequently in recent days. I'm not entirely sure, but I believe it might be related to the recent pipeline work. |
This package installs and launches normally in a Windows 10 VM. |
8db1ace
into
microsoft:master
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Details
Checklist for Pull Requests
Manifests
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the directory's name containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow