Skip to content

Commit a19cf7c

Browse files
jerodwclaude
andcommitted
Name this board's Status options as this board spells them
The three moment options shipped as Planned, "In progress" and "Ready to merge"; this board's Status field carries Planned, "In Progress" and "Ready to Merge". Planned matched and moved, and the other two did not: story-131 announced its in_progress moment and got "Status in project 1 has no option named In progress, so 208 was not moved". The option name is compared verbatim while the field name is matched through same_field_name, so the capitalisation is the whole difference. That asymmetry is filed as its own brief; this is the target value that makes the two moments reachable meanwhile, set where target values live. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U1HiUf7CrMjZMj32TySdiH
1 parent 24966d9 commit a19cf7c

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

.harness/scripts/github.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -321,8 +321,8 @@ CATEGORY_LABEL_COLOR="ededed"
321321
# board saying "In Progress", "Doing" or "En cours" is a configuration rather
322322
# than an edit to the logic above it.
323323
PLANNED_OPTION="${L5_ITEM_PLANNED_OPTION:-Planned}"
324-
IN_PROGRESS_OPTION="${L5_ITEM_IN_PROGRESS_OPTION:-In progress}"
325-
READY_TO_MERGE_OPTION="${L5_ITEM_READY_TO_MERGE_OPTION:-Ready to merge}"
324+
IN_PROGRESS_OPTION="${L5_ITEM_IN_PROGRESS_OPTION:-In Progress}"
325+
READY_TO_MERGE_OPTION="${L5_ITEM_READY_TO_MERGE_OPTION:-Ready to Merge}"
326326

327327
# --- what only the query job uses. Edit these. ---------------------------
328328
# How many items one path's search may return. The harness bounds what it will

0 commit comments

Comments
 (0)