Repository navigation
fix(website): unblock prod deploy; build website in merge queue - #3287
Conversation
Add related_docs front matter to the scaffolding-yaml-functions example, which the new example-docs prebuild test requires, and run the website build and prebuild tests on merge_group so PRs that pass alone cannot break the production deploy once combined in the queue. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Tip Atmos Pro
No affected stacks workflow was detected for this pull request.  |
Erik Osterman (Cloud Posse) (osterman)
added
the
no-release
Dependency Review✅ No vulnerabilities or license issues found.Scanned FilesNone |
|
Warning SHA Pin Verification Passed — with documented exceptionsAll 239 third-party action reference(s) are covered, but 2 rely on a documented allowlist entry in
See the action run for full details. |
|
Important Cloud Posse Engineering Team Review RequiredThis pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes. To expedite this process, reach out to us on Slack in the |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe website preview build workflow now runs for merge-queue checks. The scaffolding YAML functions example README adds links to related documentation. ChangesWebsite preview workflow
Scaffolding example documentation
Priority: ⬆️ High Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested labels: Suggested reviewers: Merge Risk: ⚪ Minimal · up to The merge-queue event runs the website build without requiring PR context; it simply does not deploy a preview. No demonstrated merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3287 +/- ##
==========================================
- Coverage 84.68% 84.67% -0.01%
==========================================
Files 2105 2105
Lines 206758 206758
==========================================
- Hits 175083 175075 -8
- Misses 23407 23410 +3
- Partials 8268 8273 +5
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
CI timing summaryLatest completed GitHub Actions runs for
Wall-clock time spans the earliest included workflow creation through the latest completion. Aggregate runner time adds each job's execution time, so concurrent jobs are counted separately.
Longest jobs (top 10)
Updated automatically when a PR workflow finishes. |
|
Tip Atmos Pro
No affected stacks workflow was detected for this pull request. |
|
Tip Atmos Pro
No affected stacks workflow was detected for this pull request. |
|
These changes were released in v1.231.0-rc.4. |
Erik Osterman (Cloud Posse) (osterman)
added this to the
1.231.0 milestone
2 participants
what
related_docsfront matter toexamples/scaffolding-yaml-functions/README.md(links toscaffold generate,scaffold validate, and the!includefunction).merge_grouptrigger toWebsite Preview Buildso the website prebuild tests and the Docusaurus build also run against the synthetic merge-queue commit. The preview deploy still ignores these runs because they have no associated PR number.why
Website Deploy Prodrun forbd75d3bc88failed in the build step, so atmos.tools has been stale since fix(agent-skills): track the Claude Code plugin version via Version Tracker #3195 (last good deploy). Theexample-docsprebuild test added in docs: improve navigation, command intros, and example guides #3272 requires every example README to declare at least tworelated_docs, and the example added in feat(scaffold): !include and other YAML functions in scaffold.yaml #3230 had none. Each PR passed on its own; they only conflict once combined.pull_request-only, so nothing validated the combined result before it reachedmain. Theconcurrencyblock on the deploy workflow only serializes deploys; it does not validate content.Merge Queueruleset. That is a repo setting and is not changed here.references
Summary by CodeRabbit
!includeYAML function.