From 89b9eb32939356aaa023c58c893a2abcdb61f098 Mon Sep 17 00:00:00 2001 From: Sebastian Kuzminsky Date: Wed, 9 Jul 2025 12:55:39 -0600 Subject: [PATCH] update 'description' in issue bed47b2be016cc41eb43ef6d0acf1f8f --- bed47b2be016cc41eb43ef6d0acf1f8f/description | 22 ++++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-) diff --git a/bed47b2be016cc41eb43ef6d0acf1f8f/description b/bed47b2be016cc41eb43ef6d0acf1f8f/description index 6b7ac88..18967cd 100644 --- a/bed47b2be016cc41eb43ef6d0acf1f8f/description +++ b/bed47b2be016cc41eb43ef6d0acf1f8f/description @@ -1,6 +1,20 @@ -add some way to un-assign an issue +make issue assignment more flexible -This will probably involve removing the `assignee` file from the issue -directory, which will mean teaching the git code about removed files. +I think there are two things i want that don't currently work: +* add some way to un-assign a person from an issue +* support multiple people assigned to the same issue -Or maybe write the empty string to that file? +Maybe the `assignee` field of the Issue struct should be a Vec +instead of String? And the `assignee` file of the issue directory should +be a list, one assignee per line? + +Possible new CLI ui: + +* `ent assign ISSUE PERSON[,PERSON...]` replaces the `assignee` list + with the new user-specified list. +* `ent assign ISSUE +PERSON` adds PERSON to the list +* `ent assign ISSUE -PERSON` removes the PERSON from the list + +Also support removing the `assignee` file from the issue directory if the +list is empty. Or maybe allow the file to exist but with 0 bytes in it? +Probably either one is fine.