Repository navigation
Docs: add Windows troubleshooting section to README - #154
Merged
Merged
Conversation
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
jay23606
marked this pull request as ready for review
November 19, 2026 06:43
codepiyusss
approved these changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #33
Adds a "Windows troubleshooting" section to README.md, placed before the License section. It covers:
venv\Scripts\Activate.ps1) and cmd (venv\Scripts\activate.bat), including the one-timeSet-ExecutionPolicy -Scope CurrentUser RemoteSignedstep for PowerShell's script block.fixitnot being recognized: activate the venv, re-run the editable install, check withwhere fixit/Get-Command fixit, or fall back topython -m fixit.Docs only. No code or test changes, and no xfail markers exist for this issue. Verified
git diff --checkpasses (no whitespace errors). pytest was not run: the change touches no Python code, and installing dependencies was out of scope for this environment. CI runs the test suite.🤖 Generated with Claude Code
Tests not run here: pytest (no code changed; dependencies not installed in this environment per task rules, CI runs the suite)
Fixes #33
🤖 Generated with Claude Code