Skip to content

Adopt shared Namespace Linux runners - #466

Draft
leynos wants to merge 1 commit into
mainfrom
adopt-namespace-runners
Draft

Adopt shared Namespace Linux runners#466
leynos wants to merge 1 commit into
mainfrom
adopt-namespace-runners

Conversation

@leynos

@leynos leynos commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Summary

  • move compatible audit and delayed-comment jobs to the shared uncached Namespace Linux runner
  • document the retained 8-vCPU build and coverage exception
  • add actionlint configuration and workflow runner contracts

Validation

  • make test-workflow-contracts
  • make check-fmt
  • make markdownlint
  • make typecheck
  • make lint
  • actionlint -ignore shellcheck -config-file .github/actionlint.yaml .github/workflows/*.yml

Summary by Sourcery

Adopt shared Namespace runners for compatible utility workflows while preserving capacity for build and coverage jobs.

Enhancements:

  • Move the audit and delayed pull-request comment jobs to the shared uncached Namespace Linux runner while retaining the existing 8-vCPU runner for capacity-sensitive build and coverage jobs.
  • Add workflow runner contracts to prevent approved runner assignments from drifting.

CI:

  • Configure actionlint to recognize the shared Namespace runner label.

Documentation:

  • Document GitHub Actions runner profiles, cache behavior, and the retained build and coverage runner exception.

Tests:

  • Add contract tests covering shared Namespace assignments and capacity-sensitive runner retention.

Move the compatible audit and pull-request utility jobs to the shared,
uncached Ubuntu 22.04 Namespace runner. Document the retained eight-core
workload exception and add workflow contracts to prevent runner drift.
@coderabbitai

coderabbitai Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

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

The PR adopts the shared uncached namespace-profile-default runner for the audit and delayed-comment workflows, keeps build and coverage workloads on ubicloud-standard-8 because of their capacity requirements, documents these runner contracts, and adds actionlint/test coverage to prevent assignment drift.

File-Level Changes

Change Details Files
Migrated low-risk utility workflows to the shared uncached Namespace Linux runner while preserving capacity-sensitive jobs on the existing 8-vCPU runner.
  • Changed audit and delayed PR comment jobs to use namespace-profile-default.
  • Documented the shared profile’s Ubuntu, architecture, resource, and cache characteristics.
  • Recorded the retained ubicloud-standard-8 exception for build and coverage workflows.
.github/workflows/audit.yml
.github/workflows/delayed-pr-comment.yml
docs/developers-guide.md
Added runner labels and executable workflow contracts to validate the intended runner assignments.
  • Registered namespace-profile-default in actionlint’s self-hosted runner labels.
  • Added contract tests for shared-profile utility jobs and 8-core build/coverage jobs.
.github/actionlint.yaml
tests/workflow_contracts/namespace_runners_test.py

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

codescene-access[bot]

This comment was marked as outdated.

@codescene-access codescene-access Bot 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.

No quality gates enabled for this code.

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