-
-
Notifications
You must be signed in to change notification settings - Fork 859
feat: lint the whole project using Super-Linter #544
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
base: main
Are you sure you want to change the base?
Conversation
46f138a
to
17c075f
Compare
17c075f
to
034b4ff
Compare
034b4ff
to
69fd710
Compare
a14cce1
to
f48c792
Compare
f48c792
to
92c8ef0
Compare
Co-authored-by: Stanislau Kviatkouski <[email protected]>
Does it make sense to keep only one of the code block lang ( |
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.
Keep empty column for non-changed lines in diff
and patch
code blocks
Co-authored-by: Stanislau Kviatkouski <[email protected]>
@7-zete-7 yes indeed, consistency is always better |
According to https://stackoverflow.com/a/68222754, |
This comment was marked as off-topic.
This comment was marked as off-topic.
Could you open another PR please? |
Yep, I'll open separated. Sorry for the annoying suggestions. |
Super-Linter is a must-have; it automatically lints all files in the project, using popular linters.
It is especially useful to lint all the non-PHP files contained in a modern project:
Dockerfile
, YAML, Kubernetes manifests, GitHub Actions...