Kurt von Laven

Ah, that is a good point, @echoix. In that specific case, I suggest WSL (Windows Subsystem for Linux), but in general I don't see why it wouldn't be possible to...

I haven't considered build-time, but at least for using Mega-Linter, I already run it without root on Linux both locally and in CI. Do we run rootful Docker in order...

Good point; starting to think there are two separate issues here. I suspect that building without the root user only impacts those of us who build locally as opposed to...

@nvuillam, I wonder if this would help with the CI failures you mentioned if `git config --global --add safe.directory "$GITHUB_WORKSPACE"` alone is not sufficient? I can give it a try...

I will finally have some time to look at this in a few days. Happy to take it over if we can afford to wait.

For some reason the bot didn’t honor the nostale label, so I removed the stale label manually.

I suggest inspecting the values of the many variables in the condition to narrow down why the entire expression evaluates to `false`, causing the step to be skipped.

Sorry, but I cannot follow the logic without parentheses. You can use [triple back ticks to format a fenced code block in GFM](https://github.github.com/gfm/#fenced-code-blocks).

[Many projects actively use the GitHub Action](https://github.com/megalinter/megalinter/network/dependents?package_id=UGFja2FnZS0yOTQyNTYxNDY1), but I think you're probably right about the cleanup step missing `if: always()`, and I certainly don't claim there are no bugs. Please...

It's all good. Your assumption that [`if: success()` is the default](https://docs.github.com/en/actions/learn-github-actions/expressions#status-check-functions) is correct. [`always()`](https://docs.github.com/en/actions/learn-github-actions/expressions#always) is equivalent to `success() || failure() || cancelled()`. In case anyone following along is confused, none...