taproot-manufacturing/entomologist
2
0
Fork 0
Code Issues 1 Pull requests 2 Projects Releases Packages Wiki Activity Actions

new description for issue 317ea8ccac1d414cde55771321bdec30

Browse source
This commit is contained in:
Sebastian Kuzminsky 2025-07-10 10:25:29 -06:00
parent 0e318f1357
commit efd4206b98
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
317ea8ccac1d414cde55771321bdec30/description
View file

@ -1,14 +1,14 @@
allow multiple read-only ent processes simultaneously allow multiple read-only ent processes simultaneously
Currently every time `ent` checks out a worktree of its "issues database", Currently every time `ent` makes a worktree to read its issues database
it uses the local branch `entomologist-data`. This means only one branch, it checks out the local branch `entomologist-data`. This means
worktree can exist at a time, because each branch can only be checked only one worktree can exist at a time, because each branch can only be
out into at most one worktree. checked out into at most one worktree.
Some ent operations are read-only which means we could `git worktree add` Some ent operations are read-only which means we could `git worktree
the `origin/entomologist-data` branch instead, which uses a detached HEAD add --detached` the `entomologist-data` branch instead, which uses a
checkout, which is sufficient for read-only operations like `ent list` detached HEAD checkout, which is sufficient for read-only operations like
and `ent show`. `ent list` and `ent show`.
This would be useful if you're sitting in `ent edit ${ISSUE_1}` and want This would be useful if you're sitting in `ent edit ${ISSUE_1}` and want
to look at another issue with `ent show ${ISSUE_2}` or list the issues to look at another issue with `ent show ${ISSUE_2}` or list the issues