Outside of the VMR, testing Arcade changes in a repo that builds with Arcade requires manually bootstrapping a consuming repo, either locally or via CI.
This usually means building Arcade (or using an official CI build), wiring it into the consuming repo, and updating feeds and dependencies (for example, via local feeds or the general testing feed). The workflow is repetitive, error‑prone, and slows iteration.
A reusable skill that handles Arcade bootstrapping end‑to‑end across both local and CI workflows would reduce toil and make validating Arcade changes much easier.
Outside of the VMR, testing Arcade changes in a repo that builds with Arcade requires manually bootstrapping a consuming repo, either locally or via CI.
This usually means building Arcade (or using an official CI build), wiring it into the consuming repo, and updating feeds and dependencies (for example, via local feeds or the general testing feed). The workflow is repetitive, error‑prone, and slows iteration.
A reusable skill that handles Arcade bootstrapping end‑to‑end across both local and CI workflows would reduce toil and make validating Arcade changes much easier.