[Enhancement] (Prompt to) enable Win32 Long Paths if action fails due to path length.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
On Windows, if the paths in the repository are too long for Gittyup to clone, instead of just "failing", it should prompt the user to enable Win32 Long Path support (with a dialog) and perform https://bigfont.ca/enable-long-paths-in-windows-with-powershell/
New-ItemProperty ` -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" ` -Name "LongPathsEnabled" ` -Value 1 ` -PropertyType DWORD ` -Force
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem] "LongPathsEnabled"=dword:00000001
if necessary.
However, this won't be of much use until https://github.com/Murmele/Gittyup/issues/597#issue-1803281272 is implemented.
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the Windows clone failure caused by long repository paths and read issue #597, which this work depends on. Identify where Gittyup handles that failure and determine how the prompt should offer enabling Win32 Long Paths. Done means the relevant failure produces a dialog and performs the requested Windows setting change when necessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100