Gssoc guidlines and Contributing.md with CI/CD pipeline

[deekshithgowda85]

Summary by CodeRabbit

• New Features

  • Added automated CI/CD workflow for lint and build validation on pull requests.
  • Added test suite dashboard for running and monitoring test executions.

• Documentation

  • Added community Code of Conduct and contributor guidelines.
  • Added standardized GitHub issue templates for bug reports, feature requests, and good first issues.
  • Added pull request template with contributor checklist.
  • Added GSSoC contributor guide and curated list of beginner-friendly tasks.
  • Added technical documentation on sandbox integration architecture.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
sec-dev-3lx6	Error		May 25, 2026 2:47pm

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR establishes SecDev as an open-source project by introducing governance templates, community guidelines, CI automation, and a comprehensive test dashboard UI. It adds GitHub issue/PR templates, code of conduct, contribution guides (including GSSoC-specific pathway), automated lint/build workflow, E2B architecture documentation, and a multi-layered test suite dashboard with real-time orchestration and AI analysis integration.

Changes

Project Governance and Foundation

Layer / File(s)	Summary
Issue and PR templates .github/ISSUE_TEMPLATE/bug_report.md, .github/ISSUE_TEMPLATE/feature_request.md, .github/ISSUE_TEMPLATE/good_first_issue.md, .github/PULL_REQUEST_TEMPLATE.md	GitHub issue templates for bug reports, feature requests, and beginner-friendly tasks; PR template includes verification checklist and contribution conventions.
Code of conduct and community standards CODE_OF_CONDUCT.md	SecDev community code of conduct defining behavioral expectations, enforcement scope, and escalating consequences following Contributor Covenant v2.1.
Contribution guidelines and starter issues CONTRIBUTING.md, CONTRIBUTING_GUIDE_GSSOC.md, GOOD_FIRST_ISSUE.md	Comprehensive contribution guide with setup, branch/commit conventions, code style and security practices; GSSoC-specific contributor pathway; and five curated beginner tasks covering console UI, sidebar accessibility, logging, empty states, and repository browser copy.
CI/CD automation workflow .github/workflows/ci.yml	GitHub Actions workflow running on push/PR with Node.js 20, npm caching, and automated lint/build steps; includes environment setup for database and API configuration.
E2B sandbox architecture documentation report/E2B_Sandbox_Deep_Dive.md	Reference guide documenting end-to-end E2B integration: deployment lifecycle, runtime templates, test/security orchestration, database persistence, environment handling, observed failure behaviors, and mental model with file index.

Test Dashboard UI Implementation

Layer / File(s)	Summary
Test data types and layer definitions app/console/testing/page.tsx.bak	TypeScript data types for deployments, test runs, and per-layer state; configuration for four testing layers (route health, API testing, security scan, performance) with IDs, labels, icons, and styling; helper functions for state initialization.
Reusable test UI components app/console/testing/page.tsx.bak	Three composable components: animated ProgressBar, LayerCard with status badges and stats, and ResultsTable for detailed horizontally-scrollable result inspection.
Page state management and test orchestration app/console/testing/page.tsx.bak	Main Page component with deployment/history fetching, per-layer test execution via sequential API calls (POST to start, repeated GET to poll), results aggregation, and abort-based stopping with computed overall scores.
Dashboard UI layout and sections app/console/testing/page.tsx.bak	Complete dashboard with deployment selector, run/stop/refresh controls, conditional overall score panel, four-layer card grid, collapsible detailed results, AI analysis recommendation panel, and run history with status indicators.

Sequence Diagram

sequenceDiagram
  participant User
  participant Page as Test Dashboard
  participant API as Test API
  participant Results as Results API
  User->>Page: Load dashboard / Select deployment
  Page->>API: Fetch /api/deploy & /api/tests/run history
  API-->>Page: Available deployments & prior runs
  User->>Page: Click "Run All Tests"
  Page->>Page: Reset all layer state
  loop For each of 4 layers sequentially
    Page->>API: POST /api/tests/run {sandboxId, type}
    API-->>Page: Run initiated
    loop Poll until complete/failed
      Page->>API: GET /api/tests/run {sandboxId, type}
      API-->>Page: Layer phase & status
    end
    Page->>Results: GET /api/tests/results {runId}
    Results-->>Page: Detailed test results
    Page->>Page: Update layer stats (pass/fail/time)
  end
  Page->>Page: Compute overall score & aggregates
  Page-->>User: Display all results & overall score
  User->>Page: Click "Analyze" (optional)
  Page->>API: POST /api/tests/analyze {runId}
  API-->>Page: AI analysis text
  Page-->>User: Display analysis & recommendations

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

The PR spans diverse artifact types: straightforward template/documentation additions (low effort) plus a substantial 644-line test dashboard component with multi-layer state orchestration and API polling logic (medium-high effort). The heterogeneity of changes (governance templates, CI config, architecture docs, and interactive UI) requires separate reasoning for each cohort; the dashboard UI itself demands careful review of state management, async orchestration, and UI composition order.

Possibly related PRs

• deekshithgowda85/SecDev#2: Implements the test API routes (/api/tests/run, /api/tests/results, /api/tests/analyze) and Inngest test orchestration that the test dashboard UI calls and polls.

Poem

🐰 A dashboard blooms with layers so bright,
Each test runs true, from morning to night,
With templates and guides, the crew gathers 'round,
E2B sandboxes spinning without a sound,
The codebase now open, the journey's begun!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title mentions only 2-3 of the 10+ files added; it misses major additions like issue templates, CODE_OF_CONDUCT, and documentation files, making it incomplete.	Consider a more comprehensive title like 'Add contribution guidelines, issue templates, CI/CD workflow, and documentation' that better reflects the full scope of changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch master

---

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 and usage tips.}