Repository navigation
docs: align dot-project docs with managed team flag convention - #673
Merged
riaankleinhans merged 1 commit intoSep 10, 2026
Merged
riaankleinhans merged 1 commit into
riaankleinhans merged 1 commit into
Conversation
README.md, example/maintainers.yaml, and AGENT.md still referenced the old hard-required 'project-maintainers' team name and rule, which was superseded by PR cncf#602 (managed flag for flexible resource provisioning). SCHEMA.md and template/maintainers.yaml were updated by that PR but these three files were missed. - README.md: update sample maintainers.yaml and required-team wording to describe the 'at least one managed team' rule and managed:false semantics (excluded from handle verification, mailing lists, service desk, Copilot seats). - example/maintainers.yaml: rename the Kubernetes example's required team from project-maintainers to maintainers, matching template/. - AGENT.md: update the sample maintainers config to use the maintainers team name and demonstrate an emeritus team with managed: false. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Robert Kielty <robert.kielty@cncf.io>
RobertKielty
requested review from
ahmadqasembader,
jeefy and
riaankleinhans
and
a balanced review from Copilot
September 10, 2026 11:22
github-actions
Bot
added
the
needs-triage
github-actions
Bot
added
needs-kind
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The documentation consistently matches the implemented schema and validation behavior.
Pull request overview
Aligns dot-project documentation and examples with the managed-team convention.
Changes:
- Replaces the legacy required team name.
- Documents
managed: falsebehavior. - Adds an unmanaged emeritus-team example.
File summaries
| File | Description |
|---|---|
utilities/dot-project/README.md |
Documents managed-team requirements. |
utilities/dot-project/example/maintainers.yaml |
Renames the example team. |
utilities/dot-project/AGENT.md |
Updates agent guidance and example. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
ahmadqasembader
approved these changes
Sep 10, 2026
riaankleinhans
approved these changes
Sep 10, 2026
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
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.
README.md, example/maintainers.yaml, and AGENT.md still referenced the old hard-required 'project-maintainers' team name and rule, which was superseded by PR #602 (managed flag for flexible resource provisioning). SCHEMA.md and template/maintainers.yaml were updated by that PR but these three files were missed.