Add a custom rule to enforce conventions in rule metadata

[btmills]

Forking this from discussion on #6915.

The problem you want to solve.

Most of our rule descriptions begin with lowercase letters. #6915 corrected two that didn't. Right now, we have no automatic verification of conventions there.

Your take on the correct solution to the problem.

@ilyavolodin We should think about adding a custom rule for this.

@vitorbal sounds good, maybe the custom rule could also enforce that the description starts with one of "enforce", "require", "disallow", etc.?
When we make it so the title of each rule page also comes from the meta.description we will benefit even more from this consistency.

[vitorbal]

I'm willing to work on this if it get's accepted. Except if you'd like to take a stab at it, @btmills!

[btmills]

@vitorbal all yours!

[platinumazure]

Dang, we haven't had any movement here in a while.

I'm in favor, but I'm not sure if this requires TSC consensus. @btmills What are our next steps here?

[btmills]

Since this isn't so much a core feature as it is an internal chore, I can't think of anything that would require TSC here. Next step be consensus and acceptance. I'll add my 👍. @vitorbal since you're willing to implement, are you also championing? It looks like @ilyavolodin 👍'd my original comment, so assuming that counts as another (ref #6424 (comment)), that would give us 3 including a champion.

[vitorbal]

Sure, I'll champion!
On Sun, Sep 4, 2016 at 10:53 PM Brandon Mills notifications@github.com
wrote:

Since this isn't so much a core feature as it is an internal chore, I
can't think of anything that would require TSC here. Next step be consensus
and acceptance. I'll add my 👍. @vitorbal https://github.com/vitorbal
since you're willing to implement, are you also championing? It looks like
@ilyavolodin https://github.com/ilyavolodin 👍'd my original comment,
so assuming that counts as another (ref #6424 (comment)
#6424 (comment)),
that would give us 3 including a champion.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6954 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmNdm9e02ZJix5WAji5I6dP9O6lJuytks5qmy-wgaJpZM4JpZMz
.

[vitorbal]

PR is up here: #7155