-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add planemo lint error/warn level parameters #23
add planemo lint error/warn level parameters #23
Conversation
as introduced here galaxyproject/planemo-ci-action#23
5d17764
to
030c970
Compare
as introduced here galaxyproject/planemo-ci-action#23
030c970
to
028071e
Compare
and set stricter defaults
values are the defaults that will be introduced in galaxyproject/planemo-ci-action#23 but I think its a good idea to add them here anyway .. just in case anyone uses the repo as template. fail level warn will be more strict that before, but I guess this is a good idea
README.md
Outdated
Optional inputs: | ||
|
||
- `report_level`: all|warn|error (default: all) | ||
- `fail_level`: warn|error (default: warn) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the default should be error. If there are instances that are clearly bugs we should elevate them in the linter to error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My rationale was that warnings correspond to violations of best practices which we usually do not want. But we can also do this per repo (I would definitely suggest this for the IUC).
@mvdbeek this should be good to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, dropped the ball here. Looks good to me!
and set stricter defaults