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
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a286666dfc
ℹ️ 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".
| wiki: | ||
| uses: ./.github/workflows/wiki-direct.yml |
There was a problem hiding this comment.
Remove the stale release-time wiki refresh
When this direct wrapper is adopted and .github/wiki is removed, the manual release flow still unconditionally invokes refresh-preview-pointer in .github/workflows/changelog.yml:277-283; that action immediately executes git -C .github/wiki fetch origin. Release preparation therefore fails after creating the release PR and before dispatching its required tests, both here and in migrated consumers.
AGENTS.md reference: AGENTS.md:L159-L173
Useful? React with 👍 / 👎.
| $data['repositories']['pinned-dev-tools'] = [ | ||
| 'type' => 'path', | ||
| 'url' => '.dev-tools-actions', | ||
| 'options' => ['symlink' => false, 'versions' => ['fast-forward/dev-tools' => 'dev-main']], |
There was a problem hiding this comment.
Make the pinned renderer installable for stable consumers
For a normal library consumer without composer.lock and with minimum-stability: stable, this path repository offers DevTools only as dev-main, so the subsequent composer install cannot satisfy a stable ^1.x requirement. With a lock file, install instead uses the exact locked version rather than this path checkout, as documented by Composer's install semantics; consequently the step either fails or runs an unpinned renderer instead of the selected revision.
AGENTS.md reference: AGENTS.md:L154-L164
Useful? React with 👍 / 👎.
| @@ -1,18 +1,14 @@ | |||
| name: Update Wiki | |||
| name: Fast Forward Wiki Update | |||
There was a problem hiding this comment.
Keep transient retries subscribed after renaming the workflow
Renaming the top-level workflow to Fast Forward Wiki Update disconnects it from .github/workflows/retry-transient-failures.yml:5-15, whose workflow_run.workflows filter still contains only Update Wiki and the legacy wiki names. Transient generation or publication failures from the replacement workflow will therefore no longer trigger the repository's automatic retry.
Useful? React with 👍 / 👎.
| * **Local sync:** ``dev-tools:sync`` generates Markdown in | ||
| ``.dev-tools/wiki-generated`` and does not initialize a Git submodule. |
There was a problem hiding this comment.
Align all canonical guides with the direct wiki flow
This now states that normal sync does not initialize a submodule, but docs/getting-started/installation.rst:13,43-44 and docs/usage/syncing-consumer-projects.rst:51-53,74,93-95 still tell consumers that sync creates .github/wiki and that the old preview/maintenance wrappers are active. Consumers following those canonical guides will retain obsolete setup and workflow expectations.
AGENTS.md reference: AGENTS.md:L203-L208
Useful? React with 👍 / 👎.
| - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4 | ||
| with: | ||
| name: wiki | ||
| path: .dev-tools/wiki-generated |
There was a problem hiding this comment.
Upload the generated files from a non-hidden path
The pinned actions/upload-artifact excludes files within dot-directories by default, but this step uploads .dev-tools/wiki-generated without include-hidden-files: true. Consequently Home.md can pass the preceding test -s, yet the upload finds no eligible files and if-no-files-found: error fails every generation run before publication; the pinned action documents both the v4.4+ exclusion and the opt-in input in its README.
AGENTS.md reference: AGENTS.md:L170-L173
Useful? React with 👍 / 👎.
Related Issue
Closes #365
Motivation / Context
Nine consumer Wiki workflows fail before execution because their old entry point no longer supports workflow_call. Use the direct publication model verified in php-fast-forward/container#15, with one shared implementation instead of copying it into every library.
Changes
Verification
Documentation / Generated Output
README, wiki/sync command docs, workflow guide, architecture and AGENTS updated. Generated Markdown and docs were inspected.
Changelog
Added two Changed entries for direct publication and submodule-free sync.
Reviewer Notes
Consumer PRs will reference an exact commit of this workflow so their read-only generation can be tested before this PR merges. Merge the shared workflow before consumer adoption to keep normal DevTools synchronization aligned. Existing workflow targets need explicit migration or sync --overwrite.
Publication remains to be verified on each consumer after merge. Main can advance after the final source check but before the Wiki push; the queued newer publication catches up. The two repositories do not share an atomic write.
The full local gate reports pre-existing PHPmetrics warnings from malformed JUnit XML; PHPUnit itself reports zero warnings/risky tests. No unrelated metrics repair is included.