numba / numba/numba-integration-testing
Question: Best way to get a status badge for a job?
- Dominant language
- Python
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I was building a [status page](https://epassaro.github.io/status) for TARDIS and noticed CircleCI does not allow the creation of individual badges for jobs (like GitHub Actions).
Also, [shields.io](https://shields.io/category/build) 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?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository files, tests, or entry points. Start by checking the linked status page and the CircleCI and shields.io capabilities described in the report; done would require a decided, reproducible way to expose an individual job's status, but no implementation target is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100