handle read-only operations #16

Merged
seb merged 2 commits from read-only-ops into main 2025-07-11 10:11:44 -06:00
Owner

Some operations only need read access to the issues database. This PR runs those operations in a detached worktree, so they don't interact with long running read-write operations like ent edit.

Some operations only need read access to the issues database. This PR runs those operations in a detached worktree, so they don't interact with long running read-write operations like `ent edit`.
seb added 2 commits 2025-07-10 13:10:13 -06:00
This makes a detached worktree, useful for read-only operations on the
issues database branch.
This makes each command in `handle_command()` handle its own issues
database.  The commands that only need read-only access to the issues
make a detached worktree, while the commands that need read-write access
make a normal worktree with the `entomologist-data` branch checked out.

This lets us run any number of read-only operations (like `ent list`,
`ent show`, etc), even when a long-lived read-write operation (like
`ent new` or `ent edit`) is running.

Fixes `ent 317ea8ccac1d414cde55771321bdec30`.
seb merged commit 0d6c43d266 into main 2025-07-11 10:11:44 -06:00
seb deleted branch read-only-ops 2025-07-11 10:11:44 -06:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: taproot-manufacturing/entomologist#16
No description provided.