You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if test `git grep -z -l 'Copyright.*The Khronos' | xargs -0 git grep -L 'Copyright.*2025.*The Khronos' | wc -l` != 0 ; then \
echo "Files with out-of-date Khronos copyrights (must be updated to 2025:" ; \
git grep -z -l 'Copyright.*The Khronos' | xargs -0 git grep -L 'Copyright.*2025.*The Khronos' ; \
exit 1 ; \
fi
fatal: detected dubious ownership in repository at '/__w/Vulkan-Docs/Vulkan-Docs'
To add an exception for this directory, call:
Result was that CI was not run for this stage, but did not fail.
We ran into this at one point a while back and the problem had to do with the odd '/__w' path that github Actions checkout the repository under. IIRC the solution then was to check out the repo under a different path, but that may not be viable here because this logic is not part of the CI script but more fundamental to Actions.
The text was updated successfully, but these errors were encountered:
FWIW, I think this is a git problem. I believe it can be solved either by ensuring the directory (if it already exists) is owned by the user of git, or a simpler solution is to disable the safe-directory check from git's config:
git config --global --add safe.directory '*'
If you want to be more targeted rather than disabling safe.directory everywhere, you can sub the wildcard for the problem path, or can add it to the user's gitconfig ~/.gitconfig.
or ensure the ownership of the folder is correct:
chown -R $(id -u):$(id -g) $PWD
This is a bug that pops up from time to time in github actions runner.
The 'user' is setup by Actions as part of cloning the repository and nothing about that is configurable AFAIK. Perhaps we could do the git config setting immediately after cloning it and before any CI stages run, though.
Related and now that I remember it, there was also an issue with image directives with the '__w' in their full path, which asciidoctor expanded as italics and failed to load.
On Sun, Jan 26, 2025, 3:14 AM Jon Leech ***@***.***> wrote:
The 'user' is setup by Actions as part of cloning the repository and
nothing about that is configurable AFAIK. Perhaps we could do the git
config setting immediately after cloning it and before any CI stages run,
though.
Related and now that I remember it, there was also an issue with image
directives with the '__w' in their full path, which asciidoctor expanded as
italics and failed to load.
—
Reply to this email directly, view it on GitHub
<#2482 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5IAY6KUFWLTFAPVHCIWL32MS7S3AVCNFSM6AAAAABVZSLE5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJUGMZTAMJTG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
Per https://github.com/KhronosGroup/Vulkan-Docs/actions/runs/12914759298/job/36015056855 :
Result was that CI was not run for this stage, but did not fail.
We ran into this at one point a while back and the problem had to do with the odd '/__w' path that github Actions checkout the repository under. IIRC the solution then was to check out the repo under a different path, but that may not be viable here because this logic is not part of the CI script but more fundamental to Actions.
The text was updated successfully, but these errors were encountered: