trunk-merge/pr-110575/2f31bc42-b18c-4088-9bda-f85f04b865c3-bisection - #110851
trunk-io[bot] wants to merge 6 commits into
Conversation
…ull screen The canvas now only covers the whole page, like the artifact full page view. It no longer asks the browser for full screen. The button labels say "Open full page" and "Exit full page". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: c378b147-7317-4d99-af9e-2ba7c7a17997
1 updated Run: c371b7b0-1eeb-47bb-8d9a-d9c485d9043d Co-authored-by: puemos <13174025+puemos@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…f04b865c3-bisection
…f04b865c3-bisection
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (14)📝 WalkthroughWalkthroughHogbox preview lifecycle updates now use sections in the shared CI report, with workflow calls for building, ready, failed, and torn-down states. CI report updates can use Priority: ⬇️ Low Merge Risk: 🔵 Low · up to This change moves preview reporting into the shared CI report and updates Canvas full-page behavior. Teardown may leave a stale ready section in rare duplicate-comment cases. The remaining findings are CI hygiene and test strength, so the change is mergeable with minor follow-up. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to Preview reporting is consolidated without an observed increase in privileges or exposure to untrusted code. Remaining uncertainty concerns concurrent status updates and recovery after interrupted reporting. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
🚥 Pre-merge checks | ❌ 1❌ Failed checks (1 warning)
Full details: Description checkExplanation The description is a Trunk Merge batch-bisection notice, not a stand-alone explanation of this pull request. It omits the required Problem, Changes, testing and test rationale, Release status, and Agent context sections. It does not describe the Hogbox CI report changes or canvas full-page behavior changes. Resolution Replace the batch-bisection text with a repository-compliant description. Explain the user or developer problem, list the observable changes and any mechanical changes, document automated tests and test rationale, select exactly one release-status option, and complete Agent context if an agent authored or assisted with the work.
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
Note
Quiet mode is enabled, so only the most important comments were posted inline. Other review comments are grouped below.
🟡 Other comments (2)
frontend/bin/ci-report/update-ci-report.mjs-266-266 (1)
266-266: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winCheck every report comment before skipping an update.
updateSectionIfPresentchecks only the first report comment. If a duplicate contains thehogbox-previewsection and the first comment does not, teardown leaves the section showing a ready preview.postSectionalready merges duplicate comments. Check all report comments for the section before deciding there is nothing to update.frontend/bin/ci-report/update-ci-report.test.ts-366-366 (1)
366-366: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAssert that an unrelated section stays unchanged.
The “untouched” case passes even if
updateSectionIfPresentoverwrites or removesbundle-size. Assert that the report body, or at least its parsedbundle-sizesection, equals the original. As per coding guidelines, an assertion should be concrete enough that “it shouldn't be possible to break the code and the test pass.”Source: Coding guidelines
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: PostHog/posthog/.coderabbit.yaml
Review profile: QUIET
Plan: Enterprise
Run ID: becbb57a-920b-4673-871c-93361857c825
📒 Files selected for processing (11)
.github/scripts/post-ci-sections.test.mjs.github/scripts/post-hogbox-preview-section.mjs.github/workflows/hogbox-preview-env.ymlfrontend/bin/ci-report/update-ci-report.mjsfrontend/bin/ci-report/update-ci-report.test.tsfrontend/snapshots.ymlproducts/canvas/frontend/scene/CanvasFullscreenExit.tsxproducts/canvas/frontend/scene/CanvasFullscreenToggle.tsxproducts/canvas/frontend/scene/canvasFullscreenLogic.test.tsproducts/canvas/frontend/scene/canvasFullscreenLogic.tstools/hogbox-preview/README.md
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 2 remain after this review.
| sparse-checkout: | | ||
| .github/scripts | ||
| frontend/bin/ci-report |
There was a problem hiding this comment.
🚀 Performance & Scalability | 🟠 Major | ⚡ Quick win
Disable cone mode for this sparse checkout.
Add sparse-checkout-cone-mode: false so the announce job checks out only the paths it needs. Cone mode also materializes repository-root files. As per coding guidelines, “Always set sparse-checkout-cone-mode: false.”
Proposed change
sparse-checkout: |
.github/scripts
frontend/bin/ci-report
+ sparse-checkout-cone-mode: false📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| sparse-checkout: | | |
| .github/scripts | |
| frontend/bin/ci-report | |
| sparse-checkout: | | |
| .github/scripts | |
| frontend/bin/ci-report | |
| sparse-checkout-cone-mode: false |
🧰 Tools
🪛 zizmor (1.30.1)
[warning] 276-282: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
Source: Coding guidelines
This pull request was created and is being managed by Trunk Merge.
This pull request is based on the master branch at SHA e6b3dfe3fa152fd136497b749e3287220b23368f.
See more details about each PR in the batch here:
When CI completes, this pull request will be closed automatically.
Pull Requests Being Tested
This pull request is testing a batch with the changes from pull requests 110575 and 110736 - batching documentation.
Batch Bisection
This pull request is in a batch bisection. Pull requests successfully tested by this PR will re-enter the main queue.