Théo FIDRY

For the record I would be very interested in being able to make it work with PHARs: https://github.com/box-project/box/issues/331

Oh cool, ok I will have to give it another go then!

If having a Composer PHAR with the plugin then you probably would need to actually replicate the Composer build process. I didn't try in a long time I think doing...

Hm I think that this events is triggered as soon as the release is created. Only after that the build is triggered and upon success the artefact is published. Maybe...

Maybe the deployment or deployment status event? In the end it's what is used to upload the additional artefacts to the release.

Sure: https://github.com/humbug/box/blob/master/.travis.yml#L69

@toolmantim would there actually be a way to use this as a GitHub action step? This would allow one to configure the exact conditions upon which the step needs to...

Thanks for the proposal! It's a bit hard to decide on that like that, would it be possible to have a rough idea of what the code and result looks...

So the logger would write this SVG into a file and then you can include this file content or extract it to display the badge?

Sounds like a good idea to me; But let's wait another team member opinion before getting started :)