diff options
| author | Arun Isaac | 2022-07-08 01:46:40 +0530 |
|---|---|---|
| committer | Arun Isaac | 2022-07-08 01:46:40 +0530 |
| commit | f281238321377710b99a78671287d2ae6a58338c (patch) | |
| tree | c0c7c244e7bb4b2f76f207852a036a726b786a3f /issues | |
| parent | 34b45c3e2bc87984cd7b60ad0680c3b092960585 (diff) | |
| download | tissue-f281238321377710b99a78671287d2ae6a58338c.tar.gz tissue-f281238321377710b99a78671287d2ae6a58338c.tar.lz tissue-f281238321377710b99a78671287d2ae6a58338c.zip | |
issues: Request GitHub-like milestones.
* issues/github-like-milestones.gmi: New file.
Diffstat (limited to 'issues')
| -rw-r--r-- | issues/github-like-milestones.gmi | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/issues/github-like-milestones.gmi b/issues/github-like-milestones.gmi new file mode 100644 index 0000000..cd4f9b1 --- /dev/null +++ b/issues/github-like-milestones.gmi @@ -0,0 +1,15 @@ +# GitHub-like milestones + +* tags: enhancement + +GitHub provides a "milestones" feature to track progress on a group of issues. This could be a set of issues that need to be resolved before releasing the next version of your software, for example. +=> https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones GitHub milestones + +We could implement a similar feature by adapting our task lists. When task lists specify paths to other issue files, we can recognize these as milestone-like lists, and automatically check/uncheck them based on the status of the referenced issues. Here is what such a milestone-like list might look like. +``` +* [] /issues/internationalize.gmi +* [] /issues/add-emacs-interface.gmi +* [] /issues/paginate-results.gmi +``` + +What heuristics do we use to distinguish these milestone-like lists from regular task lists? In other words, how do we identify paths to other issue files reliably? Should we also allow relative paths to issue files? |