-
Notifications
You must be signed in to change notification settings - Fork 258
[fix] Windows junction handling #557
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
[fix] Windows junction handling #557
Conversation
|
|
||
| # Project-specific binaries | ||
| cmd/go-getter/go-getter | ||
| go-getter |
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.
just want to confirm if we're ignoring go-getter binary or a directory named go-getter over here?
any specific reason why we're ignoring this>?
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.
there to keep the compiled go-getter binary out of version control
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.
Fix Windows Test Coverage and Implement Cross-Platform Symlink Resolution
This PR addresses two key areas to improve the robustness and test coverage of go-getter on Windows:
Previously, several important tests were being skipped on Windows, reducing test coverage and potentially hiding Windows-specific issues.
Cross-Platform Symlink Resolution
Implemented new symlink resolution infrastructure to handle the complexities of Windows filesystem links:
All previously skipped Windows tests now pass