Shelving Work in Progress
Temporarily set aside in-progress architectural changes without creating a checkpoint. Shelved work can be listed, restored, and deleted, enabling clean context switching between tasks.
When you need to switch context quickly, shelving lets you set aside uncommitted changes without losing them. Unlike creating a checkpoint, shelved work is not part of the permanent history. It is a temporary holding area for work-in-progress.
When to Shelve
Context Switching
You are working on schema changes and need to review a colleague's diagram modifications. Shelve your schema work, switch tracks, review, then restore.
Experimental Changes
You are trying a new architectural approach but are not ready to commit. Shelve the experiment, return to the stable state, and restore later if the approach works.
Urgent Fixes
A critical fix is needed on the main track. Shelve your current work, switch to main, apply the fix, then restore your shelved changes.
Clean Working Tree
Some operations (baseline creation, track switching) require a clean working tree. Shelving clears your uncommitted changes temporarily.
How to Shelve
Managing Shelved Work
| Action | Description |
|---|---|
| List | View all shelved items with descriptions and timestamps |
| Restore | Apply shelved changes back to the working tree. The shelved item is removed from the list. |
| Delete | Permanently discard a shelved item without restoring it |
Deep Git Integration
NeoArc wraps Git with architecture-first concepts: checkpoints instead of commits, tracks instead of branches, baselines instead of tags. Semantic diff, conflict resolution, drift analytics, and shelving provide a complete governance workflow.