Skip to content

Latest commit

 

History

History
115 lines (79 loc) · 2.58 KB

File metadata and controls

115 lines (79 loc) · 2.58 KB

🤝 Contributing Guidelines

Thank you for contributing to this project!


🌸 NSoC 2026 — Contribution Rules

This project participates in Nexus Spring of Code (NSoC) 2026. All NSoC contributors must follow these rules:

1. Issue Assignment (Required)

  • Always request assignment on an issue before starting work
  • PRs submitted without prior assignment will be closed without review
  • Do not work on issues already assigned to someone else

2. PR Tagging (Required)

  • Include nsoc26 in your Pull Request title or description
  • Example PR title: feat: add login page [nsoc26]
  • PRs missing this tag will be asked to update before review

3. Issue Difficulty Labels & Points

Label Points Use for
level1 3 pts Small fixes, typos, minor tasks
level2 5 pts Medium features or improvements
level3 10 pts Large features or complex fixes

4. Inactivity Policy

  • If you are assigned an issue and are inactive for 7 days, the issue will be unassigned and opened for others
  • Stay in communication if you need more time

5. Quality Standards

Do not submit low-quality, spam, or fake PRs. All PRs must have:

  • Working, tested code
  • No unnecessary changes outside the scope of the issue
  • Clear description of what was changed and why

📌 Steps to Contribute

  1. Fork the repository
  2. Clone your fork
  3. Create a new branch:
    • feature/your-feature-name
    • fix/bug-name
  4. Make your changes
  5. Commit with proper message:
    • feat: add login feature
    • fix: navbar bug
  6. Push to your fork
  7. Create a Pull Request

✅ Rules

  • Do NOT push directly to main branch
  • Follow clean code practices
  • Write meaningful commit messages
  • Test your code before submitting

🧪 Before Submitting PR

  • Code builds successfully
  • No errors in console
  • Follows project structure

💬 Need Help?

Open an issue or ask in discussions.

  1. Fork the repository
  2. Clone your fork
  3. Create a new branch:
    • feature/your-feature-name
    • fix/bug-name
  4. Make your changes
  5. Commit with proper message:
    • feat: add login feature
    • fix: navbar bug
  6. Push to your fork
  7. Create a Pull Request

✅ Rules

  • Do NOT push directly to main branch
  • Follow clean code practices
  • Write meaningful commit messages
  • Test your code before submitting

🧪 Before Submitting PR

  • Code builds successfully
  • No errors in console
  • Follows project structure

💬 Need Help?

Open an issue or ask in discussions.