[FEA] Split up build & test workflows
Open
Nobody has claimed this yet.
? - Needs Triage
feature request
- Dominant language
- Shell
- Stars
- 87
- Forks
- 59
- Avg merge
- 22h 56m
- Merged PRs (30d)
- 4
Description
To maximize flexibility in workflows (especially calling from rapidsai/actions), it would be good if the build, test, and publish steps were separated into individual workflows.
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
Start by locating the workflow that currently combines the build, test, and publish steps, then review how it is intended to be called from rapidsai/actions. Done means the three steps are available as separate workflows while preserving the repository's image-building and publishing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100