test: add test for disable command with matching submodule name

This commit adds a test to ensure full test coverage for the scenario
where `.gitmodules` contains an entry exactly matching the configuration
name instead of falling back to searching by path. This verifies that
when a submodule is added manually to `.gitmodules` using its configured
name, `submod disable <name>` will find it and correctly update the
`active = false` property in `.gitmodules`.

Co-authored-by: bashandbone <89049923+bashandbone@users.noreply.github.com>

Author: google-labs-jules[bot]

tests/integration_tests.rs

@@ -566,6 +566,39 @@ active = true
         assert!(gitmodules_content.contains("active = false"));
     }
 
+    #[test]
+    fn test_disable_command_matching_name() {
+        let harness = TestHarness::new().expect("Failed to create test harness");
+        harness.init_git_repo().expect("Failed to init git repo");
+
+        // Manually create a .gitmodules with a matching name
+        let gitmodules_content = "\
+[submodule \"my-lib\"]
+\tpath = lib/my
+\turl = https://example.com/my-lib.git
+";
+        std::fs::write(harness.work_dir.join(".gitmodules"), gitmodules_content)
+            .expect("Failed to write .gitmodules");
+
+        let config_content = "\
+[my-lib]
+path = \"lib/my\"
+url = \"https://example.com/my-lib.git\"
+active = true
+";
+        harness.create_config(config_content).expect("Failed to create config");
+
+        let stdout = harness
+            .run_submod_success(&["disable", "my-lib"])
+            .expect("Failed to disable submodule");
+
+        assert!(stdout.contains("Disabled submodule 'my-lib'"));
+
+        let gitmodules_updated = std::fs::read_to_string(harness.work_dir.join(".gitmodules"))
+            .expect("Failed to read .gitmodules");
+        assert!(gitmodules_updated.contains("active = false"));
+    }
+
     #[test]
     fn test_disable_command_preserves_comments() {
         let harness = TestHarness::new().expect("Failed to create test harness");