Gitlab.com (and Gitlab EE) allows empty commit using Gitlab's web UI

Summary

Gitlab allows to commit empty changes using Gitlab's web UI (on both CE and EE).

Steps to reproduce

In your's gitlab repository, select a file you want to edit, select edit (top right corner). When edit view renders, do not make any changes and push commit changes button.

Empty changes are submitted into a commit using default commit message (Update my.file) onto master branch.

Example Project

Example of empty commit created with gitlab's web UI: trimailov/test-project@0f70b20c

What is the current bug behavior?

Empty commit is submitted. Which may produce unwanted outcome (useless empty commit on master in big corporate repo, triggering CI/CD pipeline, etc.).

What is the expected correct behavior?

Either empty commits should not be allowed or user should be notified, that empty commit is to be made.

Output of checks

This bug happens on GitLab.com (as well as using Gitlab EE)

P.S.

This may be a non-issue, if that's intended. Though from my point of view, I do not want to make useless commits by accident.