Currently, development is started via ./run_dev.sh which only works on Unix-like systems. Windows developers need an equivalent.
Approach:
Create run_dev.bat or run_dev.ps1 as a Windows equivalent of run_dev.sh
Ensure all development dependencies and steps work on Windows
Alternatively, consider using cross-platform tooling (e.g., npm scripts, cross-env) to make a single entry point work on all platforms
Document Windows setup steps in README
Test the complete development workflow on Windows
## Feature: Windows Development Scripts
**Source:** TODO.md line 34
### Implementation Notes
Currently, development is started via `./run_dev.sh` which only works on Unix-like systems. Windows developers need an equivalent.
**Approach:**
1. Create `run_dev.bat` or `run_dev.ps1` as a Windows equivalent of `run_dev.sh`
2. Ensure all development dependencies and steps work on Windows
3. Alternatively, consider using cross-platform tooling (e.g., npm scripts, `cross-env`) to make a single entry point work on all platforms
4. Document Windows setup steps in README
5. Test the complete development workflow on Windows
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Feature: Windows Development Scripts
Source: TODO.md line 34
Implementation Notes
Currently, development is started via
./run_dev.shwhich only works on Unix-like systems. Windows developers need an equivalent.Approach:
run_dev.batorrun_dev.ps1as a Windows equivalent ofrun_dev.shcross-env) to make a single entry point work on all platforms