-
Notifications
You must be signed in to change notification settings - Fork 59
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
Broken due to Detected Dubious Ownership #21
Comments
I also started getting this error a few days ago. There's an issue with the entrypoint.sh script as well according to these errors, not sure if it's related.
|
Guys it is easy to solve, you can contribute to this by adding |
@SvanBoxel @grogou I'm sorry guys but this didn't work for me. We could do sth like: what do you think? My output:
|
@klinkeklinke and @SvanBoxel did you tested new feature before merging? I can confirm it is not working. Try to find solution and test it before merge. |
@grogou if you want to, could you submit a PR with a solution that works for you? For what I tested it works but could be your environment is different. Thanks. |
I will try if there will be time, I am here just to help. |
I cant understand different environment, I guess it is the same GitHub Actions with your package. |
TL;DR - #23 fixes the issue II didn't think it would work this way - but I managed to test my code this time just by using my fork as github action in my workflow: I ran several tests - first pushing changes manually and then with a PR on my repository and all worked fine, no dubious ownership problems. The problem was I had to do it before any git command - before the first git checkout in entrypoint.sh. Sorry for not succeeding in testing before (in #22 ). Hopefully this helps everyone. |
Available as pre-release https://github.com/SvanBoxel/gitlab-mirror-and-ci-action/releases/tag/0.5 |
Resolved for me! |
Updated to latest release. Thanks all! |
The action seems to have started to fail sometime in the last 3 days with the following error message:
Unhelpfully, it doesn't show up as a failure in GitHub Actions (likely due to #16 and #10), so the only way I found out it had stopped working was by not seeing any recent commits on my GitLab mirrors.
The text was updated successfully, but these errors were encountered: