Nicolas Suzor c8187137f5 fix(utils): prevent nil pointer panic in ResolvePartialID (#1132) ...

Add nil check at start of ResolvePartialID to return a proper error
instead of panicking when storage interface is nil.

Root cause: When bd refile (or other commands) is called with a nil
storage, calling store.SearchIssues() panics with SIGSEGV. This can
happen when routing fails to initialize storage properly.

Now returns: "cannot resolve issue ID <id>: storage is nil"

Fixes: bd-7ypor

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-17 00:00:56 -08:00

4.8 KiB

Raw Blame History

View Raw