Use "Dagger for GitHub" to clean up CI and make it more portable
Open
Nobody has claimed this yet.
wishlist
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Is your feature request related to a problem? Please describe
The actions have become increasingly complicated plus they are difficult to port to GitLab etc.
Describe the solution you'd like
Dagger for Github should help with this. For technical questions ask @edmundmiller
Describe alternatives you've considered
No response
Additional context
No response
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 reviewing the repository’s existing GitHub Actions and the linked Dagger for GitHub action. Determine which CI workflows should be migrated and how portability to GitLab will be assessed; done means the CI is less complicated and can be ported beyond GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100