Repository navigation
Add Installation Instructions for Windows Users #910
Description
Activity
/kind documentation
/this-is-fineDetails
In response to this:
/kind documentation
/this-is-fineInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
- addedkind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.
on Jul 31, 2019 I'm fine with adding a paragraph or two to Installation and Troubleshooting. If it will be longer we can have a separate doc and link to it
Issues go stale after 90d of inactivity.
Mark the issue as fresh with/remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale- addedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
on Oct 30, 2019 /lifecycle frozen
/assign
Will tie this to #266- addedlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.and removedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
on Oct 30, 2019

This issue originally appeared in #676. We provided a utility script for Windows developers to work around the symbolic link in #766. However, the script is not documented anywhere and we just got a new question on #857. I think we should add information to Readme for potential Windows developers.
We'll have to tell Windows developers about the symbolic links and our workaround - and that they'll face difficulty when trying to commit changes (should remove the copied folders, clone the base repo only if they want to change the code in the base repo, etc).
I have two ideas to document this: