From e63870ff767453c8fad13c5ad9abe98baf05da99 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 28 Jul 2026 16:47:48 +0300 Subject: [PATCH] Make mautrix-linkedin honor matrix_bridge_mautrix_linkedin_command_prefix The variable was defined, but the configuration template hardcoded the command prefix, so changing the variable had no effect. Co-Authored-By: Claude Opus 5 (1M context) --- .../matrix-bridge-mautrix-linkedin/templates/config.yaml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-linkedin/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-linkedin/templates/config.yaml.j2 index d3e596f2d..c45f7c561 100644 --- a/roles/custom/matrix-bridge-mautrix-linkedin/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-linkedin/templates/config.yaml.j2 @@ -15,7 +15,7 @@ network: # Config options that affect the central bridge module. bridge: # The prefix for commands. Only required in non-management rooms. - command_prefix: '!li' + command_prefix: {{ matrix_bridge_mautrix_linkedin_command_prefix | to_json }} # Should the bridge create a space for each login containing the rooms that account is in? personal_filtering_spaces: {{ matrix_bridge_mautrix_linkedin_bridge_personal_filtering_spaces | to_json }} # Whether the bridge should set names and avatars explicitly for DM portals.