multica-ai/multica · warning
nothing to update — provide --name and/or --color
Error message
nothing to update — provide --name and/or --color
What it means
Thrown by `multica label update` when neither --name nor --color is provided (both default to empty and the body map stays empty). The CLI refuses to send a no-op PATCH/PUT rather than issuing an empty update request.
Source
Thrown at server/cmd/multica/cmd_label.go:224
return err
}
ctx, cancel := cli.APIContext(context.Background())
defer cancel()
labelRef, err := resolveLabelID(ctx, client, args[0])
if err != nil {
return fmt.Errorf("resolve label: %w", err)
}
body := map[string]any{}
if v, _ := cmd.Flags().GetString("name"); v != "" {
body["name"] = v
}
if v, _ := cmd.Flags().GetString("color"); v != "" {
body["color"] = v
}
if len(body) == 0 {
return fmt.Errorf("nothing to update — provide --name and/or --color")
}
var result map[string]any
if err := client.PutJSON(ctx, "/api/labels/"+labelRef.ID, body, &result); err != nil {
return fmt.Errorf("update label: %w", err)
}
output, _ := cmd.Flags().GetString("output")
if output == "table" {
headers := []string{"ID", "NAME", "COLOR"}
rows := [][]string{{
strVal(result, "id"),
strVal(result, "name"),
strVal(result, "color"),
}}
cli.PrintTable(os.Stdout, headers, rows)
return nil
}View on GitHub (pinned to 2c0912b6ec)
Solutions
- Provide at least one field: `multica label update bug --color #22c55e`
- Use `multica label get` to inspect a label instead of update
- In scripts, assert at least one of NAME/COLOR is set before invoking update
Example fix
# before multica label update bug # after multica label update bug --name defect --color #ef4444
Defensive patterns
Strategy: validation
Validate before calling
# bash: require at least one update field
[[ -n "${NAME:-}" || -n "${COLOR:-}" ]] || { echo "nothing to update" >&2; exit 2; } Prevention
- Never run bare `label update REF`
- Use `label get` to inspect, update only with fields
- Scripts should assert at least one field is set
When it happens
Trigger: Running `multica label update bug` with no further flags, or with both flags set to empty strings.
Common situations: Users run update expecting an interactive prompt; scripts conditionally build flags and skip both branches; users try to use update to 'view' a label.
Related errors
- --name is required
- --color is required (e.g. #3b82f6)
- --kind must be schedule or webhook
- --cron is required for --kind schedule
- --timezone is only valid with --kind schedule
AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15).
Data as JSON: /api/errors/281dfbb2e2668b87.
Report an issue: GitHub.