fix: correct fetchRecurseSubmodules key lookup in from_gitmodules

[Copilot]

SubmoduleEntry::from_gitmodules was looking up "fetchRecurse" instead of "fetchRecurseSubmodules", the actual key used by git in .gitmodules. This caused fetch_recurse to always parse as None when reading gitmodules data.

Changes

• src/config.rs: Updated from_gitmodules to check "fetchRecurseSubmodules" first, falling back to "fetchRecurse" for backward compatibility:

// Before
let fetch_recurse = entries
    .get("fetchRecurse")
    .and_then(|fr| SerializableFetchRecurse::from_gitmodules(fr).ok());

// After
let fetch_recurse = entries
    .get("fetchRecurseSubmodules")
    .or_else(|| entries.get("fetchRecurse"))
    .and_then(|fr| SerializableFetchRecurse::from_gitmodules(fr).ok());

This aligns from_gitmodules with the rest of the codebase (git2_ops.rs, gix_ops.rs, options.rs) which consistently uses fetchRecurseSubmodules as the git config key.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Pull request overview

Fixes parsing of the git submodule fetchRecurseSubmodules setting when reading .gitmodules by updating SubmoduleEntry::from_gitmodules to use the correct key (with a fallback for legacy input).

Changes:

• Read fetchRecurseSubmodules first when parsing gitmodules entries.
• Fall back to fetchRecurse for backward compatibility.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.