Open stsquad opened 6 years ago
Patchew doesn't know what an applied pull request is, because it recognizes merged patches from the Message-id tag. Therefore it's hard to give it a concept of "current" pull requests.
Issue #55 is probably an important part of adding such a concept, as a step towards removing the dependency on Message-id. However, it's not enough; if a pull request is dropped for whatever reason (build fails, conflicts) and the next version of the pull request changes the subject, it would not be recognized as a "current" pull request.
Let's start by adding a shield for projects, it's easy. Basically you'd have a new route https://patchew.org/QEMU/badge.svg redirect to one of https://img.shields.io/badge/patchew-passing-success.svg or https://img.shields.io/badge/patchew-failing-critical.png
Projects now have a shield.
A number of CI services now provide a simple png or svg status button that can be embedded in wiki's and markdown documents to show the health at a glance of the project. For example Travis has a url of the form:
And shippable :
which can be easily embedded. Can we have something similar for patchew? I believe patchew does run some builds against a plain master but probably more useful would be something that indicated the health of current pull requests. An SVG button that was green/orange/red depending on:
That we could link to for each monitored project.