copy-artifacts: use shared rainix reusable + fix stale CLAUDE.md deps#225
Conversation
Replace the local workflow with a thin caller of rainix-copy-artifacts.yaml (rainix#201) — centralizes build-and-assert-clean + Cachix/GC-cap resilience. This repos CopyArtifacts.sol does not use ffi; the reusables --ffi is a no-op here.
The repo migrated to Soldeer (soldeer.lock, [dependencies] in foundry.toml, libs=dependencies/, no .gitmodules/lib). Update the stale dependency docs.
|
Warning Review limit reached
More reviews will be available in 51 minutes and 16 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (43)
✨ 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 |
rainix#195 runs the pre-commit bundle in rs-static CI; this repo had accumulated hook-dirt (denofmt on audit/*.md + README, prettier on test_js + json, yamlfmt on pr-assessment, shellcheck .envrc shebang). Formatting + one shellcheck directive only; no source/behaviour changes.
rainix-copy-artifacts (this repo's copy-artifacts.yaml caller) already runs BuildPointers.sol via its hashFiles guard, so the standalone build-pointers workflow is redundant. One artifact-check workflow instead of two.
|
@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment: S/M/L PR Classification Guidelines:This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed. Small (S)Characteristics:
Review Effort: Would have taken 5-10 minutes Examples:
Medium (M)Characteristics:
Review Effort: Would have taken 15-30 minutes Examples:
Large (L)Characteristics:
Review Effort: Would have taken 45+ minutes Examples:
Additional Factors to ConsiderWhen deciding between sizes, also consider:
Notes:
|
1 participant
Replace the local
copy-artifacts.yamlwith a thin caller ofrainix-copy-artifacts.yaml(rainlanguage/rainix#201) — centralizes build-and-assert-clean + the Cachix/GC-cap resilience. This repo's CopyArtifacts.sol doesn't use ffi; the reusable's--ffiis a no-op here. (The reusable also runs BuildPointers.sol when present — same plainforge scriptinvocation as rainix-build-pointers, so it's consistent.)Also fixes the stale CLAUDE.md "Git submodules" deps section — the repo is on Soldeer (
dependencies/, nolib/).🤖 Generated with Claude Code