Contributions are welcome. See the guidelines below before submitting a PR.
- Keep changes deterministic and script-first.
- Prefer additive improvements over broad rewrites.
- Preserve CLI stability of
scripts/wan2gp_operator.py.
-
Clone the repository:
git clone https://github.com/avalonreset/wan2gp-operator.git cd wan2gp-operator -
Create a virtual environment:
python -m venv .venv source .venv/bin/activate # Linux/macOS .venv\Scripts\activate # Windows
-
Verify scripts compile:
python -m py_compile scripts/*.py
- Follow PEP 8 conventions
- Use Ruff for linting:
ruff check . - Keep functions focused and small
- Add docstrings to new modules and public functions
Use the Wan2GP venv when available:
python -m py_compile scripts/*.py
python scripts/wan2gp_operator.py compose --prompt "smoke test" --quality balanced --duration-seconds 2For run-path updates, always validate:
- Dry-run path
- Full run path
- Failure diagnosis path
- Evolve path
- Create a feature branch from
main - Make your changes with clear, focused commits
- Run
python -m py_compile scripts/*.pybefore pushing - Open a PR using the PR template
- Follow the Code of Conduct
- Bug + risk first
- Repro command
- Before/after behavior
- Any new defaults and tradeoffs