new description for issue 317ea8ccac1d414cde55771321bdec30
This commit is contained in:
parent
0e318f1357
commit
efd4206b98
1 changed files with 8 additions and 8 deletions
|
|
@ -1,14 +1,14 @@
|
|||
allow multiple read-only ent processes simultaneously
|
||||
|
||||
Currently every time `ent` checks out a worktree of its "issues database",
|
||||
it uses the local branch `entomologist-data`. This means only one
|
||||
worktree can exist at a time, because each branch can only be checked
|
||||
out into at most one worktree.
|
||||
Currently every time `ent` makes a worktree to read its issues database
|
||||
branch, it checks out the local branch `entomologist-data`. This means
|
||||
only one worktree can exist at a time, because each branch can only be
|
||||
checked out into at most one worktree.
|
||||
|
||||
Some ent operations are read-only which means we could `git worktree add`
|
||||
the `origin/entomologist-data` branch instead, which uses a detached HEAD
|
||||
checkout, which is sufficient for read-only operations like `ent list`
|
||||
and `ent show`.
|
||||
Some ent operations are read-only which means we could `git worktree
|
||||
add --detached` the `entomologist-data` branch instead, which uses a
|
||||
detached HEAD checkout, which is sufficient for read-only operations like
|
||||
`ent list` and `ent show`.
|
||||
|
||||
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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue