Downstream CI for `libc`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 1.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 69
Description
libc is tested a handful of places downstream for targets that aren't Tier 2+, or have less common configurations. This issue is intended to aggregate a list of any such public CI.
| Targets | Maintainer | Link | Status Badge |
|---|
If you are interested in testing a target that can be run in Docker or natively on GitHub Actions (e.g. with a self-hosted runner), see https://github.com/tgross35/libc-downstream-ci for a simple template to get a daily job going.
If you are already running CI downstream anywhere with public results, comment a link and I'll update the table.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the issue's downstream CI table and the linked libc-downstream-ci template. If you have public CI for a libc target outside Tier 2+, run or verify its results and comment with the target, maintainer, and public link; the issue is complete when the CI is publicly visible and can be added to the table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100