chore(workflow): guess PR reviewers instead of a hardcoded list - #4848
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryDoc-only change to Files Reviewed (1 files)
Reviewed by claude-sonnet-5 · Input: 14 · Output: 2.4K · Cached: 241.2K Review guidance: REVIEW.md from base branch |
jeanduplessis
approved these changes
Jul 29, 2026
…t-20260729123034 # Conflicts: # .kilo_workflow/WORKFLOW.md
iscekic
enabled auto-merge (squash)
July 29, 2026 10:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The orchestrator no longer requests reviews from a fixed list of people (
eshurakov,jeanduplessis,marius-kilocode,chrarnoldus). It now works out who fits each PR and requests the top one or two. Assignee is unchanged — still the requesting human.Why
The hardcoded list goes stale, ignores who actually owns the touched code, and spams the same four people on every PR regardless of area.
How
New
Picking Reviewerssubsection in.kilo_workflow/WORKFLOW.md(section 3) with the exact commands: who reviewed recent PRs for the changed files, and who usually reviews the requesting human's PRs. Count names across both, drop bots and the assignee, request the top one or two. Empty history → request nobody and note it in the PR description.Doc-only change; no runtime behavior to verify.