JSON schema: Chipseq
Abierto
Evaluación
Este issue todavía no se ha evaluado.
Descripción
docs
- Fork the pipeline to your user account, if you have not done so before (Make sure you deselect Copy the master branch only)
- Go to the dev branch and sync the upstream changes (Sync fork -> Update branch)
- Create a branch called json-schema-improvements with the dev branch as base in the fork
- Open the json-schema-improvements branch of the fork either locally (git clone) or online (via Github Codespaces, GitPod...)
- Open the nextflow_schema.json file
- Check that the value in "$schema" is "https://json-schema.org/draft/2020-12/schema". The pipeline should be updated to nf-schema if this is not the case. See the migration guide on how to do this
- Check the schema for insufficient validation keywords and error messages. See the guide for more information on this
- Do the same thing for assets/schema_input.json
- Run nextflow run main.nf -profile test,docker --outdir results -stub to check for any failures in validation with the basic test setup
- Update the changelog of the pipeline
- Push all changes to your fork (if you have not done so yet)
- Open a pull request to the dev branch of the nf-core repository
- Request a review in #hackathon-mar-2025-json-schema-improvements or in the pipeline channel (e.g. #sarek for nf-core/sarek) and set the issue status to Ready to review (PR: https://github.com/nf-core/pacvar/pull/28)
- Wait for approval and merge the pull request once everything works again
- Set the issue status to Done
- Lenguaje dominante
- Nextflow
- Estrellas
- 245
- Forks
- 185
- Merge medio
- 6 min
- PR fusionados (30 d)
- 1
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nf-core/chipseq
-
MACS3 is reporting that 100 paired reads are needed, even when single end data is used as inputAbiertobug
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
-
enhancement improve-behaviour
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100