From 0989b3cff107c152e63aaa55afcf28cbf15887f2 Mon Sep 17 00:00:00 2001
From: Philippe Coval <rzr@users.sf.net>
Date: Tue, 1 Apr 2025 19:56:00 +0200
Subject: [PATCH] doc: Add workaround for ownership on self-hosted runners
Check is done in extra step
Origin: https://github.com/actions/checkout/pull/2124
Relate-to: https://github.com/actions/checkout/issues/1048#issuecomment-2768908874
Co-authored-by: tonyd-stoat <anton.d@gowombat.team>
Signed-off-by: Philippe Coval <rzr@users.sf.net>
---
README.md | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/README.md b/README.md
index 64dc025..759157c 100644
--- a/README.md
+++ b/README.md
@@ -314,6 +314,22 @@ jobs:
*NOTE:* The user email is `{user.id}+{user.login}@users.noreply.github.com`. See users API: https://api.github.com/users/github-actions%5Bbot%5D
+## Post checkout permission check
+
+```yaml
+on: push
+jobs:
+ build:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - run: >-
+ git status
+ || git config --system --add safe.directory "$GITHUB_WORKSPACE"
+```
+
+This check prevent/workaround "fatal: detected dubious ownership in repository" error on self hosted runners.
+
# Recommended permissions
When using the `checkout` action in your GitHub Actions workflow, it is recommended to set the following `GITHUB_TOKEN` permissions to ensure proper functionality, unless alternative auth is provided via the `token` or `ssh-key` inputs: