Jump to content

I made a project that uses your GitHub CLI account to quickly extract PRs, commits, branches, issues, and releases into .md files.

 

After extraction, it generates a report with insights, graphs, and more. It’s primarily a CLI, but I also added a GUI with Electron. Overall, it works fine, though not perfectly.

 

The problem is that the insights and the algorithm or logic I’m using vary a lot it’s not the same for a huge repo versus a small one, or for a repo with very few PRs compared to one with many.

 

For example: 1000 PRs, 200 commits, 100 releases, 50 issues;

50 PRs, 1500 commits, 20 releases, 10 issues;

or 250 PRs, 1000 commits, 30 releases, 5 issues;

 

The combinations are endless. So, the best solution by default might be to have a single logic orchestration for both frontends CLI and GUI while ensuring the algorithm remains consistent and delivers real insights with solid value.

 

thanks for reading if you want i can post the repo i not want spam

Link to comment
https://linustechtips.com/topic/1627648-github-cli-but-better-with-gui/
Share on other sites

Link to post
Share on other sites

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×