github-issue-state-management

Using GitHub Issues as a Single Source of Truth enables cross-environment state management by embedding environment metadata within Issue bodies. This provides a unified view of status, phase, and configuration accessible from container-use, worktree, and host environments.

Using GitHub Issue labels for environment state tracking leverages GitHub's atomic label operations to prevent race conditions. This structured label system ensures consistent status and phase tracking even when multiple processes attempt simultaneous state manipulation.

Yes, you can track environment statuses like 'active', 'blocked', or 'PR created' using a structured GitHub Issue label system. This enables seamless resumption and coordination of development work across multiple worktrees and container contexts.

Centralizing state data using GitHub Issues is the best way to synchronize development environment state across contexts. This resolves cross-environment file access issues by making host, worktree, and container environments reference the same Issue metadata.

To register a new environment state, use CLI scripts to assign an environment ID, branch name, and type to a specific GitHub Issue number. The system persists this metadata within the Issue body for detailed state recovery and tracking.