4 files changed, 21 insertions, 2 deletions
diff --git a/app/History.hs b/app/History.hs
index efb7015..48dbbc7 100644
--- a/app/History.hs
+++ b/app/History.hs
@@ -24,6 +24,7 @@ import Prelude hiding (id, lines)
 -- complete issue text and parse it.
 --
 -- @topic caching
+-- @backlog
 
 getHistory :: IO ([Issue], [(CommitHash, [IssueEvent])])
 getHistory = do
diff --git a/app/Issue/Filter.hs b/app/Issue/Filter.hs
index 7501e35..e8209a7 100644
--- a/app/Issue/Filter.hs
+++ b/app/Issue/Filter.hs
@@ -41,6 +41,8 @@ import Options.Applicative qualified as O
 --
 -- [1] Not in the sense that it is rejected, but in the sense that the negation
 -- is not parsed. It is just the literal value `!<v`.
+--
+-- @backlog
 data Filter = Filter Mode SimpleFilter deriving (Show)
 
 data Mode = Include | Exclude deriving (Show)
diff --git a/app/Main.hs b/app/Main.hs
index e367113..4d3902d 100644
--- a/app/Main.hs
+++ b/app/Main.hs
@@ -55,11 +55,13 @@
 --
 -- `--filter '(@assigned aforemny) OR (@due 2023-10-4)'`
 -- @topic tags
+-- @backlog
 
 -- TODO Tag improvements (globbing)
 --
 -- I would like to filter `--filter '@assigned *@posteo.de'`.
 -- @topic tags
+-- @backlog
 
 -- TODO Add support for ammendments
 --
@@ -83,6 +85,7 @@
 -- ```
 --
 -- @priority high
+-- @backlog
 --
 -- COMMENT Ammendments should generate IssueEvents which can be shown in the issue's log.
 
@@ -95,6 +98,7 @@
 --
 -- @topic show
 -- @topic options
+-- @backlog
 --
 -- COMMENT Do we expect the code BEFORE an issue to be ever relevant?
 --
@@ -121,6 +125,7 @@
 --
 -- @topic options
 -- @topic settings
+-- @backlog
 --
 -- COMMENT Can/ should this be made a feature of optparse-applicative, which we
 -- could fork? Like, can this work transparently if we fork
@@ -158,6 +163,7 @@
 -- ```
 --
 -- @topic ids
+-- @backlog
 --
 -- COMMENT Can you elaborate on why this would be useful? I am expecting us to
 -- do some renaming detection regarding provenance. After that, will it be
@@ -199,6 +205,7 @@
 --
 -- @topic markdown
 -- @topic tags
+-- @backlog
 
 -- QUESTION Should automatically generated ids be random?
 --
@@ -215,7 +222,7 @@
 -- issues.
 --
 -- @topic ids
--- @scheduled 2023-10-30
+-- @backlog
 --
 -- COMMENT I am not sure we want to automatically append `@id`s to the issue
 -- description. We probably want to append `@pastId` to an issue if we notice a
@@ -253,6 +260,7 @@
 -- The items should be ordered with the most blocking issues at the top.
 --
 -- @topic dependencies
+-- @backlog
 
 -- TODO Relations between issues
 --
@@ -277,6 +285,7 @@
 -- to persist the index in a local cache.
 --
 -- @topic search
+-- @backlog
 
 -- TODO Display issue type in list and show views
 --
@@ -285,6 +294,7 @@
 -- should be grouped by the type.
 --
 -- @difficulty easy
+-- @backlog
 --
 -- COMMENT I imagine emojis might be off-putting to some potential users. I
 -- would like a configuration option to disable emojis and display the marker
@@ -340,7 +350,7 @@
 --
 -- @topic options
 -- @topic cache
--- @scheduled 2023-10-30
+-- @backlog
 --
 -- COMMENT What is the point of this command? Can't caches be handled
 -- transparently to the user?
@@ -374,6 +384,7 @@
 --
 -- @topic options
 -- @topic cache
+-- @backlog
 
 -- TODO Add format option (Text, JSON, ...)
 --
@@ -389,6 +400,7 @@
 --
 -- @topic rendering
 -- @topic options
+-- @backlog
 
 -- TODO Add HTTP server
 --
@@ -403,6 +415,8 @@
 -- The JSON-Api offers endpoints `GET /<commit>/` which returns `anissue
 -- list` as `GET /<commit>/<issue-id>/` which returns `anissue show`.
 -- All command line arguments are exposed via query parameters.
+--
+-- @backlog
 
 module Main where
 
diff --git a/app/TreeGrepper/Comment.hs b/app/TreeGrepper/Comment.hs
index c912e27..1a6aed2 100644
--- a/app/TreeGrepper/Comment.hs
+++ b/app/TreeGrepper/Comment.hs
@@ -64,6 +64,8 @@ treeGrepperLanguage ext =
   --
   -- tree-grepper supported files can be listed through `tree-grepper
   -- --languages`.
+  --
+  -- @backlog
   case ext of
     ".elm" -> "elm"
     ".hs" -> "haskell"