Not sure where is the right place to ask about this, please direct me to the appropriate channel if this isn't it We are running several nf-core pipelines, as well as some other non-nextflow pipelines, in AWS HealthOmics. For various reasons, some related to AWS, some related to our data/needs/etc, we have to customize various aspects of the pipelines - mostly config changes for provisioning, added config for AWS, etc. I'm now several versions behind on a couple of the nf-core pipelines and I'm wondering how folks are managing their out-of-band changes with updates to the core pipeline repos. Do you usually just maintain a branch for your changes and periodically git rebase? Other approaches? Thanks in advance

Yeah we maintain a branch with changes in the org account. The process to update the pipeline version requires internal verification. Which checks against a benchmark dataset. Depending on the pipeline, we choose a few metrics that matter and use those.