Refresh content calendar#198
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
auto/calendar
branch
from
July 20, 2026 12:23
fd9da33 to
d2e6498
Compare
Deploying contentforest with
|
| Latest commit: |
f260bd9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://da2f8323.contentforest.pages.dev |
| Branch Preview URL: | https://auto-calendar.contentforest.pages.dev |
github-actions
Bot
force-pushed
the
auto/calendar
branch
7 times, most recently
from
July 20, 2026 15:41
e57a60c to
4ea7eaf
Compare
github-actions
Bot
force-pushed
the
auto/calendar
branch
from
July 21, 2026 03:59
4ea7eaf to
f260bd9
Compare
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
1 participant
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.
Automated refresh of the content-calendar ledgers (
content/_calendar/*.json) by the planner.This is a derived index — review is a formality; merging updates the live
/calendar. Theauto/calendarbranch is force-updated on each planner run, so this PR always reflects the latest schedule.