Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE]: Automated GSoC Final Report Generator for Contributors

Closed
  • Is something wrong?
#162 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github, javascript, react, vite
Domain
analytics, api, frontend

Research direction

Start by reading FeatureWishlist.md and tracing OrgExplorer’s existing page and GitHub API entry points. Define the scope around username and date-range inputs, merged PRs, commits, opened issues, and Markdown output; the feature is done when a contributor’s organization-wide work is summarized with live links in a usable report.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe. Currently, at the end of GSoC or other mentorship programs, students have to manually hunt down all their PRs, commits, and issues across repositories to compile their final reports. Mentors also have a hard time tracking all of a student's scattered contributions in one place when reviewing their progress. I noticed a similar idea mentioned in the FeatureWishlist.md (exportable markdown profiles), but it hasn't been implemented yet.

Describe the solution you'd like I propose building a dedicated "Report Generator" page in OrgExplorer.

  1. A user inputs a GitHub username and selects a date range (e.g., the GSoC coding period).
  2. The app uses the GitHub API to fetch all merged PRs, commits, and opened issues by that user across the organization.
  3. It generates a beautifully formatted, structured Markdown report (and optionally PDF) summarizing their work, complete with live links.
  4. The student can instantly copy this Markdown to submit as their final GSoC report.

Describe alternatives you've considered Manually copy-pasting links or using third-party scripts, which defeats the purpose of having an all-in-one OrgExplorer.
Additional context I would love to take ownership of this feature and implement it! I've already contributed to AOSSIE projects (PictoPy, etc.) and I am very comfortable with React, Vite, and GitHub APIs. Please let me know if this aligns with the vision for OrgExplorer and if I can be assigned to it also i request other contributors that please don't write ai generated auto comment in this because this is a very good feature and i am ready to work on this!

Dominant language
JavaScript
Stars
42
Forks
124
Avg merge
2d 22h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.