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

Compare commits

base: taproot-manufacturing:2e244c21927118ae57127b50c759904724bef89d
Branches Tags
taproot-manufacturing:main
taproot-manufacturing:entomologist-data
taproot-manufacturing:tags-dir
taproot-manufacturing:03/entries
taproot-manufacturing:03/tui
..
compare: taproot-manufacturing:baa7cdd7e976f40d050dc923a93d11ac6dd31cde
Branches Tags
taproot-manufacturing:entomologist-data
taproot-manufacturing:tags-dir
taproot-manufacturing:main
taproot-manufacturing:03/entries
taproot-manufacturing:03/tui

No commits in common. "2e244c21927118ae57127b50c759904724bef89d" and "baa7cdd7e976f40d050dc923a93d11ac6dd31cde" have entirely different histories.
2e244c2192 ... baa7cdd7e9

2 changed files with 0 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

7
5fe71e27727f4243dc997e63b9a02971/description
View file

@ -1,7 +0,0 @@
add a way to see how an issue has changed over time
Maybe `ent log ISSUE` (and `ent log COMMENT`)?
This could be a thinly veiled wrapper around:
`git log entomologist-data -- ISSUE`

7
fd81241f795333b64e7911cfb1b57c8f/description
View file

@ -1,8 +1 @@
commit messages in the `entomologist-data` branch could be better
It'd be nice to be able to look at the `git log --oneline` of an issue dir and see:
* creating the issue
* editing the issue
* changing state or assignee
* adding a comment
* editing a comment