Repository navigation
FAQ: How do I run several tasks at once, and where does each task's branch live? #2873
|
This is a maintainer-written FAQ, seeded from the questions people ask most. The answer below is marked as the accepted answer. If your case is different, reply here or open a new Q&A. Can codeaf work on several things at the same time? If it does, where does each task's work actually happen, which branch is it on, and how does it get back into my checkout? |
Replies: 1 comment
|
Several at once Say them in one message the way you would to a colleague. Name three things and each can become its own task, in its own copy of the repository, on its own branch. The conversation stays yours while they run, and the rail beside it shows every task and its subtasks. There is no limit on how many run at once by default. Where each task lives
(A quick task is the exception: it works directly in your own folder, with no checkout and no branch.) How the work comes home Work that passes its check lands on your branch by itself, never on If your checkout is on a protected branch ( Or check out a feature branch before starting tasks, and finished work comes home by itself. Work nothing could check waits under Sources: the README (Talk, and it becomes tasks) and the manual pages |
Several at once
Say them in one message the way you would to a colleague. Name three things and each can become its own task, in its own copy of the repository, on its own branch. The conversation stays yours while they run, and the rail beside it shows every task and its subtasks.
/task <brief>starts one explicitly.There is no limit on how many run at once by default.
task.parallel(in/settings) is blank, which means no cap; if you set one, it is a queue, never a refusal. What actually holds new starts is the machine:task.max_load(default 1.5 per core) andtask.min_free_mb(default 1536 MiB). Held work readswaiting · machine busyand starts when there is room.Where each task lives