What's the idea
Add support for integrating and analyzing third-party Git platforms (such as GitLab, Gitee, Bitbucket, or self-hosted Git instances) alongside GitHub to provide a more comprehensive view of a developer's activity and code quality.
Problem it solves
Currently, gitfut provides excellent insights, but it relies exclusively on GitHub data. However, many developers and open-source contributors do their primary work or host significant projects on other platforms due to enterprise constraints, academic requirements, or regional preferences (e.g., Gitee in China).
Because of this, assessing a developer's activity level, commit history, and coding habits solely based on their GitHub profile can result in an incomplete or inaccurate evaluation. This feature would solve the "fragmented developer identity" problem.
How it might work
- Account Integration: Add a settings section where users can connect external platforms (e.g., GitLab, Gitee) using Personal Access Tokens (PAT) or OAuth.
- Data Aggregation:
gitfut would fetch commit histories, PR/MR statistics, and issue activities via the respective APIs of these platforms.
- Unified Dashboard: Merge the data from all connected platforms into the existing analysis engine, displaying a unified developer profile, activity graph, and code analysis report.
- Self-Hosted Support: Ideally, allow users to input a custom API endpoint URL so that self-hosted instances (like self-hosted GitLab or Gitea) can also be analyzed.
Alternatives
- Manual Aggregation: Developers currently have to manually aggregate their git logs locally using custom scripts to prove their activity.
- Using Multiple Tools: Relying on platform-specific analytics (e.g., GitLab's built-in analytics) alongside
gitfut, which defeats the purpose of having a centralized, comprehensive analysis tool.
What's the idea
Add support for integrating and analyzing third-party Git platforms (such as GitLab, Gitee, Bitbucket, or self-hosted Git instances) alongside GitHub to provide a more comprehensive view of a developer's activity and code quality.
Problem it solves
Currently,
gitfutprovides excellent insights, but it relies exclusively on GitHub data. However, many developers and open-source contributors do their primary work or host significant projects on other platforms due to enterprise constraints, academic requirements, or regional preferences (e.g., Gitee in China).Because of this, assessing a developer's activity level, commit history, and coding habits solely based on their GitHub profile can result in an incomplete or inaccurate evaluation. This feature would solve the "fragmented developer identity" problem.
How it might work
gitfutwould fetch commit histories, PR/MR statistics, and issue activities via the respective APIs of these platforms.Alternatives
gitfut, which defeats the purpose of having a centralized, comprehensive analysis tool.