Skip to content

Feat/weekly productivity dashboard#2908

Closed
karthikeyakakarlapudi2007 wants to merge 4 commits into
Priyanshu-byte-coder:mainfrom
karthikeyakakarlapudi2007:feat/weekly-productivity-dashboard
Closed

Feat/weekly productivity dashboard#2908
karthikeyakakarlapudi2007 wants to merge 4 commits into
Priyanshu-byte-coder:mainfrom
karthikeyakakarlapudi2007:feat/weekly-productivity-dashboard

Conversation

@karthikeyakakarlapudi2007

@karthikeyakakarlapudi2007 karthikeyakakarlapudi2007 commented Jun 29, 2026

Copy link
Copy Markdown

Summary

This PR introduces a Weekly Productivity Summary Dashboard feature to DevTrack.

The feature provides users with a consolidated overview of their weekly development activity, including contribution metrics, productivity insights, and week-over-week comparisons to help users track their progress more effectively.

Closes #


Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that changes existing behavior)
  • Documentation update
  • Refactor / code cleanup (no functional change)
  • Performance improvement
  • Security fix
  • Tests only

What Changed

  • Added a dedicated Weekly Productivity Summary section to the dashboard.
  • Added weekly metrics including total commits, pull requests, issues created, and repositories contributed to.
  • Implemented week-over-week comparison for productivity statistics.
  • Added productivity insights and contribution trend analysis.
  • Added responsive UI for desktop, tablet, and mobile devices.
  • Maintained consistency with the existing DevTrack design system and component architecture.

How to Test

  1. Clone the repository and install dependencies.
  2. Run the development server using the project's standard setup command.
  3. Navigate to the dashboard page.
  4. Verify that the Weekly Productivity Summary section is visible.
  5. Verify that all weekly statistics render correctly.
  6. Check that comparison metrics and productivity insights display as expected.
  7. Test responsiveness on desktop, tablet, and mobile screen sizes.
  8. Ensure no existing dashboard functionality is broken.

Additional Notes

This feature enhances DevTrack by providing users with meaningful weekly productivity insights, helping them better understand their contribution patterns and overall development activity.

@github-actions github-actions Bot added type:bug GSSoC type bonus: bug fix type:feature GSSoC type bonus: new feature type:design GSSoC type bonus: UI/design (+10 pts) type:performance GSSoC type bonus: performance (+15 pts) gssoc26 GSSoC 2026 contribution labels Jun 29, 2026
@github-actions

Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

@Priyanshu-byte-coder

Copy link
Copy Markdown
Owner

Hi — new feature pages and UI additions are currently on hold while we focus on code quality (see discussion #2651). This is a large feature PR (23 files, 1884+/1009-) — please hold it until the quality sprint wraps up. PRs for tests, refactoring, bug fixes, and docs are welcome in the meantime.

@Priyanshu-byte-coder

Copy link
Copy Markdown
Owner

New feature/UI PRs are on hold during the code-quality sprint — see discussion #2651. We'll revisit after the sprint; tests, refactors, and bug-fix PRs are the priority right now.

@Priyanshu-byte-coder

Copy link
Copy Markdown
Owner

This PR bundles three unrelated feature systems into one 22-file change: the weekly productivity dashboard, a full achievements system (src/components/achievements/* + achievements-config.ts), and a goals rewrite (src/components/goals/* + GoalTracker + goals API routes). That's impossible to review or land safely as a unit — a problem in any one blocks all three, and it overlaps your own #2717 (the focused weekly-summary) plus the other goals PRs in flight.

Please split it: keep #2717 as the weekly-summary PR, and open separate PRs for (a) the achievements system and (b) the goals redesign, each on its own so they can be reviewed and their UI checked independently. Closing this one in favor of that split — the individual pieces are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:design GSSoC type bonus: UI/design (+10 pts) type:feature GSSoC type bonus: new feature type:performance GSSoC type bonus: performance (+15 pts)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants