Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Change-request explanation describes review stages and apply-on-submit that BReg does not have

Open Beginner friendly
#1,989 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, rust
Domain
documentation

Research direction

Read the “Change requests” paragraph in docs/site/src/content/docs/explanation/configuration-defined-registry.mdx and compare it with products/breg/CHANGE_REQUEST_EXAMPLES.md. Update the paragraph to describe review by Casework or no review, manual or automatic application after approval, and Evidence preconditions checked at apply. Run npm test and npm run check in docs/site; done when both pass and the paragraph matches the contract.

Written by the indexing model from the issue text.

Description

agent-ready area:breg area:docs criticality:p3 documentation triage:needs-implementation

Problem

docs/site/src/content/docs/explanation/configuration-defined-registry.mdx
(the "Change requests" paragraph) says reviewers approve or reject a change
request "stage by stage" and that a request type may "apply on submit or final
approval when the acting profile holds apply authority".

Neither exists. BReg hands review to Casework under one policy per request type
(review: {type: required, authority: casework, policyId} or
{type: none}), and applies either manually or automatically after approval
(onApproved.mode). products/breg/CHANGE_REQUEST_EXAMPLES.md says "BReg does
not host review stages", and
crates/registry-breg/src/change_request.rs
(obsolete_stages_and_application_modes_are_not_authoring_inputs) refuses the
old keys.

Fix

Rewrite the paragraph from products/breg/CHANGE_REQUEST_EXAMPLES.md: review
by Casework or none, manual or automatic apply after approval, Evidence
preconditions checked at apply.

Done when

The paragraph matches the change-request contract, and npm test and
npm run check pass in docs/site.

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

Getting set up

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.