redhat-developer / redhat-developer/rhdh-fullsend

Monorepo workspace routing improvements

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
2
Forks
7
Avg merge
1d 13h
Merged PRs (30d)
8

Description

Three open gaps in workspace-level agent routing for monorepo targets (rhdh-plugins, rhdh-agentic).

1. Routing skill: label priority

The workspace routing skill guesses the target workspace from issue title/body instead of trusting an existing workspace/* label. When a label is already set, the skill should prioritize it over heuristic detection.

2. Routing skill not in triage harness

Triage has no workspace awareness — it can misroute issues to the wrong workspace. Adding the routing skill to the triage harness would fix this.

3. workspace/* labels not automated

Labels must be manually created when adding new workspaces. Could be automated via a GitHub Action or post-workspace-creation script.


Related: #28 (rhdh-plugins gaps), the rhdh-workspace skill
Migrated from docs/known-issues.md

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the rhdh-workspace skill and the triage harness to trace how workspace labels and heuristic routing are handled. Then inspect the workspace-creation automation options mentioned in the issue, including a GitHub Action or post-workspace-creation script. Done means existing workspace/* labels take priority, triage uses workspace routing, and labels are created automatically for new workspaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.