-
Notifications
You must be signed in to change notification settings - Fork 9
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
fatal: detected dubious ownership in repository at '/github/workspace' #27
Comments
Hello, Thanks for reporting this issue.
The problem is that pana runs Git in a way that prevents any custom config to be used, this is why your workaround didn't work. I fixed the issue by assigning the ownership of the Git directory to the user set in the container. Btw, this issue failed my automated tests recently so it shouldn't have made its way to you, but I thought it was a bug in my tests and I changed the tests instead of the code... I'll be more careful next time. |
Thanks @axel-op :) no worries about the small break |
@axel-op It works now, thanks for your work. |
Should fix an issue with error "detected dubious ownership in repository" See axel-op/dart-package-analyzer#27
it's still failing for us, anything we're doing wrong? getsentry/sentry-dart#1918 |
@buenaflor Thanks for notifying it. Here's what I did:
Can you please retry the workflow? |
Still failing unfortunately :( |
I think I found the root cause and definitely fixed the issue. Your package is located in a subdirectory. My initial fix acquires the ownership of this subdirectory only but not of the root repository. The problem is that Git commands are run from the root. I implemented a fix and added a new test to prevent any regression. Tell me if this solves your issue :) |
works now, thx! |
I run into an issue when using the
axel-op/dart-package-analyzer@v3
recently, the error loghere's the failed job
https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/actions/runs/8075870137/job/22154729575?pr=1585
After some search, actions/runner-images#6775, I tried to add this as a workaround in my step, but it's no luck.
I'm not very sure if it should be added inside the
Dockerfile
, I think it can easily reproduce this issue with the following workflow configThe text was updated successfully, but these errors were encountered: