Add CI Workflow and Badge#895
Conversation
❌ Deploy Preview for fixmybharat failed. Why did it fail? →
|
🙏 Thank you for your contribution, @fy23-ssvhankade-star!PR Details:
Quality Checklist:
Review Process:
Note: The maintainers will monitor code quality and ensure the overall project flow isn't broken. |
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ 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 |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
👋 Hello @fy23-ssvhankade-star! Thank you for your first Pull Request to VishwaGuru! 🎉
We appreciate your contribution to this open source platform empowering India's youth to engage with democracy.
What happens next?
- A maintainer will review your PR soon
- Please ensure all tests pass and the code follows our style guidelines
- Be ready to address any feedback or requested changes
Before your PR is merged:
- Ensure your code follows the project's coding standards
- All tests should pass
- Update documentation if needed
- Make sure your commits are clear and descriptive
Resources:
Thank you for contributing! 🚀
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found and verified against the latest diff
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/ci.yml">
<violation number="1" location=".github/workflows/ci.yml:13">
P2: The new workflow uses older major versions of core GitHub Actions (`actions/checkout@v3` and `actions/setup-node@v3`) rather than their current supported releases. These v3 actions run on deprecated Node 16 runtimes, which GitHub has been phasing out, and newer major versions like v4 were released specifically to address those deprecation warnings. Because this workflow is newly introduced, it would be better to start on a current, supported version to avoid immediate technical debt and future runtime failures.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| build: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v3 |
There was a problem hiding this comment.
P2: The new workflow uses older major versions of core GitHub Actions (actions/checkout@v3 and actions/setup-node@v3) rather than their current supported releases. These v3 actions run on deprecated Node 16 runtimes, which GitHub has been phasing out, and newer major versions like v4 were released specifically to address those deprecation warnings. Because this workflow is newly introduced, it would be better to start on a current, supported version to avoid immediate technical debt and future runtime failures.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/ci.yml, line 13:
<comment>The new workflow uses older major versions of core GitHub Actions (`actions/checkout@v3` and `actions/setup-node@v3`) rather than their current supported releases. These v3 actions run on deprecated Node 16 runtimes, which GitHub has been phasing out, and newer major versions like v4 were released specifically to address those deprecation warnings. Because this workflow is newly introduced, it would be better to start on a current, supported version to avoid immediate technical debt and future runtime failures.</comment>
<file context>
@@ -0,0 +1,21 @@
+ build:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - name: Setup Node.js
+ uses: actions/setup-node@v3
</file context>
| - uses: actions/checkout@v3 | |
| - uses: actions/checkout@v4 |
2 participants
Added a generic CI workflow and a badge to the README to make the project look more professional.
Summary by cubic
Add a GitHub Actions CI workflow that runs on push and PR to
main/master, usesactions/checkout@v3andactions/setup-node@v3to set up Node.js 18, and runs placeholder checks. Add a CI status badge to the README linking to the workflow and includesocial_preview.pngfor better link previews.Written for commit e84c5f4. Summary will update on new commits.