Add `lint` subcommand to CLI
Opened this issue · 0 comments
rtyler commented
Eventually I think this could spot anti-patterns like:
input
step inside of asteps {}
directive, rather than at a top-level of a stage- use of
script
steps - use of Groovy outside of the
pipeline
block - ???
Will need to find some "extensible" way to define these lints without having to add surgery in the parser for each new lint.