You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The section starting with "Adding pre-commit plugins to your project" is pretty unclear.
Maybe it could be worded differently and show usage of more/most of the "keywords"?
s/The pre-commit config file describes:/The following directives/options control which hooks are applied to your project and how they behave:/
Also, the table should clarify at what level in the file the different words are relevant - for example "sha" applies one level higher than "id" - you could either split the table into two groups, one for the top level (per repo) and one for the lower level (per hook). I reckon a BNF for the config file format is overkill, but the current setup is not clear enough.
Activity
philipmulcahy commentedon May 9, 2016
The section starting with "Adding pre-commit plugins to your project" is pretty unclear.
Maybe it could be worded differently and show usage of more/most of the "keywords"?
s/The pre-commit config file describes:/The following directives/options control which hooks are applied to your project and how they behave:/
Also, the table should clarify at what level in the file the different words are relevant - for example "sha" applies one level higher than "id" - you could either split the table into two groups, one for the top level (per repo) and one for the lower level (per hook). I reckon a BNF for the config file format is overkill, but the current setup is not clear enough.
asottile commentedon Oct 4, 2017
@philipmulcahy (yes, I'm very late to the party) separating out
repo/shajust happened in #138 so now it's a little more obvious (I hope!)