1 workspace package roles and scoped quality profiles
forgejo-actions edited this page 2026-07-11 12:38:13 +00:00

Workspace Package Roles And Scoped Quality Profiles

Workspace package roles let quality gates run targeted checks without losing track of which crates belong to editor, service, protocol, or shared validation workflows.

How It Works

Workspace metadata assigns roles such as editor_client, services, and protocol_config to package names. Quality gate profiles read that role inventory and choose cargo check targets, features, and command descriptions.

Scoped profiles speed feedback for focused changes while the full profile remains the broad regression guard.

How To Use It

Use standard or full before broad integration. Use scoped profiles like editor-client, services, or protocol-config when iterating in one ownership area. Update workspace package role metadata when adding, removing, or renaming workspace members.

Do not treat a scoped profile as proof that unrelated areas are safe.

Invariants

Role entries must reference real workspace members. Profiles should explain which packages they cover. Scoped checks should reduce turnaround time without skipping validation that belongs to the changed ownership area.

Debugging

If a role references a non-member, the role inventory should fail before a misleading cargo command runs. If a scoped profile misses a package, inspect workspace metadata and profile descriptors together.