Compare commits
No commits in common. "1cb4c08db239d65cf733576a26dfc040a446448d" and "676a8ff168306b99d94922c2dbde89622162dc03" have entirely different histories.
1cb4c08db2
...
676a8ff168
5 changed files with 4 additions and 30 deletions
|
|
@ -35,26 +35,11 @@ or a due date this week.
|
|||
|
||||
## Done last week
|
||||
|
||||
I can imagine finding the issues with state=done, running `git log` on
|
||||
their state file, finding the datetime of the transition to done, and
|
||||
selecting the ones where that datetime is in a particular time window.
|
||||
I can imagine finding the issues with state=done, running `git log`
|
||||
on their state file, finding the datetime of the transition to done,
|
||||
and selecting the ones where that datetime is in a particular time window.
|
||||
|
||||
This has the drawback that it's hard to lie about... With taskwarrior
|
||||
I often found myself finishing a task on Week X, but forgetting to mark
|
||||
it complete. Then the Monday of Week X+1 i would mark it complete.
|
||||
If i didn't override the completion-date the task would look like it
|
||||
was completed on Week X+1, not Week X like i wanted.
|
||||
|
||||
In git we have `git commit --date=DATE`, but that's only usable at
|
||||
commit-time (and awkward to express to ent). We can rewrite history with
|
||||
`git rebase`, but only until we `ent sync`.
|
||||
|
||||
Maybe the `state` file should have a date in it, in addition to the
|
||||
state word? Or maybe `completion-date` should be a key in a per-issue
|
||||
key-value store? Is that kv store related to tags? Idk...
|
||||
|
||||
Not sure how to express to ent what completion-dates i want to see.
|
||||
Maybe a new filter type? `ent list finished=2025-07-01..now`?
|
||||
Not sure how to express to ent that that is what i want though.
|
||||
|
||||
Maybe we can use git tags in the entomologist-data branch somehow?
|
||||
`git log` between tags and look for "state: _ -> done". But how to
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
Oops, i stupidly ran: ent new "add `ent sync --dry-run`"
|
||||
|
||||
Because i used double-quotes, bash saw the `...` and ran that as a
|
||||
command, which failed, but then bash ran the result anyway ("ent new
|
||||
"add "), and here we are.
|
||||
|
||||
This would be a good time for `ent rm` as suggested by issue
|
||||
1ebdee0502937bf934bb0d72256dbdd1.
|
||||
|
|
@ -1 +0,0 @@
|
|||
add
|
||||
|
|
@ -1 +0,0 @@
|
|||
wontdo
|
||||
|
|
@ -1 +0,0 @@
|
|||
add `ent sync --dry-run`
|
||||
Loading…
Add table
Add a link
Reference in a new issue