Skip to content

chore: sync the org labels to krini - #76

Merged
uniqueg merged 1 commit into
mainfrom
chore/75-labels-krini
Nov 14, 2026
Merged

uniqueg merged 1 commit into
mainfrom
chore/75-labels-krini

Conversation

@uniqueg

@uniqueg uniqueg commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Summary

Adds krini to repositories in labels/labels.yml, in alphabetical order, so that labels/sync.sh covers it by default. krini had neither status: triage nor type: dependencies, which its dependabot.yml sets. The labels were synced to krini by hand already; this keeps them in sync from now on.

Left for a maintainer in the UI (the script never deletes): relabel krini issues from status: new to status: triage, and delete status: new, do not merge and migration in progress there.

Light lane: configuration only (one list entry); I reviewed the diff myself.

Closes #75

Verification

  • bash tests/labels/test.sh: ok for labels.yml, --check, sync, repositories, unlisted and errors.
  • CI: all checks passed.

Declined review findings

None (light lane).

Open questions

None.

🤖 Generated with Claude Code

Summary by Sourcery

Enhancements:

  • Include the krini repository in the default label synchronization configuration.

Add krini to the repositories that labels/sync.sh covers by default,
so that it gets the org label set (status: triage, type: dependencies
for its Dependabot configuration, the current descriptions).

Closes #75

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@uniqueg uniqueg self-assigned this Nov 14, 2026
@sourcery-ai

sourcery-ai Bot commented Nov 14, 2026

Copy link
Copy Markdown

Reviewer's Guide

Configuration

Add krini to the default repository list so the label sync covers it.

  • labels/labels.yml L18

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

@uniqueg
uniqueg marked this pull request as ready for review November 14, 2026 19:14
@sourcery-ai

sourcery-ai Bot commented Nov 14, 2026

Copy link
Copy Markdown

Linked issues

Checked at commit 2df3925

#75 chore: sync the org labels to krini · 1 of 5 met · 4 to check by hand

# Requirement Status Notes
1 Add krini to repositories in labels/labels.yml. ✅ Met The diff adds krini to the repository list.
2 After the merge, run labels/sync.sh for krini or the default set. 👀 Check by hand (manual process) A maintainer must confirm the post-merge sync was run; the PR says the labels were synced by hand already.
3 Relabel krini issues from status: new to status: triage. 👀 Check by hand (external system) A maintainer must check the krini issue labels in the UI and make this change if it is still needed.
4 Delete status: new, do not merge and migration in progress from krini. 👀 Check by hand (external system) A maintainer must check the krini labels in the UI and delete these labels if they are still present.
5 After the sync, krini has every label of labels and temporary with the colours and descriptions in the file. 👀 Check by hand (external system) A maintainer must verify the resulting krini labels, colours and descriptions in the UI.

@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

Needs a human reviewer. Adding krini to the sync list may create or update organization labels in that repository. Reverting removes it from future syncs, but labels already applied can remain until they are cleaned up; that is bounded and repairable.


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

@uniqueg
uniqueg merged commit ab3b1ff into main Nov 14, 2026
7 checks passed
@uniqueg
uniqueg deleted the chore/75-labels-krini branch November 14, 2026 19:34
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.

chore: sync the org labels to krini

1 participant