Summary

Add a retry mechanism to commit message generation so that transient LLM failures or empty responses are automatically retried instead of surfacing as errors to the user.

Context

Commit message generation relies on an LLM call, which can occasionally fail transiently or return an empty message due to model hiccups, rate limits, or network blips. Previously these failures would propagate immediately as errors, forcing the user to manually re-invoke the command. This change wraps the generation call in the project's existing retry_with_config infrastructure, providing automatic resilience.

Changes

• Derived Clone on DiffContext so it can be passed into the retry closure on each attempt
• Wrapped generate_message_from_diff with retry_with_config, pulling retry settings from the project config (services.get_config().retry)
• Added an empty-message guard that returns a Retryable error when the LLM produces an empty commit message, triggering a retry rather than silently returning a blank string

Key Implementation Details

The retry configuration is sourced from get_config().retry, falling back to RetryConfig::default() when not set. The empty-message check is placed after parsing the LLM response so only the generation + parse step is retried — not the diff truncation or context-building logic.

Testing

# Run the forge_app crate tests
cargo insta test --accept -p forge_app

# Verify the build
cargo check -p forge_app

Links

• No related issues