-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helix testing on public PR coming from fork fails #4886
Comments
@smitpatel Yes, this is an authorization thing that everyone runs into -- you have to do on the build to make it accept forks (in AzDO). I don't remember what it is off the top of my head (been a while since I've seen it) but I'll track it down for you as soon as I can. |
Ah, I found it. Instructions here: https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#validate-contributions-from-forks |
Ensure that you don't check "make secrets available," however. |
Talked to Smit offline and this should be resolved; I was mistaken on checking "make secrets available." @smitpatel please close this after you've confirmed it's working! |
Verified working. |
Error message
Run: https://dev.azure.com/dnceng/public/_build/results?buildId=530301&view=logs&jobId=107b6447-6976-5e9d-0de1-92099cc60ad8&j=107b6447-6976-5e9d-0de1-92099cc60ad8&t=d41080c9-6b6f-523e-8424-6273a8737d4d
I am not sure what kind of authentication needs to be passed here.
The text was updated successfully, but these errors were encountered: