-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
chore: adding new kpi report workflow #26922
Conversation
relies on this PR in the release-automations repo - https://github.com/cypress-io/release-automations/pull/85 |
@@ -0,0 +1,71 @@ | |||
name: 'KPI Report Generation' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name: 'KPI Report Generation' | |
name: 'Triage Report' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest renaming to app_triage_weekly_report.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the end goal is to report on the overall health of the repo and not just firewatch specific. That just happens to be the first metric I was generating.
This KPI report workflow begins by generating reports on open vs closed issues and triage throughput metrics
Additional details
Steps to test
I don't think there is a way to test this easily. I have been doing testing in my private repos to verify it works.
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?