Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
fatal: unsafe repository ('/github/workspace' is owned by someone else)
See original GitHub issueAt some moment it started to give this error
Push to branch ***************
fatal: unsafe repository ('/github/workspace' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /github/workspace
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:6
Top Results From Across the Web
git - Fatal error "unsafe repository ('/home/repon' is owned by ...
Here are four possible solutions: trust the Git directory (do it if you know the directory contents are safe)
Read more >`fatal: unsafe repository (REPO is owned by someone ... - GitHub
This issue seems only happens for workflows based on docker container, workflows directly running on runners is not affected. git config -- ...
Read more >Unsafe repository (REPO) is owned by someone else
Create a .gitconfig file in /var/www directory, which is the home for www-data user, with the following content : · Add the folder...
Read more >What to do when Git reports Fatal: Unsafe Repository
Earlier this month - April 2022 - Git released an update (2.35.2) to fix a security vulnerability. The problem was that on multi-user...
Read more >Git: Unsafe repository is owned by someone else (Windows)
Git : Unsafe repository is owned by someone else (Windows) · Open Windows “Explorer” and go to the repository where the error occurred...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jinek Please switch the used version of the GitHub push action to
ad-m/github-push-action@master. That should solve your issue, because the fix is already implemented there.Hi @jinek, I’ll prepare a PR to update the documentation and make it more transparent that a version change is necessary.