diff options
author | EuAndreh <eu@euandre.org> | 2020-11-07 11:32:07 -0300 |
---|---|---|
committer | EuAndreh <eu@euandre.org> | 2020-11-07 11:33:10 -0300 |
commit | fb2bbfbbd1f53e849d4f6a3f74c1af0a0838bca4 (patch) | |
tree | 88376572395fc9e29cb9d0061b4df75bddc7648d /_articles | |
parent | Update "Datomic on global" slides, as presented (diff) | |
download | euandre.org-fb2bbfbbd1f53e849d4f6a3f74c1af0a0838bca4.tar.gz euandre.org-fb2bbfbbd1f53e849d4f6a3f74c1af0a0838bca4.tar.xz |
DIY todos bugs: spell-checking
Diffstat (limited to '')
-rw-r--r-- | _articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md b/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md index 0eff520..e9d1b6b 100644 --- a/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md +++ b/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md @@ -80,7 +80,7 @@ existing workflow for source code and documentation. I like to keep a [`TODOs.org`][todos-org] file at the repository top-level, with two relevant sections: "tasks" and "bugs". Then when building the documentation I'll just [generate an HTML file from it][org-mode-to-html], and -[publish][published-todos] it alonside the static website. All that is done on +[publish][published-todos] it alongside the static website. All that is done on the main branch. Any issues discussions are done in the mailing list, and a reference to a @@ -94,11 +94,10 @@ For the other 1%, having Fossil's "[tickets][fossil-tickets]" could be an alternative, but you may not want to migrate your project to Fossil to get those niceties. -Even though I keep a `TODOs.org` file on the main branch, you may pick any name -you like, or use a dedicated branch just for that, split tasks and bugs into -different files, or have one file for each. +Even though I keep a `TODOs.org` file on the main branch, you can have a `tasks` + branch with a `task-n.md` file for each task, or any other way you like. -These tools are familliar enough that you can adjust it to fit your workflow. +These tools are familiar enough that you can adjust it to fit your workflow. [todos-org]: https://git.euandreh.xyz/mediator/tree/TODOs.org [org-mode-to-html]: https://git.euandreh.xyz/mediator/tree/scripts/build-site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14 |