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
Leave an empty line between pod and code to all the files under lib #15139
Conversation
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files |
Why not to try to add the script that you used somewhere in the tools folder and call it from the Makefile? |
CI is the next step. thats why is still draft as not complete |
f19f22d
to
490fa36
Compare
0b35bd5
to
1901408
Compare
Following the recommendation all the perl POD documentation should have a empty line before the beginning of the code as a good practice. In this PR all the files which found under lib directory and its subdirectories are adding a new line from all the cases which matched `=cut\nsub` Signed-off-by: Ioannis Bonatakis <ybonatakis@suse.com>
As a convention the POD and the code needs to have an empty line in between. The script checks all the files rather the commit files in the lib directory. With this PR we enable validation of the rule in CI Signed-off-by: Ioannis Bonatakis <ybonatakis@suse.com>
Following the recommendation all the perl POD documentation should have a
empty line before the beginning of the code as a good practice. In this PR all
the files which found under lib directory and its subdirectories are adding a
new line from all the cases which matched
=cut\nsub
Signed-off-by: Ioannis Bonatakis ybonatakis@suse.com