Repository navigation
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Description check |  |
The description clearly explains the direct Wiki publication workflow, submodule removal, legacy workflow removal, validation, and main-only publication. |
| Title check | |
The title clearly and concisely identifies the main change: restoring Wiki publication without a submodule. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the Wiki flow,
A push or pull request starts the show.
The submodule hops out of sight,
Direct pages land by workflow light.
One carrot saved for publish night.
Comment @coderabbitai help to get the list of available commands.
|
🚀 Preview is available for this pull request. |
This branch has not been deployed
1 participant
The current Wiki flow still depends on a tracked Wiki submodule and preview-maintenance writers. Adopt the direct-publication workflow derived from php-fast-forward/container#15 and shared in php-fast-forward/dev-tools#366.
Generate API Markdown with read-only credentials on PRs; only main can publish through an isolated checkout of the separate Wiki repository. Remove the .github/wiki gitlink and its matching .gitmodules entry, preserving the remote Wiki/history. Retire the automatic legacy maintenance wrapper so it cannot recreate pointer-based behavior.
The caller is pinned to a286666dfca2300fffca1ab0d3517b6294ec2c4e, the reviewed implementation commit of dev-tools#366. This makes the generation checks executable before that shared PR merges; merge the shared change first so normal dev-tools:sync also stops invoking wiki --init.
Validation: Composer validate --strict --no-plugins, actionlint and git diff --check passed. The shared actual publisher passed 54 offline assertions and DevTools passed 717 tests / 2,201 assertions with 91.83% coverage. GitHub checks exercise this repository's real Markdown generation. Publication is main-only and remains to be verified after merge.
The required full local composer dev-tools command was run: tests (2 / 78 assertions), Rector, ECS and report generation pass, but it flags existing PHPDoc formatting in unchanged source. This workflow-only PR does not reformat library code.