Skip to content

Move CI to the shared Namespace runner - #54

Draft
leynos wants to merge 2 commits into
mainfrom
adopt-namespace-runners
Draft

leynos wants to merge 2 commits into
mainfrom
adopt-namespace-runners

Conversation

@leynos

@leynos leynos commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Summary

This branch moves repository-owned Linux jobs to the shared uncached
Namespace profile namespace-profile-default (Ubuntu 22.04, amd64, 4 vCPU,
16 GB) and records the custom runner labels for actionlint. Profile cache
volumes remain disabled. Native wheel matrices and externally controlled
reusable workflows retain caller-selected runners.

Review walkthrough

Validation

  • actionlint: passed
  • make check-fmt markdownlint: blocked because repository dependencies are not installed (node_modules/@biomejs/biome/bin/biome missing)

Notes

The shared profile is deliberately used without a repository-specific cache
volume during the pilot. The native wheel matrix remains GitHub-hosted because
it selects Windows, macOS, and architecture-specific runners at the reusable
workflow boundary.

Summary by Sourcery

Move repository-owned CI onto the shared uncached Namespace runner while documenting its contract and stabilizing related checks.

Bug Fixes:

  • Make startup-output snapshots resilient to Node.js warning lines and process-specific output.

Enhancements:

  • Move the repository-owned CI verification job to the shared uncached Namespace runner profile.
  • Document the shared CI runner contract and configure actionlint with the Namespace runner labels.
  • Refine spelling and documentation style checks for repository terminology and hexadecimal identifiers.

CI:

  • Add actionlint configuration for the shared Namespace runner labels.

Documentation:

  • Document the shared Namespace CI profile, its resource characteristics, disabled cache volume, and reusable-workflow runner behavior.

Tests:

  • Update startup-output snapshots and normalization to accommodate current Node.js output.

@coderabbitai

coderabbitai Bot commented Sep 1, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Warning

Your free Security trial is over. An organization admin can upgrade to Advanced for continuous pull request security review or dismiss this notice.


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

@sourcery-ai

sourcery-ai Bot commented Sep 1, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR migrates the repository-owned Linux verification job to the uncached shared Namespace profile, adds actionlint awareness of the custom runner labels, and documents the runner contract while leaving native wheel matrices and externally controlled reusable workflows on caller-selected runners.

File-Level Changes

Change Details Files
Move the repository-owned verification job to the shared uncached Namespace runner profile.
  • Replace the GitHub-hosted Ubuntu runner with namespace-profile-default.
  • Document the profile’s Ubuntu 22.04 amd64 environment, capacity, and disabled cache volume.
.github/workflows/ci.yml
docs/developers-guide.md
Declare shared Namespace runner labels for actionlint validation.
  • Add the default amd64 and arm64 Namespace profile labels to the actionlint configuration.
.github/actionlint.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Use the shared uncached Ubuntu profile for the repository-owned CI job and
document that externally controlled workflows retain caller-selected runners.
Keep startup snapshots independent of Node warning stream ordering and align
the Oxford spelling policy with existing commit and environment identifiers.
@leynos

leynos commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Where this branch's work went, so nothing is lost if it is eventually closed.

The Namespace migration is cancelled, so the runner change in c1a75be is not
being carried anywhere. The other commit is:

Commit Where it is now
e502ca6 "Stabilize documentation and startup gates" cherry-picked into #56 with your authorship preserved, and merged to main as part of f6565d3.

#56 also corrected three things in that commit, in a separate commit so the
difference stays visible in the history: ba had been added to [words] accepted, which stopped ba being corrected to be or by anywhere in the
repository, so the abbreviated commit hashes it answered are now matched by
their written form instead; the `color` example was restored to the style
guide and the term recorded in typos.local.toml; and the list marker on that
line, which had become +, failed markdownlint with MD032, which this
repository's CI does not run.

This pull request is deliberately left open. Closing it is yours to decide, not
an agent's.

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.

1 participant