-
Notifications
You must be signed in to change notification settings - Fork 184
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
Update the help text for the Pylint descriptor #933
Update the help text for the Pylint descriptor #933
Conversation
@uhafner could you please regenerate |
Codecov Report
@@ Coverage Diff @@
## master #933 +/- ##
=========================================
Coverage 92.89% 92.89%
Complexity 2322 2322
=========================================
Files 341 341
Lines 6450 6450
Branches 669 669
=========================================
Hits 5992 5992
Misses 262 262
Partials 196 196
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Can you please run mvn verify
then the file will be re-generated. Then you can commit it as well.
The `msg-template` setting only works in the pylintrc configuration file if it is under the `[REPORTS]` section header [0]. Otherwise the setting gets ignored: ``` $ cat ./pylintrc msg-template={path}:{module}:{line}: [{msg_id}({symbol}), {obj}] {msg} $ pylint --rcfile=./pylintrc test.py ************* Module pylintrc pylintrc:1:0: F0011: error while parsing the configuration: File contains no section headers. file: 'pylintrc', line: 1 'msg-template={path}:{module}:{line}: [{msg_id}({symbol}), {obj}] {msg}\n' (config-parse-error) [...] ``` Using the `--msg-template` CLI option is more convenient for the usage inside Jenkins pipelines. [0]: https://github.com/pylint-dev/pylint/blob/v2.17.4/examples/pylintrc#L481
ff224ad
to
666a98a
Compare
Ok, I just did that and amended the commit. I also replaced
|
Thanks! |
The
msg-template
setting only works in the pylintrc configuration file if it is under the[REPORTS]
section header 0. Otherwise the setting gets ignored:Using the
--msg-template
CLI option is more convenient for the usage inside Jenkins pipelines.Related Jira issue: https://issues.jenkins.io/browse/JENKINS-71665
TODO: SUPPORTED-FORMATS.md must be regenerated.
Testing done
Submitter checklist