Commit Message Enforcement and Auto-Population in Microsoft Fabric Source Control

[abishekr]

In the Source Control interface within Microsoft Fabric, the commit message field is labeled as "Optional Commit Message." This allows users to commit changes without entering a message, which undermines traceability and governance in our deployment pipelines.

Additionally, when selecting a modified item (e.g., a report like Leads_Report), there is no auto-population of the commit message based on the selected file name. This leads to inconsistent commit logs and manual overhead.

Feature Requests:

Mandatory Commit Message Enforcement:

Commit button should remain disabled until a non-empty message is entered.
Ideally configurable at workspace or tenant level for governance enforcement.
Auto-Populate Commit Message Based on Selected Artifact:

When a user selects a modified report or dataset, the commit message field should auto-fill with a default format like:
"Update: Leads_Report"
This improves consistency and supports automated traceability workflows.

Environment:

Microsoft Fabric workspace
Source Control panel (DEV branch)
Artifact: Power BI report (Leads_Report)

Business Impact:
We are building automated governance pipelines that rely on structured commit messages for work item linking, audit trails, and rollback logic. Lack of enforcement and automation here introduces risk and manual effort.