psalm / shepherd Goto Github PK

If enabled with Psalm in jakzal/phpqa, it fails with:

Extra content at the end of the document
 on line 4, column 1

See https://github.com/dkarlovi/xezilaires/runs/443789869?check_suite_focus=true#step:6:32

Warning: Division by zero in /var/www/vhosts/shepherd.dev/httpdocs/src/Api.php on line 72 🙃

If the github api or some similar api identifies repo B as being forked from repo A and branch B:C is either equal to or "behind" the commits of A:C (i.e. commits ahead/behind master), I would suggest suppressing the listing of repo B from the landing page.

i.e. there's little utility in my fork of psalm showing up on the landing page when the master branch is always either equal to or behind the master branch of vimeo/psalm

I don't know how long it has been, but apparently, https://shepherd.dev is down.

As far as I know type coverage is for e.g. a function's argument and return type has type, but there might be more info about it.

I request to add docs about what type coverage is and how it is calculated

Thanks

to ease finding bigger regressions in coverage it would be great if the shepherd result list would indicate the difference between coverage of commits in

https://shepherd.dev/github/redaxo/redaxo

example for a single commit

I have noticed recently that type coverage has stopped being updated for one of my projects ( https://github.com/azjezz/psl ), I'm not sure if this is an issue on my side, but the CI script has always been the same ( see: https://github.com/azjezz/psl/blob/develop/.travis.yml#L33 / https://github.com/azjezz/psl/blob/develop/composer.json#L42 ).

The latest CI build ran just a few seconds ago, but the latest update according to shepherd.dev is 4 months ago ( https://shepherd.dev/github/azjezz/psl ).

The only thing I can think of that has changed since then is the default branch name from master to develop

current type coverage: 100% ( 100.084 actually 😆 )
type coverage in shepherd: 91%

A recent PR I made to PSL, lowered the type coverage from 100% to 99%, and I didn't notice until after it got merged and I saw the badge. while the fix was pretty easy ( 00602d71 ), I would have rather the CI failed in the PR or at least shepherd bot commented to alert about the type coverage decrease.

How feasible is it to add support for other repo providers to shepherd, either in a self-hosted context or a pr context?

Shields.io offers shields in several different styles. It would be great if Shepherd could do the same. In particular, I'd really like to use the flat-square style for visual compatibility with my other shield images.

Hi, I have problems in using psalm with --shepherd.

This is when running it into ci (github actions):

Error with Psalm Shepherd:
<br />
<b>Fatal error</b>:  Uncaught Github\Exception\RuntimeException: Not Found in /var/www/vhosts/shepherd.dev/httpdocs/vendor/muglug/github-api/lib/Github/HttpClient/Plugin/GithubExceptionThrower.php:101
Stack trace:
#0 /var/www/vhosts/shepherd.dev/httpdocs/vendor/php-http/httplug/src/Promise/HttpFulfilledPromise.php(34): Github\HttpClient\Plugin\GithubExceptionThrower-&gt;Github\HttpClient\Plugin\{closure}(Object(GuzzleHttp\Psr7\Response))
#1 /var/www/vhosts/shepherd.dev/httpdocs/vendor/muglug/github-api/lib/Github/HttpClient/Plugin/GithubExceptionThrower.php(102): Http\Client\Promise\HttpFulfilledPromise-&gt;then(Object(Closure))
#2 /var/www/vhosts/shepherd.dev/httpdocs/vendor/php-http/client-common/src/PluginClient.php(161): Github\HttpClient\Plugin\GithubExceptionThrower-&gt;handleRequest(Object(GuzzleHttp\Psr7\Request), Object(Closure), Object(Closure))
#3 /var/www/vhosts/shepherd.dev/httpdocs/vendor/php-http/client-common/src/PluginClient.php(175): Http\Client\Common\PluginClient-&gt;Http\Client\Common\{closure}(Object(GuzzleHttp\Psr7\Req in <b>/var/www/vhosts/shepherd.dev/httpdocs/vendor/muglug/github-api/lib/Github/HttpClient/Plugin/GithubExceptionThrower.php</b> on line <b>101</b><br />

Configs contain sensitive info which is better passed passed to the app via environment variables when deployed using platforms like Docker and Kubernetes.

I know some deployment platforms work better with files, so this solve should prob read from ENV first, then fallback to file for compatibility.

In addition to clarifying the build process for Docker images, this should also serve as a convenience to users seeking to run their own shepherd services via Docker or Kubernetes.

Does shephard.dev support a json endpoint (or something similar) to support shields.io badges?
https://shields.io/

We use this badges, which are more customizable/beautiful. Would be great all of our badges would have the same visual appearance

See our projects readme as an example
https://github.com/redaxo/redaxo/blob/master/README.md

A few hours ago we added shepherd but the badge is still rendered as „unknown“, see https://camo.githubusercontent.com/551ab204c7b0a8690d86e223d9552a75174ad2ff/68747470733a2f2f73686570686572642e6465762f6769746875622f72656461786f2f72656461786f2f636f7665726167652e737667

The github action reports that the coverage data was uploaded successfully

https://github.com/redaxo/redaxo/pull/3098/files