Hi @NotebookEnjoyer ,
Actually, allowing empty commit messages in Fabric’s git integration isn’t really a best practice, and it surprises me too that it’s possible by default. I’d guess the reason is just to keep the integration flexible and as close as possible to standard git behavior, where technically you can do commits with no message (even though, almost nobody recommends it for production work). Sometimes, for quick testing or automation scenarios, people might want to skip the message, but honestly, it usually brings more trouble than benefit.
Personally, I’d always suggest enforcing a commit message policy if your team or project cares about traceability and code quality. If there isn’t an option for enforcement in the UI right now, maybe you could use a pre-commit hook on your repo or raise a suggestion to the Fabric team.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
