5
0
Fork 0
mirror of https://github.com/actions/checkout.git synced 2025-11-11 07:26:55 +00:00

Compare commits

...

2 commits

Author SHA1 Message Date
Phil Coval
a7b7d87eb1
Merge 0989b3cff1 into ff7abcd0c3 2025-08-18 14:04:15 +02:00
Philippe Coval
0989b3cff1 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>
2025-05-28 14:44:05 +02:00

View file

@ -349,6 +349,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 *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 # 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: 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: