Repository navigation
Runway 0.1.6
·
20 commits
to main
since this release
- A repo no longer needs a runway.json before Runway's sessions can run its tests. When you add a repo, Runway finds the check command and the build and run commands (a Swift package in a subfolder too) and keeps them in Runway, so nothing has to be committed first. A runway.json on the base branch, when it has them, still wins.
- A repo with no check command says so on the board, with "Set check command…". Right-click a repo to change its commands any time.
- "Add a repo…" in the sidebar now opens the folder picker and shows what Runway found.
- In Terminal:
runway repo check <repo>shows, sets (--check,--allow) or suggests (--suggest) them.