Add repository infrastructure for collaborative development

[Copilot]

Establishes CI workflows, templates, and documentation to enforce code quality and teach students professional Git workflows.

CI Workflows

• Python: Ruff linting + Black formatting
• JavaScript/TypeScript: ESLint with auto-detection of package.json
• All workflows trigger on PRs and pushes to master, fail on violations

Templates

• Issue templates: Bug report and feature request with structured fields
• PR template: Checklist covering testing, documentation, code quality

Documentation

For Contributors

• README.md: Project overview, getting started, contribution quickstart
• CONTRIBUTING.md: Complete workflow guide including:
  • Branch naming conventions (feature/, bugfix/, docs/)
  • Commit format (conventional commits)
  • Code standards (PEP 8, Black, no debug statements)
  • PR submission process

For Administrators

• Branch protection guide: Configuration steps for protecting master (required reviews, status checks)
• GitHub Projects guide: Board setup with automation rules, label taxonomy
• Labels guide: Complete categorization (priority, type, status, difficulty, area) with color codes
• Setup summary: Quick reference with next steps checklist

Repository Structure

.github/
├── ISSUE_TEMPLATE/          # Bug + feature templates
├── workflows/               # 3 new + 2 existing CI workflows
├── branch-protection.md     # Admin setup guide
├── labels-guide.md          # Label taxonomy
├── project-setup.md         # Kanban board configuration
├── PULL_REQUEST_TEMPLATE.md
└── SETUP_SUMMARY.md

Administrators must still enable branch protection, create labels, and set up GitHub Projects per provided guides.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Feature] Setup Git Repository</issue_title>
<issue_description>### ✨ Feature Description
Initial setup and configuration of the GitHub repository to support collaborative development, code quality, and project management.

This includes configuring CI workflows, branch protection rules, GitHub Projects, and essential repository settings to ensure a clean and scalable development process.

🧩 Problem Statement

Currently, the repository lacks standardized automation, governance, and structure.
Without proper workflows, branch rules, and project management:
• Code quality cannot be enforced consistently
• Risk of breaking changes increases
• Collaboration between students and team leads becomes harder
• Tracking progress, tasks, and ownership is inefficient

A proper repository setup is essential to ensure best practices, learning value, and long-term maintainability.

💡 Proposed Solution

Set up the GitHub repository with the following configurations:

1️⃣ GitHub Actions (Workflows)
• Add CI workflows for:
• Code linting and formatting
• Trigger workflows on:
• Pull Requests
• Pushes to protected branches

2️⃣ Branch Protection Rules
• Protect the master branch:
• Require Pull Requests before merging
• Require at least 1–2 approving reviews
• Require all CI checks to pass
• Prevent direct pushes
• (Optional) Add rules for develop or feature branches if used

3️⃣ GitHub Projects Setup
• Create a GitHub Project (Kanban-style) with columns such as:
• To Do
• In Progress
• Review
• Done
• Use labels and milestones for better tracking

4️⃣ Repository Structure & Settings
• Add or verify:
• .gitignore
• README.md with project overview and contribution guidelines
• CONTRIBUTING.md for students and contributors
• Issue and PR templates
• Enable:
• Issues
• Projects
• Define repository labels (bug, feature, enhancement, good first issue, etc.)

🔗 Related Issues / Links

• GitHub Actions Documentation
• GitHub Branch Protection Rules
• GitHub Projects (v2) Documentation

📋 Additional Context

This setup is intended to:
• Teach students real-world Git & GitHub workflows
• Enforce clean development practices
• Make onboarding easier for new contributors
• Scale the project as more features and teams are added

This issue should be completed before active development begins.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Feature] Setup Git Repository #3

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.