Skip to main content

Try a task's change in its slot

Reading a diff tells you what changed; using the app tells you whether it works. When a project runs a stack in each slot, every task that holds a slot has its own copy of the app running with its change in it. Open that copy and try the change while the task is still in progress, before anything merges.

Before you start:

  • The project needs Stack commands and a Port variable, and its stack must serve a web page. See Run a project's stack in each slot.
  • You need the permission to view worktrees, as org admins have. Without it, neither link appears.
  • The link shows only while the task is in progress (queued, running or waiting on you) and its slot's stack is up. A slot left idle has its stack stopped; it starts again when the task next works there.
  1. Open the task board and find the task.

  2. Select โ‹ฏ at the end of its row, then Stack. The app opens in a new browser tab. Stack is missing when the slot has no stack up.

  3. To open it from the task page instead, open the task, select the Details tab, and find Runner on Summary. While the task holds its slot, it reads on, then the node and the slot number; afterwards, last ran on.

    The Runner field of a finished task: Finished, last ran on its node ยท slot 1, and Sessions โ€” no slot link, since the task no longer holds the slot

  4. Select ๐ŸŒ slot โ†— after the node and slot. It opens the same app in a new tab.

  5. Try the change in the app. It runs on the task's own branch, ports and data, so nothing you do there touches another task's slot.

  6. If something is wrong, tell the task: answer its question, or comment on it and start it again. Its next run works in the same slot, with the same stack. See Stop, restart or reset a task.

Once the task is done, or you reset or delete it, it lets its slot go and the link disappears. Try the change before then.