E

Pull request 401 Unauthorized error inquiry

Summary

The user submitted a pull request that failed a check due to a 401 Unauthorized error, inquiring if this is a known issue and if the check can be re-run. The response confirmed it is a known issue related to external contributors lacking access to GitHub secrets, and the team will review and trigger the build. The user also asked if the contribution will be included in version 0.8.16, to which the response was affirmative.

Status
resolved
Tags
    Source
    #earthly
      n

      nacho

      8/7/2024

      Yea

      e

      eliott.wiener

      8/7/2024

      Thanks! Will it be incorporated into 0.8.16?

      n

      nacho

      8/6/2024

      Merged Eliot thanks for the contribution

      n

      nacho

      8/5/2024

      Hi this is a known issue. Builds triggered from external contributors don’t have access to GH secrets. We’ll review it and trigger the build

      e

      eliott.wiener

      8/5/2024

      A PR I submitted ( https://github.com/earthly/earthly/pull/4267 ) had a check fail due to what seems like an unrelated error:

      Error: failed to SAVE IMAGE: failed to authorize: failed to fetch oauth token: unexpected status from GET request to <https://auth.docker.io/token?scope=repository%3Aearthly%2Fearthlybinaries%3Apull%2Cpush&amp;service=registry.docker.io>: 401 Unauthorized

      Is this a known issue with the CI checks? Can this be re-run?