-
|
I have an idea of tracking type coverage on private project that uses GitHub and GitHub actions. I've decided to start from a simple setup to store info and build charts on google spreadsheet but the a problem to extract type coverage on GitHub workflow. Does anyone solved similar problem or used another approach to track type coverage? example: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
Maybe take a look at shepherd. It's what Psalm use to contact shepherd.dev and store and display widgets you see on: https://shepherd.dev/ The request to shepherd is built in Psalm, but it's possible to override the host name to target any domain. So, you could receive on your website a payload with the summary of Psalm analysis after each CI run (either you host the whole shepherd repo on it or you just create the same entry point only to receive the datas) See here how the payload is constructed: psalm/src/Psalm/Plugin/Shepherd.php Line 37 in 3e837ca and here to override the host name: psalm/src/Psalm/Internal/Cli/Psalm.php Line 300 in fccc366 (shepherd is actually an ordinary psalm plugin built in Psalm itself. If you're not satisfied with the format or the way it's done, you could perfectly create your own plugin base on the Shepherd class to change it however you like) |
Beta Was this translation helpful? Give feedback.
-
|
If you want to do a PR adding documentation to walk through this that would be excellent! |
Beta Was this translation helpful? Give feedback.
-
|
Great to see it works fine :) I have no problem with adding new params in shepherd payload itself as long as it doesn't break compatibility with shepherd.dev. number of issues, time and memory seems like great additions we could even display one day on the website (though I'm not forcing you to change shepherd if you don't want, please just create an issue in the repo so we know it's on the todo list) |
Beta Was this translation helpful? Give feedback.
-
|
@orklah |
Beta Was this translation helpful? Give feedback.
-
|
I'd be fine with a PR for that :) |
Beta Was this translation helpful? Give feedback.
-
PR #9133 |
Beta Was this translation helpful? Give feedback.
Maybe take a look at shepherd. It's what Psalm use to contact shepherd.dev and store and display widgets you see on: https://shepherd.dev/
The request to shepherd is built in Psalm, but it's possible to override the host name to target any domain.
So, you could receive on your website a payload with the summary of Psalm analysis after each CI run (either you host the whole shepherd repo on it or you just create the same entry point only to receive the datas)
See here how the payload is constructed:
psalm/src/Psalm/Plugin/Shepherd.php
Line 37 in 3e837ca
and here to override the host name:
psalm/src/Psalm/Internal/C…