[FEATURE] Add DOTNET_AICOMMITMESSAGE_IGNORE_API_ERRORS environment variable to bypass AI API failures gracefully

[gitauto-ai]

Resolves #285

Summary

Introduce the DOTNET_AICOMMITMESSAGE_IGNORE_API_ERRORS environment variable to allow graceful fallback when AI API calls fail.

Changes

• Added a new environment variable check for DOTNET_AICOMMITMESSAGE_IGNORE_API_ERRORS.
• Updated API error handling to catch exceptions and log a warning when the variable is active.
• Implemented a fallback to continue processing and return the original or partially transformed message without interrupting the workflow.

git fetch origin
git checkout gitauto/issue-285-20250912-171517-Z3jS
git pull origin gitauto/issue-285-20250912-171517-Z3jS

[korbit-ai]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[korbit-ai]

I was unable to write a description for this pull request. This could be because I only found files I can't scan.

[deepsource-io]

DeepSource Code Review

DeepSource reviewed changes in the commit range 58cad28..9944c67 on this pull request. Below is the summary for the review, and you can see the individual issues we found as review comments.

For detailed review results, please see the PR on DeepSource ↗

PR Report Card

Security	× 0 issues		Overall PR Quality    Focus Area: Reliability Guidance Address the use of a generic `Exception` catch in Src/AiCommitMessage/Services/GenerateCommitMessageService.cs.
Reliability	× 1 issue
Complexity	× 0 issues
Hygiene	× 0 issues
Coverage	× 2 issues

Code Review Summary

Analyzer	Status	Summary	Details
Test coverage		2 new issues detected.	Review ↗
Secrets		No new issues detected.	Review ↗
Docker		No new issues detected.	Review ↗
C#		1 new issue detected.	Review ↗

How are these analyzer statuses calculated?

Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings.

Code Coverage Summary

Language	Line Coverage		Branch Coverage
	New Code	Overall	New Code	Overall
Aggregate	14.3%	46.1% [▼ down 0.9% from main]	0%	42.9% [▼ down 3.3% from main]
C#	14.3%	46.1% [▼ down 0.9% from main]	0%	42.9% [▼ down 3.3% from main]

➟ Additional coverage metrics may have been reported. See full coverage report ↗

[github-actions]

🔥 Formatting issues detected

File	Line

⚡ Please run dotnet csharpier . locally to fix the formatting issues.

[sonarqubecloud]

Quality Gate failed

Failed conditions
7.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-02-16T06:59:50Z INF scanning for exposed secrets...
6:59AM INF 265 commits scanned.
2026-02-16T06:59:50Z INF scan completed in 76.9ms
2026-02-16T06:59:50Z INF no leaks found

[sonarqubecloud]

Quality Gate failed

Failed conditions
7.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud