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

create new issue 46317396704f388542daa7cb56d50076

Browse source
This commit is contained in:
Sebastian Kuzminsky 2025-07-12 13:28:50 -06:00
parent e0624d9dc8
commit 9970f3960d
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
46317396704f388542daa7cb56d50076/description Normal file
View file

@ -0,0 +1,20 @@
put ent issue database in a dir in the main branches?
Currently entomologist can access an issue database in a branch (via
temporary worktrees), or in a directory (via direct access).
The directory-based issue database mode is kind of broken, because
entomologist blindly runs `git commit` after modifying the database
(and isn't careful about managing the git index when doing so).
(Tangent: The IssueDatabase and IssueDatabaseSource structs of the `ent`
binary should maybe move into the lib Issues struct, and the code could
make smarter choices about how to access the database.)
Putting the entomologist issue database in the main branch(es) of the
repo has some appealing qualities. For example, a bug-fix branch could
both fix the bug in the code, and change the bug's issue status from
"InProgress" to "Done", so that when the branch is merged to main,
the bug gets fixed there.
The branch can be rebased on top of main to pick up changes to the bug.