shepherd icon indicating copy to clipboard operation
shepherd copied to clipboard

WIP - what runs on shepherd.dev

Results 10 shepherd issues
Sort by recently updated
recently updated
newest added

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

A recent [PR ](https://github.com/azjezz/psl/pull/44#event-3617355861) I made to [PSL](https://github.com/azjezz/psl), lowered the type coverage from 100% to 99%, and I didn't notice until after it got merged and I saw the badge....

Shields.io offers shields in [several different styles](https://shields.io/#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...

Without a timezone indication its rather hard to match the date of the history entry to a commit on github, since time is differen ![89ED528D-088C-41F5-A89D-5361327E0366](https://user-images.githubusercontent.com/120441/138593962-1538a98f-e14e-4964-8202-b23ffa3503eb.png) ![D387CF7B-4381-4DD2-AFCC-2BF1C7E19779](https://user-images.githubusercontent.com/120441/138593997-212b6331-cf4f-446d-a896-b48365d4b18e.png)

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...

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...

Hi, I have problems in using psalm with --shepherd. This is when running it into ci (github actions): ``` Error with Psalm Shepherd: Fatal error: Uncaught Github\Exception\RuntimeException: Not Found in...

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

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...