ci(readiness): add readiness validation and guidance - #2038
Conversation
# [6.4.0](v6.3.0...v6.4.0) (2026-04-24) ### Bug Fixes * add x-access-token prefix for GitHub App token in URL substitution ([3243a22](3243a22)) * **app-conf:** preserve source is_visible setting ([#2028](#2028)) ([33c287a](33c287a)), closes [#1953](#1953) * **schema:** require access token endpoint for oauth client credentials ([#2030](#2030)) ([bccf288](bccf288)), closes [#1950](#1950) ### Features * **nav:** add configurable default.xml nav color ([#2024](#2024)) ([38a26ea](38a26ea)), closes [#2021](#2021) * **ui:** wire custom favicon contract ([#2032](#2032)) ([514181c](514181c)), closes [#1730](#1730) * **validate:** expose detailed AppInspect output options ([#2025](#2025)) ([78f3500](78f3500)), closes [#1976](#1976) [hi#level](https://github.com/hi/issues/level)
Add explicit naming and complexity enforcement, a hardened changed-line coverage workflow, repo-local agent skills, and contributor guidance for secret handling and diagnostic redaction.
|
@codex review |
![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: ba9c9d3028
ℹ️ 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".
| selector: 'variableLike', | ||
| format: ['camelCase'], | ||
| leadingUnderscore: 'allow', |
There was a problem hiding this comment.
The new @typescript-eslint/naming-convention rule applies variableLike as camelCase only, and variableLike includes named functions, so existing PascalCase component declarations now violate lint (for example function DashboardPage() and many similar function <ComponentName>() declarations under ui/src). This makes yarn run lint fail after this change even without touching source code, which can block CI/release jobs that depend on UI lint passing. Add a function-specific exception (e.g., allow PascalCase for selector: 'function') or narrow variableLike so component function names remain valid.
Useful? React with 👍 / 👎.
2 participants
Issue number: N/A
PR Type
What kind of change does this PR introduce?
Summary
Changes
Add explicit naming and complexity enforcement, a hardened changed-line coverage workflow, repo-local agent skills, and contributor guidance for secret handling and diagnostic redaction.
User experience
N/A
Checklist
If an item doesn't apply to your changes, leave it unchecked.
Review
Tests
See the testing doc.
Demo/meeting:
Reviewers are encouraged to request meetings or demos if any part of the change is unclear