Feature/advanced export ai guidelines 8613210377134183394#3
Conversation
- Added GitHub Actions workflows for CI (verification) and CD (publishing). - Integrated automated NPM publishing with provenance support and version-check protection. - Added dependency caching to workflows for faster build times. - Updated README with instructions for configuring NPM_TOKEN and CI/CD overview. - Fixed type errors in Player and Renderer components ensuring build success. Co-authored-by: codedbytahir <200578194+codedbytahir@users.noreply.github.com>
- Updated main README to distinguish between `npx create-motionforge` (new projects) and `npm install motionforge` (existing projects). - Added local testing instructions for the CLI tool to avoid 404 confusion. - Fixed `packages/motionforge/README.md` to accurately describe the high-performance export engine features. - Ensured all documentation reflects the latest framework capabilities. Co-authored-by: codedbytahir <200578194+codedbytahir@users.noreply.github.com>
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughThis PR establishes CI/CD automation via GitHub Actions for testing and npm publishing, updates documentation to reflect new onboarding flows and publishing automation, extends the renderer API with WebCodecsEncoder export, modifies renderCompositionToVideo signature to accept a frame-setter function and element instead of canvas, adds bitrate configuration, and exposes CacheStats interface. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
✨ 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 |
Summary by CodeRabbit
New Features
Documentation