fix(git): increase commit timeout for slow pre-commit hooks

[C-W-D-Harshit]

What Changed

Increased the git commit command timeout from 30s to 120s.

Why

Repositories with slow pre-commit hooks (linting, type-checking, formatting) regularly exceed the hardcoded 30s default timeout, causing the commit to fail with a timeout error in the UI. The hook itself succeeds — it just needs more time.

The 120s limit matches common CI expectations for pre-commit hook runtimes while still catching genuinely stuck processes.

Only the commit path is changed. All other git operations keep the existing 30s default.

Fixes #1194

Checklist

• This PR is small and focused
• I explained what changed and why

Note

Increase git commit timeout to 120 seconds for slow pre-commit hooks

Replaces runGit with executeGit in GitCore.commit to pass an explicit timeoutMs: 120000 option, up from the previous default. This prevents premature failures when pre-commit hooks take a long time to run.

^{Macroscope summarized f13bf0d.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 013ab767-7168-4808-a467-06010bc0cb72

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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