Skip to content
This repository was archived by the owner on Jun 10, 2026. It is now read-only.

ci: add Nebius selftest workflow - #20

Closed
opencolin wants to merge 1 commit into
KiranChilledOut:mainfrom
opencolin:add-ci-workflow
Closed

ci: add Nebius selftest workflow#20
opencolin wants to merge 1 commit into
KiranChilledOut:mainfrom
opencolin:add-ci-workflow

Conversation

@opencolin

Copy link
Copy Markdown

Runs python start_proxy.py --selftest (which performs a real round
trip to Nebius Token Factory) on:

  • push to main: so the main branch is always known-functional
  • workflow_dispatch: so a maintainer can re-verify on demand

We deliberately don't run on pull_request: PRs from forks don't
receive secrets, so a real-API selftest there would always fail
with a useless "secret not set" error. The existing Test Matrix
workflow already covers PRs with pytest (no API needed).

Required: NEBIUS_API_KEY repository secret. Fails loudly with a
GitHub annotation if the secret is missing rather than silently
skipping. Uses moonshotai/Kimi-K2.5 (live as of writing) to avoid
the model-not-found failure mode that retired model IDs cause.

Depends on: --selftest flag (PR #13) being merged first.

Runs python start_proxy.py --selftest (which performs a real round
trip to Nebius Token Factory) on:

  - push to main: so the main branch is always known-functional
  - workflow_dispatch: so a maintainer can re-verify on demand

We deliberately don't run on pull_request: PRs from forks don't
receive secrets, so a real-API selftest there would always fail
with a useless "secret not set" error. The existing Test Matrix
workflow already covers PRs with pytest (no API needed).

Required: NEBIUS_API_KEY repository secret. Fails loudly with a
GitHub annotation if the secret is missing rather than silently
skipping. Uses moonshotai/Kimi-K2.5 (live as of writing) to avoid
the model-not-found failure mode that retired model IDs cause.

Depends on: --selftest flag (PR #4) being merged first.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@KiranChilledOut

Copy link
Copy Markdown
Owner

Would do this if we are using custom runners, Internal Repo, for now would not risk any Nebius keys on open source project directly. Specially if we add other maintainers then we strictly need to adhere to Zero Trust Arch

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants