Feat/prettier and ci#64
Conversation
|
Warning Review limit reached
More reviews will be available in 57 minutes and 12 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (33)
✨ 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 |
|
@Zahnentferner, there are too much insertion and deletion bcz I have configured Prettier for formatting and these all changed are related to formatting only and only and other than this, I have configured deploy.yml according to vite-react app. |
Addressed Issues:
Fixes: No issue to link.
Additional Notes:
This PR updates the GitHub Actions deployment workflow to properly support the Vite + React application setup for GitHub Pages deployment.
Changes Made
Configured deploy.yml workflow for:
dependency installation
production build generation
GitHub Pages deployment
artifact upload handling
Updated workflow environment to use a modern Node.js version compatible with current GitHub Actions recommendations.
Added and configured Prettier to enforce consistent code formatting across the project.
Applied formatting consistency improvements throughout the codebase.
Checklist
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.