There is an option named allow_empty_commits that controls whether an empty commit is allowed. However, it is true by default, and:

1. caused a lot of confusion. This package commits every hour and the developer doesn't know how to stop it;
2. did not make sense. There is no effect to push an empty commit to AUR, which only contains files for building and packaging.

--allow-empty has been added since the initial commit with no reason. So I assume that it is kept true for backward compatibility.

I suggest making it false by default.

Q: But it is a break change...!

I don't think the change will really "break" anyone's workflow. After all, you can publish a new major version for it.