Pull requests across repositories, tested together
about 2 months ago
Related pull requests in several repositories now run as one test, chat got faster, and multi-repository environments come to the Pro plan.
A feature often spans repositories: the frontend in one pull request, the API in another. When pull requests in different repositories share a branch, qlane now tests them together in one sandbox and reports the result on each of them.
Chat got faster too. In our measurements replies arrive about 40% sooner (a median of 3.1 seconds, down from 5.3), and when you ask the agent to check something it starts a test right away instead of asking for a URL: 14 times out of 14, up from 8.
acme/web#214
feat/saved-cards
acme/api#88
feat/saved-cards
One run
Both branches, one sandbox
Results posted to 2 pull requests
- Pull requests that share a branch across repositories are tested in one run and reported on each.
- Chat replies about 40% faster and starts a test when you ask for one.
- Multi-repository environments are now part of the Pro plan.
- A redesigned report on GitHub for every run.
- The agent checks its results against what the pull request says it does.
- Seven project settings that had no UI are now on a redesigned settings page, each with a help tip.
- A per-project switch for qlane's status block in pull-request descriptions.
- Compose environments can expose more than one public service.
- qlane.ai explains the product in three pillars.