caseworkctl explain omits reviewKinds, queues, and accessProfiles

Open
#1,245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli, tooling

Research direction

Start by locating the implementations and tests for the caseworkctl explain and caseworkctl check commands. Trace how the effective configuration is serialized for source-backed projects, then verify that reviewKinds, ordered stages and outcomes, queues, accessProfiles, and review producers appear in the requested outputs with their ordering preserved.

Written by the indexing model from the issue text.

Description

area:casework enhancement rust

Problem

caseworkctl explain does not report three parts of casework.yaml that shape what actually happens to a request:

  • reviewKinds and their ordered stages (queue, deciding profiles, required approvals, initiator and previous-stage exclusions) and outcomes (settlement, reason required, result required)
  • queues with their labels
  • accessProfiles

caseworkctl check has the same gap on the effective block: for source-backed projects it does not include reviewKinds, nor the review producers that back them.

The result is that the review model, which is the centre of the product since approval ownership moved into Casework, is the part of the configuration the tooling explains least.

Request

  1. Include reviewKinds (stages and outcomes, in order), queues, and accessProfiles in caseworkctl explain --format json.
  2. Include reviewKinds and their producers in the caseworkctl check effective block for source-backed projects.

Ordering matters and should be preserved: stage order is semantic.

Why it matters

A reader asking "who can decide this, and how many approvals does it take" cannot get that answer out of the tooling today without reading the YAML by hand.

Dominant language
Rust
Stars
2
Forks
0
Avg merge
3h 45m
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

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.

More from registrystack/registry-stack

All issues in registrystack/registry-stack

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.