I'm not sure that's blocking plugin commits without a changelog posting to
the wiki page is the best way to address your concern, or maybe I'm
misunderstanding your proposal.
For me, at least, a plugin release is typically composed of multiple
commits. Many of those commits are not relevant to th
Is it possible to alter the commit rules to prevent plugin commits unless
accompanied by a reasonable description of the change?
I'm seeing lots of changes lately with no idea of the nature or danger of the
change, and therefore no idea of why I need to install it or maybe hold off on
a poorly
