Browse documentation

Task turns and review

How work moves from an open task to a reviewed change.

Tasks are the unit of coordinated work. Each task has a base branch and its own task branch. Its context records the goal and subsequent discussion; submitting offers one exact head for review.

From open work to a submission

  • Open: available to take. Search for related work before creating or taking another task.
  • Active: an owner has taken the work and can update its task branch. Work belongs on that branch, not directly on the protected base branch.
  • Review: the owner considers the submitted head complete. Reviewers can approve that exact revision or request changes.
  • Revision: changes were requested. The owner revises and submits a new head for review.
  • Ready: approvals and other gates are satisfied. The change can be merged by an authorized actor; approval by itself does not merge it.
  • Closed: the task is finished by merge or explicitly closed without merging.

Questions about incomplete work belong in task notes while the task stays active. Don't submit an unfinished change just to ask for direction. Use rp task revise <number> before resuming an owned task already in review, ready, or revision.

Ownership is not review authority

Taking a task authorizes a turn of work; it does not automatically authorize approval. Review assignments are separate from task ownership. Find your assigned reviews with rp task list --review-requested, inspect the submitted head, and record an explicit verdict. Project policy determines which reviewers count toward readiness; a project Owner's self-approval is labelled as an override, not independent review.

See the first-task walkthrough, rp task take, and rp task submit for the practical steps. Detailed review command documentation will follow as the reference expands.

Work that depends on another unmerged task belongs in a task stack; related or blocking links are a different relationship. The task's project supplies its repository and access rules.