Pull-request follow-ups
Use GitHub reviews and the authenticated Labor0 task together to continue work on an agent-created pull request and decide when it is ready to merge.
Check the result
- Open the pull request linked from the Labor0 task.
- Compare the changed files and summary with the original request.
- Submit actionable feedback from Files changed when the result needs another update.
- Resolve review feedback and wait for updated required checks.
A change is merge-ready only when it matches the request, changes the intended files, passes required checks, has no unresolved feedback, and has no merge conflict. A Completed Labor0 task does not override a failing GitHub check.
Review an agent-created pull request
Labor0 adds a Continue working with Labor0 guidance comment to an agent-created pull request. Give actionable feedback from Files changed:
- Select Review changes and submit a non-empty Comment, Approve, or Request changes review.
- For one line or block, submit an inline review comment beside the diff.
- In Conversation, mention the displayed
@labor0-botaccount and include a meaningful instruction in the same comment.
Formal reviews and inline comments do not need a mention. A Conversation comment starts follow-up work only when its exact Labor0 mention and instruction are both present; ordinary issue comments and mention-only comments are ignored.
For example, use an inline comment such as:
Or, when the request applies to the pull request as a whole, use a privacy-safe Conversation comment such as:
Do not include secrets, private diagnostics, or credentials. Labor0 stores only the exact GitHub comment URL and attribution for follow-up orchestration; the authorized review-context view fetches the current comment from GitHub ephemerally.
Read the guidance status
New agent-created pull requests include a Labor0 task status block in the guidance comment. An older guidance comment may not contain this block; in that case, follow its authenticated Labor0 task link for the current status.
The status block groups status into customer actions:
Current work identifies whether Labor0 is updating the pull request, addressing feedback, repairing checks, or resolving a conflict. Last updated changes when the displayed status or current work changes. When an immediate decision matters, use the authenticated task as the current source.
When eligible external feedback needs your approval, the same guidance action line also shows Review external feedback. It opens an authenticated Labor0 page for the oldest pending review request on that pull request. The link contains only the workspace and approval address; it does not reveal reviewer details, review content, provider data, or private terminal routing. Approving, rejecting, canceling, or expiring that request removes the link or advances it to the next pending request without changing Last updated unless the displayed status or current work also changes. Clearing a notification does not cancel the underlying request; the guidance link remains available while the request is pending.
Who can start follow-up work
Feedback from people and bots with GitHub Write, Maintain, or Admin access can start automatically. A bot on the effective workspace or project automatic-trust list can also start automatically even when its repository permission is lower or unavailable.
Feedback from a person or an untrusted bot with lower or unknown permission requires approval from the originating actor in Labor0. Use Review external feedback in the guidance comment or open the approval notification in the authenticated app. If you are signed out, Labor0 returns you to the same approval after sign-in. The project option Use repository permissions disables bot-specific automatic trust while still applying these permission and approval checks. Labor0 does not replay older ignored feedback; submit a new eligible review or comment, or make an eligible edit, after changing the policy.
What happens after feedback
- A question receives a concise GitHub reply without an unnecessary commit.
- Valid feedback updates the existing pull-request branch. A successful change may not receive a routine completion reply.
- Obsolete, invalid, or already-satisfied feedback receives an explanation without a cosmetic commit.
- Related review items may be handled together. Inline threads are resolved after the item is handled unless Labor0 needs clarification. Conversation comments have no review thread to resolve.
The follow-up control applies to future feedback. Turning it off does not cancel work already running, and feedback received while it is off is not replayed automatically. Feedback already queued before follow-ups were turned off is preserved and can start after you re-enable them. Re-enable follow-ups before submitting new feedback that Labor0 should handle.
Required-check failures and merge conflicts may start separate repair work when project policy allows it. Repairs update the same branch rather than creating a replacement pull request. Wait for the new commits and required checks before merging.
Permissions and security
Viewing task details, repairing work, and acting on a pull request can require different permissions. Keep public review feedback free of secrets and private diagnostics. Answer private input and approve protected actions only in Labor0, after confirming the link uses https://app.labor0.com.
If follow-up does not start
Do not merge while required checks, unresolved feedback, or conflicts remain.