Skip to content
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

Is option -p in mega-linter-runner working properly? #3552

Closed
vkucera opened this issue May 10, 2024 · 2 comments
Closed

Is option -p in mega-linter-runner working properly? #3552

vkucera opened this issue May 10, 2024 · 2 comments
Labels
O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity question Further information is requested

Comments

@vkucera
Copy link
Contributor

vkucera commented May 10, 2024

The documentation of mega-linter-runner says that the -p option specifies "Directory containing the files to lint".

The way I understand it is that if I run npx mega-linter-runner -p <path> in the root directory of my repository, it will lint files in <path> with the configuration taken from .mega-linter.yml in the root directory.

However, it seems that what it does instead is to enter <path> and run the runner from there, as if <path> was the current directory, resulting in running with default settings.

@vkucera vkucera added the question Further information is requested label May 10, 2024
@nvuillam
Copy link
Member

nvuillam commented May 12, 2024

Would you mind sharing logs (after removing proprietary data if necessary) ?

Path is indeed used to map your local folder to lint with /tmp/lint in the container in the docker run instruction

image

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

@github-actions github-actions bot added the O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity label Jun 12, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants