Open
Conversation
The generate-og command existed but was never scheduled. This adds a daily systemd timer (3am) to regenerate OG images where install counts have changed since last generation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
generate-ogcommand existed but was never scheduled — OG images were only generated on first page view and never updatedGetPackagesNeedingOG(claimed to detect metadata changes but only checks install counts)Deploy notes
sudo systemctl start wpcomposer-generate-og.timerTest plan
wpcomposer generate-ogruns successfully on the serversystemctl status wpcomposer-generate-og.timer🤖 Generated with Claude Code