It is related to Sizzle and Testing more than Build. Like I said, this is not a firm match for any component. And I don't think we need to be legalists here. Let's add component names where they helpfully provide scope for the commit.
Everything Grunt related is definitely Build. You won't be able to make exceptions like this once we start programmatically checking commit message format, so you might as well get used to it now.
There is no "definite" about this. There is a reason why Grunt is now called a task manager rather than just a build tool. This seems like a case where strict adherence to guidelines has steered us away from what is suitable and helpful, but I concede that this is the exception rather than commonplace. That said, I'm all in favor of automating consistency enforcement. This is just the sacrifice that we make.
This comment has been minimized.
markelog repliedJan 3, 2014
You forgot to add component name in front of the commit message
This comment has been minimized.
timmywil repliedJan 3, 2014
No, I the omission was intentional. This isn't firmly related to any of our components.
This comment has been minimized.
mgol repliedJan 3, 2014
@timmywil It is, to "Build". Every commit has to have an associated component according to the new policy.
This comment has been minimized.
timmywil repliedJan 3, 2014
It is related to Sizzle and Testing more than Build. Like I said, this is not a firm match for any component. And I don't think we need to be legalists here. Let's add component names where they helpfully provide scope for the commit.
This comment has been minimized.
markelog repliedJan 3, 2014
@timmywil i think it would better if we would document this kind of exception
This comment has been minimized.
scottgonzalez repliedJan 3, 2014
Everything Grunt related is definitely Build. You won't be able to make exceptions like this once we start programmatically checking commit message format, so you might as well get used to it now.
This comment has been minimized.
timmywil repliedJan 3, 2014
There is no "definite" about this. There is a reason why Grunt is now called a task manager rather than just a build tool. This seems like a case where strict adherence to guidelines has steered us away from what is suitable and helpful, but I concede that this is the exception rather than commonplace. That said, I'm all in favor of automating consistency enforcement. This is just the sacrifice that we make.
This comment has been minimized.
mgol repliedJan 3, 2014
Maybe it's just a question of renaming the "Build" component to sth more suitable.