Skip to content

Restore the Website dispatch so the Docs pin advances again - #38

Merged
batuhan merged 1 commit into
mainfrom
fix/restore-website-dispatch
Aug 29, 2026
Merged

Restore the Website dispatch so the Docs pin advances again#38
batuhan merged 1 commit into
mainfrom
fix/restore-website-dispatch

Conversation

@batuhan

@batuhan batuhan commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

#24 removed the notify-website job, which turned out to be the only path that advances .spacefast/docs-revision in spacefast/www — the Refresh Docs workflow there fires solely on this repository_dispatch and has skipped every run since. The pin froze at b7eb03de (Aug 19), so every Website build since — including succeeding ones — composed ten-day-old Docs: the live site is missing the zero-runtime rename, the glossary, the local-development page, and the /docs/apps/zero redirect.

This reverts #24 verbatim. spacefast/www#30 unpins the immediate staleness and unblocks the (separately broken) hosted builds; this PR keeps the pin advancing for every future Docs merge.

If pinging the Website per push was removed for a reason (noise during the Aug 19 firefight?), the alternative is deleting the pin mechanism entirely and having the hosted build clone latest — but that decision should be made explicitly, not by a severed dispatch.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Summary by CodeRabbit

  • Chores
    • Added automated notifications to the website when documentation updates are published from the main branch.
    • Includes the documentation commit reference in the notification for reliable synchronization.
Removing notify-website on Aug 19 severed the only path that advances
.spacefast/docs-revision in spacefast/www: the Refresh Docs workflow
there fires solely on this repository_dispatch, so the pin froze at
b7eb03d and every Website build since has composed ten-day-old Docs.
Reverts #24.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 29, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-29T12:53:39.350584Z 4887bb2 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Aug 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7a4862d2-9e35-4078-a86b-96f2587b0e14

📥 Commits

Reviewing files that changed from the base of the PR and between ea2e011 and 4887bb2.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The CI workflow adds a notify-website job. The job runs after docs for pushes to main in the canonical repository, then dispatches the documentation commit SHA to spacefast/www.

Changes

Documentation update notification

Layer / File(s) Summary
Website notification workflow
.github/workflows/ci.yml
Adds a conditional post-docs job. The job creates a scoped GitHub App token and sends a docs-updated repository dispatch with the source repository and commit SHA.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 4887b

This change restores Website updates after Docs merges so the published documentation pin can advance. No actionable merge-blocking risk remains in the supplied evidence; the PR is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes restoring the Website dispatch that advances the Docs revision pin. It matches the main change.
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

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 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/restore-website-dispatch

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@spacefast
spacefast Bot temporarily deployed to preview/fix/restore-website-dispatch August 29, 2026 12:52 Inactive
@batuhan
batuhan merged commit 50f8c57 into main Aug 29, 2026
7 checks passed
@batuhan
batuhan deleted the fix/restore-website-dispatch branch August 29, 2026 13:26
batuhan added a commit that referenced this pull request Aug 29, 2026
The Website's hosted build now clones latest Docs main on every build
(spacefast/www#31), so no cross-repo dispatch, app token, or pin bump is
needed. Reverts #38, which restored the job before the right fix was
clear.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant