Are we adding successful builds to `meta.yml`? That'd be nice. Then we could just not add to `meta.yml` on fail but not trigger a CI failure for now.
Open
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Are we adding successful builds to `meta.yml`? That'd be nice. Then we could just not add to `meta.yml` on fail but not trigger a CI failure for now.
A slack hook on build fail would be nice if easy 🤔
Originally posted by @ewels in https://github.com/nf-core/modules/pull/7101#discussion_r1867929103
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 meta.yml and the CI configuration responsible for build results, then read the linked pull request discussion for context. Clarify whether successful builds should be recorded, whether failures should avoid failing CI, and whether Slack notification is in scope. Done requires an agreed scope and corresponding CI checks or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100