Cy 404

[RamuuXfree]

Summary

This Pull Request populates the Previous Year Questions (PYQs) for CY-404: Operating Systems (B.Tech. IV Semester). It adds complete exam papers from five semesters (June 2022 - December 2024) with question-by-question unit tags mapped directly to their syllabus modules.

---

Related Issue

Closes #

---

Type of Change

• Feature (Content Addition)
• Bug Fix
• Documentation / Content Update
• Refactor
• Other

---

What Changed?

📚 Operating Systems Past Papers (CY-404)

• content/rgpv/cscy/semester-4/cy-404/pyqs.json: Populated past papers for:
  • December 2024
  • June 2024
  • November 2023
  • June 2023
  • June 2022
• Syllabus Unit Mapping: Each sub-question has been assigned a "unit": "Unit X" tag (Unit 1 to Unit 5) based on the course syllabus structure (Process Management, Memory Management, File Systems, I/O, etc.) to render unit tags correctly in the UI.

---

Screenshots (UI Changes Only)

N/A (Database/Content changes only. Tag values are consumed dynamically by the frontend to render course unit badges).

---

Testing

• Syntactic Validation: Verified the JSON formatting in pyqs.json to prevent parsing or build errors.
• Local Review: Checked local dev workspace representation of syllabus matching.

---

Checklist

Before requesting a review, confirm the following:

• My branch is up to date with the latest main.
• My code follows the project's coding standards.
• I have tested my changes locally.
• This Pull Request focuses on a single feature branch (cy-404).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyper-learning-tech	Ready	Preview, Comment	Jul 10, 2026 1:11am

[coderabbitai]

Warning

Review limit reached

@RamuuXfree, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 157eda30-806f-4831-afec-e85299893bf9

📥 Commits

Reviewing files that changed from the base of the PR and between c41d9b0 and 95aabe6.

📒 Files selected for processing (1)

• content/rgpv/cscy/semester-4/cy-404/pyqs.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cy-404

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🎉 Congratulations @RamuuXfree!

Thank you for contributing to HyperLearningTech.

Your pull request has been successfully merged into main.

📦 Merge Summary

• PR: Cy 404 #85 - Cy 404
• Status: ✅ Merged
• Repository: HyperLearningTech

🚀 Keep Contributing

• Follow the CONTRIBUTING.md guidelines.
• Keep each Pull Request focused on a single feature or fix.
• Run formatting, linting, type checking, and a production build before opening a PR.

Thank you for helping make HyperLearningTech better.

Happy Coding! 🚀