ci: clang-tidy: no repo ref

[hmaciak]

This PR provides fix for fork repositories check.

[hmaciak]

test: https://github.com/uxlfoundation/oneDNN/actions/runs/13965752650/job/39095639717

[vpirogov]

I don't understand what this change does exactly. Please explain.

The issue we have after PR #2911 got promoted is that clang-tidy runs on files from the main branch (either fork or main repo), instead of the PR branch.

[atkassen]

I don't understand what this change does exactly. Please explain.

The issue we have after PR #2911 got promoted is that clang-tidy runs on files from the main branch (either fork or main repo), instead of the PR branch.

Looks like it is now running against a merge commit of the two branches that GitHub creates for the PR in the base repo.

In the log for #2924:

/usr/bin/git -c protocol.version=2 fetch --prune --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/* +8f65a5f3d4cd70134dc97eea365c75bc6b2cce39:refs/remotes/pull/2924/merge
...
/usr/bin/git checkout --progress --force refs/remotes/pull/2924/merge

[vpirogov]

Looks like it is now running against a merge commit of the two branches that GitHub creates for the PR in the base repo.

This sounds reasonable, as it would reflect the state after the PR is merged.

Shall we test whether it works like that for forks as well?

[hmaciak]

This test is for fork. This #2911 worked fine for branches and it uses PR merge branch (example: https://github.com/uxlfoundation/oneDNN/actions/runs/13972297648/job/39116992717). The only issue is for forks, and deleting repo ref fixes the issue and allows default checkout to merge commit.

[atkassen]

Shall we test whether it works like that for forks as well?

I just meant that the merge exists as part of the base repo. The merge commit is made from the base branch and the head branch (be it in a fork or not). @hmaciak's test was with the branch from my fork and everything looked good.

[vpirogov]

Thanks for the explanation, @hmaciak and @atkassen!