Skip to content

Generalize for any repo #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 15 commits into
base: master
Choose a base branch
from
Draft

Generalize for any repo #16

wants to merge 15 commits into from

Conversation

jericson
Copy link

I love the curl dashboard and I want to use some of the stats for other projects. I forked this repository and started generalizing the scripts. For instance, github-cache.pl grabs a copy of issues in any repository. By default it still fetches curl issues. But if you provide another owner/repo, you can get issues from other repositories. Relevant to my interests, OpenSSL:

perl ./stats/github-cache.pl -owner openssl -repo openssl

I've gotten to a point where I'm going to want to remove curl-specific charts. (I love Daniel vs. the rest, but sadly Daniel Stenberg doesn't show up in every GitHub repository.) Before I do that, I was curious if some of my changes would be useful to port back to this repository. If so, I'm happy to work with y'all to make a cleaner patch.

@@ -24,7 +24,8 @@ set ytics 2
set xtics rotate 3600*24*365.25 nomirror
unset mxtics

set pixmap 1 "stats/curl-symbol-light.png"
if (!exists("logo")) logo="stats/curl-symbol-light.png"
set pixmap 1 logo
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we can use load "filename" in gnuplot, so we could move the logo thing into a separate file and avoid having to duplicate this logic all over.

It could actually also be applied to some of the other stuff that is identical in all .plot files here right now.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved some common code into config.plot. It's a bit messy at the moment since there are a few variations on just the code to set the logo.

@bagder
Copy link
Member

bagder commented Apr 28, 2025

I'd be thrilled to accept patches to make the dashboard more generic. We could probably create some sort of config file to set some of the key data, like repo etc.

@jericson
Copy link
Author

I'd be thrilled to accept patches to make the dashboard more generic. We could probably create some sort of config file to set some of the key data, like repo etc.

Awesome! GitHub has become a vital tool for open source projects and it's not easy to pull out useful data about community interactions. Pushing stuff into a config file seems the right thing to do. I hope to hack on it next week.

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

Successfully merging this pull request may close these issues.

2 participants