I was building a status page for TARDIS and noticed CircleCI does not allow the creation of individual badges for jobs (like GitHub Actions).

Also, shields.io isn't capable of doing that (just filter by branch, not job or workflow).

This makes it difficult to track the state of our code without visiting this repository frequently. I thought about a few ways to achieve this with a certain degree of success, but I feel this is still complicated. For example, I could maintain a new branch on my fork that runs the nightly workflow just for TARDIS.

Any suggestion?

I can't think of anything better than to run this from a fork, with all tests except poliastro disabled. We could then remove poliastro from our suite and you would take responsibility for reporting any issues that Numba's main causes you to us. I think it could work.

Hi! Thanks for answering.

I've been thinking a lot about this, and now I don't remember any possible solution :/

I've write again soon once I remember what can be done here.

Just remembered, I think the best way of doing this is to grabbing the status from here:

https://api.github.com/repos/numba/numba-integration-testing/statuses/21989cb59534ab61b7e41ea983f7b66340528273

And make badges through GitHub Actions, JSONbin.org and shields.io.

I don't know if you want to have a general solution for all packages (maybe it's not worth) but I can try something later this week.

@esc here it is: https://github.com/epassaro/numba-integration-badges

It should be updated 2 hours after the nightly tests run.

This could be easily added to this repo, but requires login to JSONBin on behalf of the org.

@esc here it is: https://github.com/epassaro/numba-integration-badges

It should be updated 2 hours after the nightly tests run.

This could be easily added to this repo, but requires login to JSONBin on behalf of the org.

This looks awesome!! I can probably setup a login if need be. Can this be incorporated with a PR to this repo?

Yes, let me check a few things and I'll open a PR later today.