• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

IBM / unitxt / 37210332000
78%

Build:
DEFAULT BRANCH: main
Ran 04 Oct 2026 02:48PM UTC
Jobs 1
Files 64
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

04 Oct 2026 02:43PM UTC coverage: 78.319%. Remained the same
37210332000

push

github

web-flow
CI: Don't fail fork and Dependabot runs on unavailable secrets (#1989)

GitHub withholds repository secrets from workflow runs triggered by forks
and by Dependabot. Two steps treated those secrets as mandatory and failed
hard when they resolved to an empty string, which is why PR #1986 showed 11
red jobs that never executed a single test.

The internal-dependency step wrote secrets.LLMEVALKIT_SSH_KEY to
~/.ssh/id_ed25519 and pip-installed from git+ssh://github.ibm.com. With an
empty key this aborts the whole job:

    Load key "/home/runner/.ssh/id_ed25519": error in libcrypto
    git@github.ibm.com: Permission denied (publickey).

That killed unittests, eager, and all ten preparation shards before the test
step. The host is IBM-internal, so it is unreachable from an external fork
regardless of the secret. Skip the install when no key is present. The
llmevalkit imports in metrics.py are already lazy and guarded by
_requirements_list, so the affected metrics raise a clear "install with..."
message if something actually instantiates them; everything else is
unaffected.

The Hugging Face login step interpolated an empty token into
`huggingface-cli login --token`, looped five times, and left the run
unauthenticated, which then hit the shared-runner rate limit:

    urllib.error.HTTPError: HTTP Error 429: Too Many Requests

Skip the login when no token is present and say so in the log, instead of
retrying a call that cannot succeed. Unauthenticated runs remain exposed to
Hub rate limits; this reports the cause rather than fixing it.

Both guards are no-ops on trusted runs. Prefer a guard inside the step over
continue-on-error at the call sites, so a real install failure still fails
the job when the secret IS available.

Also pass both secrets through env: rather than interpolating them into the
script body, and write the key with printf instead of echo, which mangles
values containing backslashes or a leading dash.

Signed-off-by: Yoav Katz <katz@il.ibm.co... (continued)

2785 of 4018 branches covered (69.31%)

Branch coverage included in aggregate %.

10974 of 13550 relevant lines covered (80.99%)

0.81 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37210332000.1 04 Oct 2026 02:48PM UTC 64
78.32
GitHub Action Run
Source Files on build 37210332000
  • Tree
  • List 64
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #37210332000
  • ce5e3ac1 on github
  • Prev Build on main (#37196919318)
  • Next Build on main (#37277233664)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc