"Could not find a matching team" error in pre-commit CI of some github PRs

[cor3ntin]

Some CI jobs, for example https://buildkite.com/llvm-project/github-pull-requests/builds/122 (triggered from #65193), do not get triggered properly be github PRs with a "Could not find a matching team that includes both pipelines each having a minimum "Build" access level" error

[llvmbot]

@llvm/issue-subscribers-infrastructure

[metaflow]

@cor3ntin I think that you've correctly identified the issue in discord: https://forum.buildkite.community/t/could-not-find-a-matching-team-that-includes-both-pipelines/1182/3

• /github-pull-requests pipeline only had team "libcxx"
• /clang-ci only had team "everyone"

so if user was not registered in buildkite then "team matching" rules would not allow build on clang ci from PR.
I have updated github PR pipeline so should be good. Please confirm!

[metaflow]

note to self: capture this behavior in doc for .ci

[cor3ntin]

@metaflow is there a good way to test? This PR seems to have been created after your change and still exhibit the bug
#65214

[metaflow]

sure, I will try to create a PR under another account tomorrow to see if it works.

…

On Sun, Sep 3, 2023, 11:20 cor3ntin ***@***.***> wrote: @metaflow <https://github.com/metaflow> is there a good way to test? This PR seems to have been created after your change and still exhibit the bug #65214 <#65214> — Reply to this email directly, view it on GitHub <#65207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB6EO62PLKEZEPEBDH2RL3XYRDVNANCNFSM6AAAAAA4IRN6UE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[metaflow]

Seems to be fixed now.