Repository navigation
Adopt Issues-Only Repository Features - #2
terryrogers wants to merge 3 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: daa5b49b68
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Repository Feature Exceptions | ||
|
|
||
| Every repository must keep Issues enabled and carry local `bug_report.yml`, `feature_request.yml`, `question.yml`, & `config.yml` files. Discussions, Wikis, & Pages remain disabled by default. Any deviation must be recorded in that repository's `.repository-standards.json` `featureExceptions` array with the feature, intended state, owner, reason, approved status, & review or retirement condition. |
There was a problem hiding this comment.
When a repository follows this new policy and adds the prescribed top-level featureExceptions array, the Documentation Quality workflow invokes scripts/Test-RepositoryStandards.ps1, whose property allowlist rejects it as unsupported; the mirrored module payload has the same restriction. As written, every documented feature exception necessarily fails validation, so extend the schema and both validator copies to accept and validate the new structure.
AGENTS.md reference: AGENTS.md:L26-L26
Useful? React with 👍 / 👎.
| "requiredLocalIssueTemplates": [ | ||
| "bug_report.yml", | ||
| "feature_request.yml", | ||
| "question.yml", | ||
| "config.yml" |
There was a problem hiding this comment.
For downstream repositories that retain the former three-template set—or provide no local issue templates—the standards validator still passes: its supported-file list omits question.yml, and it only checks that the old three files appear together when at least one exists. Update both the deployed validator and its module payload so this newly mandatory four-file contract is actually enforced and the question form's provenance is checked.
AGENTS.md reference: AGENTS.md:L26-L26
Useful? React with 👍 / 👎.
| @@ -3,7 +3,7 @@ | |||
|
|
|||
| ## Questions & Usage Help | |||
|
|
|||
There was a problem hiding this comment.
This changes the centrally inherited support route to the 1.2.0 Issues-only policy, but SUPPORT.md still declares version=1.0.0 in its provenance marker. Consumers or audits that use the marker to identify the adopted source revision can therefore treat materially changed content as the old standard; update the marker alongside the route.
AGENTS.md reference: AGENTS.md:L23-L24
Useful? React with 👍 / 👎.
| ## Status | ||
|
|
||
| The repository is aligned with Repository Standards 1.1.0. Account defaults apply only when a downstream repository does not provide a supported local override. | ||
| The repository is aligned with Repository Standards 1.2.0. Account defaults apply only when a downstream repository does not provide a supported local override. |
There was a problem hiding this comment.
The repository now announces Standard 1.2.0 and changes organization-wide support routing and required issue forms, but CHANGELOG.md remains unchanged and only describes the prior baseline. Add an entry describing this release-impacting behavior so downstream adopters can identify the new requirements and compatibility impact.
AGENTS.md reference: AGENTS.md:L17-L17
Useful? React with 👍 / 👎.
Summary\n\n- adopt Issues as the standard repository intake & support surface\n- add the required local question form alongside bug, feature, & configuration forms\n- document Issues enabled and Discussions, Wikis, & Pages disabled by default\n- define repository-local feature exceptions through .repository-standards.json\n\n## Validation\n\n- JSON & YAML parsing passed\n- whitespace validation passed\n- public-content sanitation scan passed\n\nNo repository feature setting is changed by this documentation pull request; the live settings were applied & verified separately.