Fixes commit signing ignoring git.enableCommitSigning

`getSigningConfig` only checked the repo's `commit.gpgsign`, so users who
enabled signing solely via VS Code's `git.enableCommitSigning` (without
`commit.gpgsign`) were reported as signing-disabled, and GitLens-driven
commits (e.g. the Commit Composer) wouldn't sign.

Threads the host override through `GitServiceConfig.signing.enabled` and
falls back to it when `commit.gpgsign` is unset/false (it can only enable
signing, never force it off). Regression from the standalone-packages refactor.

Author: ianhattendorf

CHANGELOG.md

@@ -46,6 +46,7 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 ### Fixed
 
 - Fixes opening the _Commit Graph_ in multi root workspace to the correct repo ([#5276](https://github.com/gitkraken/vscode-gitlens/issues/5276))
+- Fixes commit signing not being detected as enabled when only VS Code's `git.enableCommitSigning` setting is on (without `commit.gpgsign` set in Git config) — GitLens-driven commits (e.g. the _Commit Composer_) now sign in this case
 - Fixes the `gitlens.advanced.similarityThreshold` setting being ignored when computing Git status — rename detection in status, working changes (WIP), and stash file lists used Git's default threshold (50%) instead of the configured value
 - Fixes the `gitlens.advanced.similarityThreshold` setting being ignored when listing changed files for a diff — rename detection used Git's default threshold (50%) instead of the configured value
 - Fixes force push from the _Push_ command always using `--force-with-lease` (and `--force-if-includes`) and ignoring VS Code's `git.useForcePushWithLease` and `git.useForcePushIfIncludes` settings — the confirmation could offer a plain `--force` while GitLens still pushed with lease; it now honors the configured preference

packages/git-cli/src/providers/config.ts

@@ -433,11 +433,10 @@ export class ConfigGitSubProvider implements GitConfigSubProvider {
 		const sshProgram = configMap.get('gpg.ssh.program');
 		const allowedSignersFile = configMap.get('gpg.ssh.allowedsignersfile');
 
-		// Check if git config has commit signing enabled
-		const isEnabled = parseGitBoolean(enabledRaw);
-
-		// Note: To override commit signing, pass it via the host/caller.
-		// The library no longer reads a config for this.
+		// Check if git config has commit signing enabled, falling back to the host-level override
+		// (e.g. VS Code's `git.enableCommitSigning`) when `commit.gpgsign` is unset/false. The host
+		// override can only enable signing, never force it off.
+		const isEnabled = parseGitBoolean(enabledRaw) || this.context.config?.signing?.enabled === true;
 
 		return {
 			enabled: isEnabled,

packages/git/src/context.ts

@@ -96,6 +96,16 @@ export interface GitServiceConfig {
 		 */
 		readonly useForceIfIncludes?: boolean;
 	};
+
+	/** Commit-signing preferences. */
+	readonly signing?: {
+		/**
+		 * Host-level override for whether commit signing is enabled (e.g. VS Code's `git.enableCommitSigning`).
+		 * When `true`, signing is treated as enabled even if the repo's `commit.gpgsign` is unset/false. It never
+		 * forces signing off.
+		 */
+		readonly enabled?: boolean;
+	};
 }
 
 /** Git command types that can produce conflicts. */

src/git/gitProviderContext.ts

@@ -56,6 +56,11 @@ export function createGitProviderContext(container: Container): GitServiceContex
 				useForceIfIncludes: configuration.getCore('git.useForcePushIfIncludes') ?? true,
 			};
 		},
+		get signing() {
+			return {
+				enabled: configuration.getCore('git.enableCommitSigning'),
+			};
+		},
 	};
 
 	return {