Commit & Close: finish tasks without leaving your IDE
Finish work in the IDE. Vi commits the code and updates the board — one action replaces the whole "update the ticket" ritual.
Done in VS Code. Board updated automatically — the 40-second Commit & Close demo.
The code is done. The board doesn't know.
Developers finish the code, but the project board stays outdated — because updating the ticket is a separate, manual step in a browser tab. Someone has to find the ticket, change its status, write a note, and get back to the editor. Multiply that by every task, every developer, every day, and the tracker becomes a fiction that managers chase in standups.
How Commit & Close works
The developer selects a task in the IDE — their one active In Progress task.
When the code is ready, they mark the task as Done — still inside the IDE.
Vi stages the changes and creates a task-aware commit like "[#142] Fix auth bug".
Vi pushes to Git — locally, with the developer's own credentials.
Vi closes the task and moves it through the workflow — into Review, approval, or Done.
The project board updates automatically. Managers see real status — no chasing.
Why it matters
Developers stay in the IDE
No tab switching, no hunting for tickets. The whole task lifecycle happens where the code is written.
Managers see real status
The board reflects what actually shipped, because updating it is part of shipping — not a favor someone remembers to do.
Git and workflow stay connected
Every commit is linked to its task, so history, reviews, and tickets always line up.
Less context switching
Fewer manual ticket updates means more uninterrupted coding time — every day, for every developer.
One active task per developer
Vi enforces a focused execution model: each developer can have only one task In Progress at a time. Commit & Close completes that task and frees the slot for the next one. The result is less parallel unfinished work, an accurate workload picture, and a board where "In Progress" actually means in progress.
Your code never leaves your machine
All Git operations — stage, commit, push — run locally on the developer's machine through the Vi IDE extension. Vi never accesses, stores, or uploads source code. It orchestrates the task workflow; your repository stays yours.
Where you can use Commit & Close
- VS Code — Available
- RAD Studio — Under Review
- Visual Studio — In Testing
- Lazarus — In Testing
- JetBrains IDEs — Planned
Frequently asked
What is Commit & Close?
Commit & Close is Vi's branded workflow action: a developer marks a task as Done from the IDE, and Vi stages the changes, creates a task-aware commit, pushes to Git, closes the task, and updates the project board automatically.
Does Vi access my source code?
No. All Git operations run locally on the developer's machine through the Vi IDE extension. Vi never accesses, stores, or uploads source code — it only orchestrates the task workflow.
Does Commit & Close work with Git?
Yes. Commit & Close is built on Git: it stages your changes, writes a task-aware commit message like "[#142] Fix auth bug", and pushes to your remote — using your local Git configuration and credentials.
Can a developer have multiple tasks in progress?
No. Vi enforces one active In Progress task per developer. This focus rule prevents parallel unfinished work and keeps the board an accurate picture of what is actually being worked on.
What happens after a task is marked Done?
Vi stages the changed files, creates a task-aware commit, pushes to Git, closes the task, and advances it through the workflow — for example into a Review step with its approval chain, if your workflow defines one.
Does Commit & Close update the project board?
Yes. The task is moved to Done (or the next workflow step) and the project board updates automatically — managers see real project status without anyone editing tickets in a browser.
Keep exploring: Git-aware project management · project management in VS Code · IDE project management