Skip to content

ci: run Linux jobs on Namespace runners (namespace-profile-vig) - #16

Merged
DevVig merged 1 commit into
mainfrom
ci/namespace-runners
Oct 29, 2026
Merged

DevVig merged 1 commit into
mainfrom
ci/namespace-runners

Conversation

@DevVig

@DevVig DevVig commented Oct 29, 2026

Copy link
Copy Markdown
Owner

Summary

Move the Linux CI job onto Namespace runners.

  • File: .github/workflows/ci.yml
  • Job: build (Typecheck & test)
  • Change: runs-on: ubuntu-latest → runs-on: namespace-profile-vig

Jobs will queue until the Namespace app is installed on DevVig and the vig profile exists in Namespace.

Type of change

  • Refactor / internal

Checklist

  • bun run typecheck passes
  • bun run test passes
  • Context-routing changes include a case in tests/unit-context-window.mjs
  • For model-mapping changes, I noted how the served context window was verified

Notes

CI YAML only. No application code changes.

Open in Web Open in Cursor 

Replace ubuntu-latest with namespace-profile-vig for the CI build job.

Co-authored-by: Jonathan Borgwing <DevVig@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings October 29, 2026 00:46
@coderabbitai

coderabbitai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 102 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Learn how review limits work.

Review configuration:

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: d6e64f2a-f450-4b33-a908-b4cf8a44465a
Commits

Reviewing files that changed from the base of the PR and between fd403e4 and 6fa8549.

Files selected for processing: 1
  • .github/workflows/ci.yml
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Switching CI runners to namespace-profile-vig could queue or block all CI unless the required Namespace app and vig profile already exist, so human confirmation that the infrastructure is ready is needed before merge.

No open issues 🎉

What changed in this PR

This PR migrates the Linux CI job from GitHub-hosted runners to self-hosted Namespace runners by changing a single runner label in the workflow. The goal is to run the build (Typecheck & test) job on the vig Namespace profile instead of ubuntu-latest. It is a CI configuration-only change with no application code impact.

Changes:

  • Swap runs-on: ubuntu-latest → runs-on: namespace-profile-vig for the build job in .github/workflows/ci.yml.
File Description
.github/​workflows/​ci.yml Points the Typecheck & test job at the namespace-profile-vig self-hosted runner label instead of ubuntu-latest.

No objective code defects were found in the diff. The change is a straightforward, self-consistent runner label swap, and ci.yml is the only workflow file in the repository, so there are no sibling workflows left on the old label.

One operational note worth human confirmation before merge (already acknowledged in the PR description): until the Namespace app is installed on DevVig and the vig profile exists, the build job will queue indefinitely, which would block CI status checks on all PRs targeting main.

Review effort: Balanced

@DevVig
DevVig merged commit 9087897 into main Oct 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants