Is your feature request related to a problem? Please describe.
Currently, CommitPulse visualizes GitHub activity but does not provide insights into the programming languages a user works with.
Developers often want to showcase their technical profile, but they need to use external tools to understand and display their repository language distribution.
Describe the solution you'd like
Add a repository language analytics card that displays the distribution of programming languages used across a user's repositories.
Example:
JavaScript 45%
TypeScript 30%
Python 15%
CSS 10%
The feature should:
- Fetch language statistics using GitHub API data.
- Calculate language percentages.
- Display the information as a visual card/chart.
- Support export along with other CommitPulse visuals.
This would help developers showcase their technical diversity directly through CommitPulse.
Describe alternatives you've considered
An alternative is manually collecting language statistics from individual repositories, but this is time-consuming and not scalable.
Another option is relying on third-party analytics tools, but integrating this feature directly into CommitPulse would provide a smoother experience.
Is your feature request related to a problem? Please describe.
Currently, CommitPulse visualizes GitHub activity but does not provide insights into the programming languages a user works with.
Developers often want to showcase their technical profile, but they need to use external tools to understand and display their repository language distribution.
Describe the solution you'd like
Add a repository language analytics card that displays the distribution of programming languages used across a user's repositories.
Example:
JavaScript 45%
TypeScript 30%
Python 15%
CSS 10%
The feature should:
This would help developers showcase their technical diversity directly through CommitPulse.
Describe alternatives you've considered
An alternative is manually collecting language statistics from individual repositories, but this is time-consuming and not scalable.
Another option is relying on third-party analytics tools, but integrating this feature directly into CommitPulse would provide a smoother experience.