Craig Gardner

In the meantime, I found that you can add tasks in the notes that have to be marked off before you can mark a task as done. I'm trying out...

You do that by adding a task in the notes. `- [ ] my subtask`

@FearTheBadger There isn't a good way to expose the sub-tasks in the dstask interface at the moment. Sub-tasks are just a [task list in markdown](https://github.blog/2014-04-28-task-lists-in-all-markdown-documents/)

It's pretty simple, It just updates a file with templated value. https://www.ledger-cli.org/3.0/doc/ledger3.html#Time-Keeping So when I start a task, It'll just update my file with something like `i 2020/07/27 16:40:00 PROJECT:ProjectName`...

I've started going down this route with pretty much all of my tools. Here's an example of the `dstask` function that I've been working on with a stub for start...

I wonder how well the [git-hooks](https://git-scm.com/docs/githooks) could be used as a workaround. Specifically some custom pre and post commit script examples.

@naggie, @dontlaugh so is the `due` property when we edit tasks just a placeholder? It's in all of the tasks. It's in the code too here: https://github.com/naggie/dstask/blob/master/task.go#L53

> if you have a binary `git-command` why would you want to run it as `git command` ? For me, it fits nicely into the workflow and will work with...

It seems like there are some conflicts in these changes now.

@geddski I was having the same problem and the update seemed to do the trick. Thank you.