-
Notifications
You must be signed in to change notification settings - Fork 132
fatal: detected dubious ownership in repository at '/github/workspace' #138
Comments
Progressive mode does not work for you became you did not make a full checkout. |
I have tried using current example from the README, still the same error. I have tried |
Can I expect further help or maybe reopening the issue if necessary? |
@MarcinWieczorek Please post a link to a job failing. If original repo is not public, create a public one that contains the minimum code needed for reproducing the error. |
I have made my playground public. https://github.com/MarcinWieczorek/ansible-action |
Just to note I get the same error when using progressive on v6.10.2, even with fetch-depth 0. |
Some details on https://medium.com/@thecodinganalyst/git-detect-dubious-ownership-in-repository-e7f33037a8f -- I am working on a fix, even if the root cause is not originating from us, being likely a GHA container engine misconfiguration. |
I can confirm that this works. Thanks! I'm looking forward to use this action and maybe help improving the ansible-lint itself as proposed in this discussion: |
@MarcinWieczorek You are more than welcomed. This one took longer than expected to fix because it was a far edge-case. |
First of all thank you for creating the action, but I really need to use progressive mode. I have a legacy codebase with many errors. Linting only files changed in the commit would be even better than progressive mode, is it possible with this action?
Progressive mode doesn't seem to be working properly.
I don't have enough knowledge to establish if this is an issue with
ansible-lint
or your action.My config:
My workflow:
Action output:
The text was updated successfully, but these errors were encountered: