microsoft / microsoft/winget-pkgs
[Package Issue]: Git.Git
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Please confirm these before moving forward
- I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Installation issue.
Brief description of your issue
The Git for Windows package doesn't create the paths to easily work with Git.
Steps to reproduce
Winget install Git.Git
And then from the command line git clone url should be possible which is not
Actual behavior
Missing environmental paths
Expected behavior
Environmental paths created. Wen you download the installer from the git for windows website this path is created:
(Get-ChildItem Env:\Path).Value
C:\Program Files\PowerShell\7;C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\PowerShell\7\;**C:\Program Files\Git\cmd**;C:\Users\Guido\AppData\Local\Microsoft\WindowsApps;C:\Users\Guido\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Guido\AppData\Local\Programs\Bicep CLI Which is not when you install it using winget
Environment
winget --info
Windows Package Manager v1.2.10691
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22621.2283
Package: Microsoft.DesktopAppInstaller v1.17.10691.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Screenshots and Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Git.Git package entry in the winget-pkgs repository and reproduce the installation with winget install Git.Git. Check whether the resulting environment includes C:\Program Files\Git\cmd; done means git clone url works from a command-line session after installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100