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

Compare commits

base: taproot-manufacturing:cdb0f450d94b5daab31b55de5e0a4c14b8d0b632
Branches Tags
taproot-manufacturing:main
taproot-manufacturing:entomologist-data
taproot-manufacturing:tags-dir
taproot-manufacturing:03/entries
taproot-manufacturing:03/tui
..
compare: taproot-manufacturing:e3a47c5c37da1d5cb1f1063c2c6edba4e19bf8a2
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. "cdb0f450d94b5daab31b55de5e0a4c14b8d0b632" and "e3a47c5c37da1d5cb1f1063c2c6edba4e19bf8a2" have entirely different histories.
cdb0f450d9 ... e3a47c5c37

3 changed files with 2 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
317ea8ccac1d414cde55771321bdec30/state
View file

@ -1 +1 @@
done inprogress

2
9502937b139b797f94eb422651417757/description
View file

@ -1,4 +1,4 @@
`ent show`: visually distinguish issues and comments from each other visually distinguish issues and comments from each other
`git log` does it well: `git log` does it well:

3
fd81241f795333b64e7911cfb1b57c8f/description
View file

@ -6,6 +6,3 @@ It'd be nice to be able to look at the `git log --oneline` of an issue dir and s
* changing state or assignee * changing state or assignee
* adding a comment * adding a comment
* editing a comment * editing a comment
I think each kind of log message we want will correspond to a matching
API function in the entomologist crate.