syntaqxThe runner guides cover g1t-runner 0.3.5's needs and the desktop app's Set up in full (#52). Self-hosted runners gets "What the sandbox needs": run `g1t-runner sandbox status` first, since it downloads nothing; a sample of what it prints; a row for each need it names (windows_update, virtualization, nested_virtualization, vm_platform, wsl, wsl_update, windows_edition, windows_sandbox, restart, kvm_module, kvm_group, qemu, macos_update, homebrew, vfkit) with its kind of job and the fix; that each is named only when the computer says it for certain, and Windows' facts are kept per boot; and that `sandbox up` stops before downloading the image when Linux jobs lack something, leaving out Windows jobs unless named with --only. Its JSON sample and field table gain `needs`, with the current cause and fix wording, and the troubleshooting rows and the desktop app section point at the new section.fcc5171History
- ..
- advisories.rs
- code_scanning.rs
- config.rs
- deps.rs
- history.rs
- lib.rs
- manifests.rs
- overview.rs
- patterns.rs
- planning.rs
- pull_text.rs
- ranges.rs
- registries.rs
- resolved.rs
- schedule.rs
- secret_alerts.rs
- security_updates.rs
- store.rs
- suite.rs
- suite_store.rs
- summaries.rs
- supply_chain.rs
- timezones.rs
- update_store.rs
- updates.rs
- version_updates.rs
- yaml.rs