Skip to content

docs(claude): correct runner-label note (runners are repo-scoped) - #108

Merged
owine merged 1 commit into
mainfrom
docs/new-host-label-wording
Oct 10, 2026
Merged

owine merged 1 commit into
mainfrom
docs/new-host-label-wording

Conversation

@owine

@owine owine commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

Sourcery review of #107: these runners are registered per repo (see the troubleshooting section's repos/<caller>/actions/runners), so a reused label can't send deploys to another repo's host; the job would just queue. Fixes the note I added in #107.

Summary by Sourcery

Correct the runner-label guidance for adding self-hosted hosts.

Bug Fixes:

  • Correct the self-hosted runner guidance to clarify that runners are repository-scoped and reused labels cannot route deployments to another repository's host.

Documentation:

  • Update the host setup documentation with accurate runner registration and queuing behavior.

@sourcery-ai

sourcery-ai Bot commented Oct 10, 2026 •

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

Reviewer's Guide

Updates the new-host runbook highlights to accurately explain that self-hosted runners are registered per repository, so labels are not globally shared across repositories and reused labels cannot redirect deployments.

File-Level Changes

Change Details Files
Correct the self-hosted runner labeling guidance to reflect repository-scoped runner registration.
  • Remove the claim that reusing a label routes deployments to another repository’s host.
  • Explain that each repository requires its own runner regardless of label, and a label mismatch across repositories causes jobs to queue rather than route elsewhere.
CLAUDE.md

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

@sourcery-ai sourcery-ai 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.

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@owine
owine merged commit b03af5f into main Oct 10, 2026
3 checks passed
@owine
owine deleted the docs/new-host-label-wording branch October 10, 2026 13:37
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