diff options
author | Alexander Foremny <aforemny@posteo.de> | 2024-03-14 07:04:09 +0100 |
---|---|---|
committer | Alexander Foremny <aforemny@posteo.de> | 2024-03-14 07:07:45 +0100 |
commit | e0ffe3e85faf4a52fbacf56edc6067c44773a8b1 (patch) | |
tree | 4ec622f8e808207b2fd1342eb2c7cc78da1ddf2b | |
parent | 1821aca5ef5451d0b1943c8640c5eb1f6fa7bbee (diff) |
chore: add future review todos
-rw-r--r-- | app/Main.hs | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/app/Main.hs b/app/Main.hs index 2729511..d49f627 100644 --- a/app/Main.hs +++ b/app/Main.hs @@ -1,3 +1,39 @@ +-- TODO Add `anissue review-comments` +-- +-- The command `review-comments` should list all review comments within the current review. +-- +-- @assigned aforemny +-- @priority medium +-- @topic review + +-- TODO `anissue review --base` should take own commits into account +-- +-- To facilitate reviewing, the `--base` parameter of `anissue review` should implement some heuristic to review a set of changes multiple times. +-- +-- The first time a review is performed, `--base` should default to the base branch. Any subsequent time, it should default to the last review commit added by myself. +-- +-- @assigned aforemny +-- @priority high +-- @topic review + +-- TODO Add `anissue merge` +-- +-- The command `anissue merge` should merge the currenlty checked out feature request, if there are no unresolved review comments. +-- +-- If there are unresolved review comments, it should fail with a warning. +-- +-- @assigned aforemny +-- @priority high +-- @topic review + +-- TODO Add `anissue request-review` +-- +-- The command `request-review` should create an empty commit, stating that a review is requested. It should mention the eventual "base branch" for inclusion of the feature. +-- +-- @assigned aforemny +-- @priority high +-- @topic review + -- TODO Compute history from the top -- -- Currently we are computing the history from the bottom (ie. earliest commit |