Completing Tasks in LatchLoop
This guide explains the two ways you can complete tasks in LatchLoop and what happens after a task is completed, especially when your work involves GitHub pull requests.
Ways to mark a task as complete
A. Manually mark complete
- Click the check icon on a task in the list or inside the task detail view to mark it as Complete.
- This action only updates the task’s status inside LatchLoop. It does not modify your code, branches, or GitHub in any way.
- Use manual completion for tasks that aren’t tied to an open pull request, tasks you’ve handled outside of LatchLoop, or tasks that are no longer relevant but you want to close.
- If a task is not actually complete and you simply want to hide it from active views, consider Archiving instead.
B. Automatically complete on PR merge
- When you merge a GitHub pull request that’s linked to a LatchLoop task, LatchLoop automatically marks the task as Complete.
- The task will also show a label indicating that the pull request was merged.
What happens after a task is completed
- Completed tasks appear in the Complete column (board view) and in filtered lists when you choose the Complete filter.
- If the Complete column is collapsed on your board, you can expand it to review recent completions.
- In the task detail view, you’ll see indicators that the related pull request was merged (when applicable).
Reopening a completed task to request more changes
Sometimes you merge a pull request and later discover additional changes are needed on the same branch (for example, a bug slipped through). You can continue using LatchLoop on the original task:
- Open the completed task directly or find it under your Completed tasks.
- Use the sidebar in the task detail view to request additional changes.
- LatchLoop will reopen the pull request and continue working on the same branch, applying the requested adjustments.
- The task status will automatically move back to PR Open when changes are requested.
- After review, you can merge the updated pull request again.
This means you do not need to create a brand-new task for follow-up work on an already-merged PR. Simply request changes on the existing, completed task and LatchLoop will take it from there.
Complete vs Archive
- Complete: Indicates the task’s goals were met or the linked PR was merged. The task remains accessible for follow-up work and history.
- Archive: Hides the task from active views when you don’t plan to work on it. You can unarchive later if needed.
Tips and notes
- Manual completion does not affect your repository or GitHub. It’s purely a status change inside LatchLoop.
- If a task was marked Complete by mistake, you can reopen it. In many places, clicking the checkmark on a completed task will toggle it back to Pending so you can continue working.
- For work that’s unrelated to the previously merged changes or requires a different scope, consider creating a new task to keep history and context clear.
FAQ
- Does marking a task Complete close or merge the PR? No. Manual completion only updates LatchLoop’s status and does not change anything in GitHub.
- Can I use LatchLoop after I’ve merged a PR? Yes. Open the completed task and request changes in the sidebar. LatchLoop will reopen the pull request and continue on the same branch.
- Do I need a new task if I discover a bug after merging? Not necessarily. You can request changes on the existing, completed task and LatchLoop will handle reopening the PR. Create a new task only if the follow-up work is unrelated or significantly different in scope.
- Where can I find completed tasks? Use the Complete filter in list view or expand the Complete column in board view.
Need more help?
- See Working on Pull Requests for details on reviewing, requesting changes, and merging.
- Review Tasks and Task Editor for task organization and description best practices.
- Explore Background Code Agent and Managing Context to control what LatchLoop considers when building or updating your PRs.