-
Notifications
You must be signed in to change notification settings - Fork 3
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
Give health score a shot #85
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #85 +/- ##
=======================================
Coverage 77.70% 77.70%
=======================================
Files 17 17
Lines 776 776
Branches 129 129
=======================================
Hits 603 603
Misses 172 172
Partials 1 1 ☔ View full report in Codecov by Sentry. |
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.
This is sick 💯 but not sure about the token naming, is this for testing?
Also is -572 good or bad?
- name: Report health score | ||
uses: slackapi/[email protected] | ||
with: | ||
codecov_token: ${{ secrets.FILS_CODECOV_API_TOKEN }} |
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.
Is this the correct token to use?
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.
Yeah I just wanted to make it clear which human user the API token belongs to (in case I e.g. get hit by a bus)
According to Slack internal Health Score, a score of 0 is perfection, and each identified problem contributes a negative score. |
You can click the check to see a breakdown of how the score is calculated. |
Testing out this alpha GitHub Action we are working on