-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
feat(github): Analyse past release times #3135
Conversation
Signed-off-by: Tim Collins <tim@thecollins.team>
Signed-off-by: Tim Collins <tim@thecollins.team>
Sadly my python knowhow is even worse :D I totally missed that Python era - I am still on pure bash or Go ^^ Shall we present the output of this on the GH pages over there? |
short answer is “yes, eventually, but not in this PR”. We should use gha to build the data as we go rather than this expensive query for the whole history. Once we have that then we can look into publishing. |
Could I get some reviews please? |
I am okay with that :) 👍 |
The SLA comes from a time that @jmeridth told me. But I can't find it written anywhere. |
@tico24 maybe documentation regarding what permissions the PAT requires would be nice, WDYT? |
Ah yeh I'll do that. It just needs public read, so super minimal. |
https://cloud-native.slack.com/archives/C0574J7GR5Z/p1737707991527589 |
I'm far from a python expert so please don't laugh too much.
I wanted to understand whether or not we are releasing at a faster pace than before (given we are a more organised team and we have automation in the likes of Renovate now).
This script calculates the release time for each upstream release and plots the values on a graph.
Checklist: